DNS Slave Servers and alternc.net
Word of warning
You must have a thorough knowledge in the DNS system, or precise instructions from your hosting provider or system administrator when changing the values in both pages.
It changes the way the domain lists and domain name resource records are exchanged between your server and the secondary dns servers.
You should leave this management to these people if you don’t want to bring your entire server and all your domains in a complete havoc!
Again, please remind the following admin control panel sections are not to be messed with unless you know what you are doing.
Requirements
These features are natively supported by AlternC.
To enable a server as a master server, it is required to install on it the alternc-slave package.
if [[ ! $(dpkg -l alternc-slavedns) =~ "ii" ]] ; then aptitude install alternc-slavedns; fi;
Also, please note that if you want to enable different DNS servers than the ones you provided during the installation of AlternC, you must edit the /etc/alternc/local.sh
file and reload the alternc.install
script.
# vim /etc/alternc.local.sh ... edit the following lines .... NS1_HOSTNAME="ns1.my-ns-domain.tld # Secondary DNS hostname NS2_HOSTNAME="ns2.my-ns-domain.tld" ... save and run ... # /usr/sbin/alternc.install
Introduction
AlternC allows you to define some servers as DNS slaves or masters for your domain zones.
A good use case for this feature is when you have many servers (slaves) and you want to use your own name servers (masters). In this case, you’ll want the master server to read the list of domaines installed on each alternc slave, regularly retrieve the zones associated with these domains and add them to the name server database.
Note that the terms "master" and "slave" meaning in this documentation differs from the meaning of master / slave in classical DNS documentation, ie. primary/master and secondary/slave name servers.
Alternatively, you could also want to use this feature to replace entirely your registar DNS. In which case, you might want to read the information regarding the alternc.net service.
Manage allowed IP Addresses for slave DNS transfers
To enable a server to retrieve the domains zones, you need to allow its individual IPv4 address (/32) or allow subnets (ex: 10.1.1.0/24).
![](local/cache-vignettes/L680xH150/8.5.allowed-ip-ea4a3.png?1699737637)
Manage accounts for slave DNS transfers
To enable a server to retrieve the domains list, you need to create a http-auth access.
![](local/cache-vignettes/L643xH62/8.5.http-access-2357c.png?1691764425)
This will allow the server to access the url http(s)://user:password@yourdomain.tld/dom_list.php which provides a one-domain-per-line document.
The alternc.net free service
The AlternC association provides a free service for users who need DNS servers to replicate their zones.
The servers are hosted in high quality datacenters to provide a solid resilience in case of failures.
The service is available on https://www.alternc.net.
To make it work, you need to allow the server IPs and provide them an http authentification as previously explained on this page.
Author Published : 17/10/13
Translations : English, English