Re: Failure of secondaries

Stupid question perhaps, but where the domains in question actually
delegated to ns2/ns3? or where they only delegated to ns1...

Moving the IP address from ns1 to ns3 would only work if they were in
the same level 2 subnet, and there was no fancy setup involved (for
example no ARP queries being sent by the router).

On Sat, Sep 11, 2010 at 12:44, Hal Burgiss <[email protected]> wrote:
> Hello,
> I am trying understand a predicament I found myself in today. As backgrou=
nd,
> my environment is that I work for a small web hosting company. We handle =
the
> authoritative DNS for most of our clients, using djbdns/tinydns. So we ha=
ve
> ns1, ns2, and ns3 type setup. data.cdb is shared among the 3 when the
> Makefile is executed so that everything stays in sync. This is a
> non-clustered set up, with one ip address per server.
> This has seemed to work flawlessly for years now. Last night though someo=
ne
> inadvertantly disconnected the wrong server, and unplugged the ns1 system=
.
> The eventual impact of that one mistake was that the dns for the hosted
> domains all went down totally. The ns2 and n3 systems were never queried.
> Direct querying during testing showed they were responding normally (eg d=
ig
> blah.com @ns2). =C2=A0Yet, for all practical purposes they might as well =
been
> unplugged too since they were totally quiet. I had been under the false
> assumption that should ns1 go down, that the others would automatically c=
ome
> into play. What am I missing?
> Secondly, when I realized what happened and that the two secondary system=
s
> were totally useless, I moved the ip address from the ns1 to ns3, and
> changed the tinydns configs, restarted the service, verified that tinydns
> was listening on the correct ip and port, and direct test queries worked
> fine. I am doing all this remotely, and did not have the ability to
> reconnect the original system. I was assuming the ip move would be a
> reasonable hotfix. But this did not work. Some 2 hours later the original
> system was reconnected, and within mintues all started working normally
> again. Help me understand this so I can avoid this kind of headache in th=
e
> future!
> Thank you.
> --
> Hal
>