Re: Slave DNS server not taking over.


Slave DNS server not taking over.
\ techjohnny (19 Jul 2006)
. \ Bryan Irvine (19 Jul 2006)
. \ Chris Buxton (20 Jul 2006)

4 msg	TLD wildcard doesn't always work
20 msg	bind replication between sites
2 msg	Least expensive, most robust infrastructure
4 msg	include files in named.conf.local
2 msg	Newbie: Multiple Domains
20 msg	Host = domain
2 msg	Unexpected Token? SERVFAIL?
2 msg	BIND 9.3.2 and Solaris 10 zones
3 msg	Configuring Absolute minimum TTL in BIND-8.4.7
13 msg	building a DNS system
2 msg	Dynamic Reverse Configuration
3 msg	Resolve single word names?
9 msg	How to override an A record
8 msg	Round-robin for high availability?
8 msg	Cache poisoning
7 msg	Strange / Frustrating Caching Problems
8 msg	Name Servers
4 msg	Why is slave zone different from master zone..?
1 msg	Bind - named exiting (due to assertion failure)

Subject:	Re: Slave DNS server not taking over.
Group:	Bind-users
From:	Chris Buxton
Date:	20 Jul 2006

Many operating system resolvers don't make effective use of a second
DNS server. So your experience is unsurprising.

Chris Buxton
Men & Mice

On Jul 19, 2006, at 2:42 PM, techjohnny wrote:

> Hello, Group:
>
> I've got an Active Directory providing the primary DNS to clients, and
> the backup DNS server is running Bind 9 as a slave.
>
> Today, the primary DNS server failed, but the clients still couldn't
> resolve, even though I was able to manually use the nslookup, change
> servers, and verify that the slave responded to requests made by the
> clients.
>
> The clients are using DHCP and have a primary and secondary dns
> server,
> but the secondary doesn't automatically kick in when the primary
> fails.
>
> The slave dns server is properly receiving requests from the primary
> and the zones are all up-to-date.
>
> Thanks,
>
> --TJ
>
>
>