Skip to content
Bots!
Bots!
  • About
    • Myself
    • আমার দোয়া
  • Bookmarks
    • Bookmarks
    • My OCI Bookmarks
    • Useful Proxmox Commands & Links
    • Learning Nano
    • Useful Sites
    • Useful Virtualbox Command
    • Useful MySQL Command
    • Useful Linux Command
    • BTT-CAS
  • Resources
    • Webinar on Cloud Adoption for Project Managers
  • Photos
  • Videos
  • Downloads
Bots!

Bind DNS Auto Slave Using Webmin

Rumi, June 13, 2018June 13, 2018

The latest webmin has bug! In this tutorials I’m using webmin verison 1.801- that actually works. Don’t know if webmin team really knows are aware of the bug 🙁

So, let’s start. But before that, it’s assumed that you have webmin installed in both the servers.

Configuring Webmin Server

  • Go back to the Virtualmin server. Log in with root and go to the Webmin section. Browse Webmin>Webmin Servers Index.
  • Click Register a new server.
  • Enter server2.example.com as the hostname of your slave server.
  • Select Ubuntu OS as OS type.
  • Select a Link type of Login via Webmin with username, and enter the authentication details for your root account.
  • Change Make fast RPC calls? to Yes.
  • Click Save.

Configuring Secondary DNS

  • Now go to Servers>BIND DNS Server and click on Cluster Slave Servers.
  • In the Add server drop-down menu, select your slave server (if it’s the only server you’ve added, you won’t have to select it, as it will already be selected).
  • Set the Create secondary on slave when creating locally? option to Yes.
  • If you have already created any domains on your Virtualmin server, set the Create all existing master zones on slave? option to Yes.
  • If you entered ns2.example.com in the Post-Installation Wizard as secondary name server, then change the Name for NS record option to textbox and enter it.
  • Click Add server and return to the Module Index.
  • Click Apply Configuration in the right corner.

Setting the Master IP Address (optional)

By default, Virtualmin will use the IP address that the master server’s hostname resolves to as the IP that the slaves should contact to transfer records. However, on some systems this IP is 127.0.0.1, which will not work. If you edited the hosts file at the beginning of the tutorial this should not be a problem, but I’ll show you how to solve this.

  • Go to Servers>BIND DNS Server, and click on Module Config.
  • In the Cluster slave servers section, find the Default master server IP for remote slave zones field.
  • Enter the IP address of your master server.
  • Click Save. Any DNS zones created from now on will use that IP.
  • Click Apply Configuration in the right corner.

Please note: that it won’t update existing DNS zones.

Basic Setup of DNS server

There are some more options that you should check. Go to Servers>BIND DNS Server and click on Zone defaults

  • Set the Default email address to an existing email address (Some technical check requires to set an existing email address).
  • Set Default nameserver for master domains to ns1.example.com (optional).

Click Apply Configuration in the right corner.

Create new DNS zone

Now it’s time to test our settings. Click on Create master Zone. Enter your domain name.

  • Check your settings (By default, the IP address for address records will be the primary server’s IP address).
  • Click Create.

Check your master zone on primary and slave zone on the secondary server.

Pointing the Main Domain to DigitalOcean’s Name Servers

The most common problem is that in some cases there is a technical check which requires an email address. That email address is set in the DNS zone file, which is hostmaster@domain.tld, postmaster@domain.tld, etc. by default. Some domain providers let you edit this email address, but most of them do not.

You can solve this problem by pointing the domain to DigitalOcean’s name servers. Of course you can’t do that immediately. After completing this tutorial you have to create a virtual domain in postfix module and create an alias for hostmaster@domain.tld or you can create a virtual server in Virtualmin for domain example.com, which will create these aliases for you, but remember to disable DNS zone.

Other Options

If you want only DNS management, you can install two Webmin instances instead of Virtualmin and Webmin, but this way you have to create DNS records manually. It is the same as Webmin installation above, but you have to do it twice. From Configure Cluster and DNS the steps are the same.

You can use your secondary DNS server for more than one Virtualmin server. In this case the primary DNS server is the virtualmin server, the secondary is the webmin server. This means that you have several Virtualmin servers which are primary DNS servers and you have only one secondary server.

You can use two Virtualmin server as DNS servers. In this case each virtualmin server wil conatin the master zone for the domains added to them. This means that if you create a virtual server in virtualmin1, then virtualmin1 will be the primary DNS server for that domain.

 All done! You have successfully finished this tutorial.

Src:
https://www.digitalocean.com/community/tutorials/how-to-setup-dns-slave-auto-configuration-using-virtualmin-webmin-on-ubuntu

Administrations Collected Articles Configurations (Linux) BindWebmin

Post navigation

Previous post
Next post

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Myself…

Hi, I am Hasan T. Emdad Rumi, an IT Project Manager & Consultant, Virtualization & Cloud Savvyfrom Dhaka, Bangladesh. I have prior experience in managing numerous local and international projects in the area of Telco VAS & NMC, National Data Center & PKI Naitonal Root and CA Infrastructure. Also engaged with several Offshore Software Development Team.

Worked with Orascom Telecom-Banglalink, Network Elites as VAS partner, BTRC, BTT (Turkey) , Mango Teleservices Limited and Access to Informaiton (A2I-UNDP)

Currently working at Oracle Corporation as Principal Technology Solution and Cloud Architect.

You can reach me [h.t.emdad at gmail.com] and I will be delighted to exchange my views.

Tags

Apache Bind Cacti CentOS CentOS 6 CentOS 7 Debain Debian Debian 10 Debian 11 Debian 12 DKIM Docker endian icinga iptables Jitsi LAMP Letsencrypt Linux Munin MySQL Nagios Nextcloud NFS nginx pfsense php Postfix powerdns Proxmox RDP squid SSH SSL Ubuntu Ubuntu 16 Ubuntu 18 Ubuntu 20 Varnish virtualbox vpn Webmin XCP-NG zimbra

Topics

Recent Posts

  • Install Jitsi on Ubuntu 22.04 / 22.10 April 30, 2025
  • Key Lessons in life April 26, 2025
  • Create Proxmox Backup Server (PBS) on Debian 12 April 19, 2025
  • Add Physical Drive in Proxmox VM Guest April 19, 2025
  • Mount a drive permanently with fstab in Linux April 16, 2025
  • Proxmox 1:1 NAT routing March 30, 2025
  • Installation steps of WSL – Windows Subsystem for Linux March 8, 2025
  • Enabling Nested Virtualization In Proxmox March 8, 2025
  • How to Modify/Change console/SSH login banner for Proxmox Virtual Environment (Proxmox VE / PVE) March 3, 2025
  • Install Proxmox Backup Server on Debian 12 February 12, 2025

Archives

Top Posts & Pages

  • Install Jitsi on Ubuntu 22.04 / 22.10
©2025 Bots! | WordPress Theme by SuperbThemes