secondary zone weirdness

[Kevin Darcy]

How are you set up to resolve Internet names? This secondary (i.e.
slave) zone, it's not the *root* zone, is it? Are there any log messages
while your external lookups are broken?


- Kevin

Austin Williams wrote:

> We have a secondary zone defined in our internal DNS boot file for our
> parent company so we can resolve their internal names and addresses via
> their wide area network connection to our local network.
> Fine, everything has worked great for about 5 years now.
> About two weeks ago we could suddenly no longer resolve internet names
> or addresses for the parent company. In other words internal names
> resolve fine as always but external names result in a timeout.
> If I try to do lookups using a machine that is also on the internet then
> I can resolve their internet names fine.
> If I remove the secondary zone from my internal DNS server and restart
> named then I can once again resolve internet names but of course not
> internal names.
> The parent company claims not to have changed anything (of course) and I
> know I haven't but something stopped working somehow.
> Anyone have any ideas or suggestions of things to try?