Slaves not picking up when master is offline

Andre admin at
Fri Dec 21 09:42:33 UTC 2007

I'm having a problem with my DNS-setup. I'm running 1 master and 2 slave nameservers. These servers are authoritative for about 20,000 domains which we registered for our clients.
The problem is; When the master server is offline for several (4+) hours, the slaves don't seem to pick this up properly. Several of our customers can't connect to their domains because of unresolving hostnames.

AFAIK the set-up for the domains is ok. Here's an example of such a domain in the masterserver.

$TTL 14400

@ IN SOA   (
                                         2007102401  ; serial
                                         10800  ; refresh
                                         3600  ; retry
                                         604800  ; expire
                                         86400)  ; min_ttl         IN NS         IN NS         IN NS    IN A *.*.*.*     IN A *.*.*.*       IN A         IN A *.*.*.*     IN A *.*.*.*         IN A *.*.*.*
*       IN CNAME         IN  MX 30         IN TXT "v=spf1 a mx ~all"

- All domains in the masterserver are defined as 'type master' in named.conf
- All domains in de slaveservers are defined as 'type slave' and contain a reference to the master
- All 3 nameservers are listed correctly at our registrars, checked through whois
- zone-transfers and updates are working fine, so communication between master and slaves is ok

The only possible explanation for this problem that I can come up with is that the nameserver's hostnames ( in this example) are also resolved by these servers, the nameservers are authoritative for their own hostname. Is this a problem? As far as I know the registrars keep a hostname as well as an IP-adress for these 3 nameservers, so this shouldn't be a big problem.

Does anyone have any idea what could be wrong with this setup?

Thanks a lot in advance!

Andre P.

More information about the bind-users mailing list