Actually, master and slave has little (read "nothing") to do with
whether the domain resolves.
What's relevant are the delegation records pointing to your domain and
the authoritative
records for the two servers. In a normal, straight-forward setup for
one master and
one slave, both servers wou
DHCP options not giving both nameservers? What happens when you
manually configure your workstation to only query the master?
Quoting "Dennis J." :
Hi,
This morning the slave in our nameserver setup went down and
surprisingly none of the domains hosted on these system could be
resolved anymo
-- Forwarded message --
From: Chris Dew
Date: 2009/3/20
Subject: Re: No name resolution when slave is down
To: "Dennis J."
Asking the obvious here, but does your domain registrar list both your
master and your slave as authoritative nameservers for your domain?
More data will need to be known. Where is the master and where is the
slave, in the same subnet, or elsewhere?
Were you previously getting any queries against the master at all,
look in your logs?
Are you sure your domains NS records even point to the master server?
If the master is rep
Hi,
This morning the slave in our nameserver setup went down and surprisingly
none of the domains hosted on these system could be resolved anymore even
with the master working perfectly fine.
When I send queries directly to the master it resolves the domains fine so
I'm not sure why a failure o
5 matches
Mail list logo
