Experiments on production DNS (was: Re: NS.EU.NET running NSD)
- Previous message (by thread): Experiments on production DNS (was: Re: NS.EU.NET running NSD)
- Next message (by thread): Experiments on production DNS (was: Re: NS.EU.NET running NSD)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Mon Jan 20 12:07:21 CET 2003
On 17.01 15:18, Jim Reid wrote: > The fact you're reporting NXDOMAIN errors points to a different > problem. A name server or servers are saying these TLDs don't exist, > which is absurd. So there is a misconfigured server or some cache > poisoning going on. That's got nothing to do with what name server > software runs on ns.eu.net. Unless of course someone configured it to > tell lies for these 4 TLDs. Which is in fact what happened by accident. So ns.eu.net was telling lies about those TLDs for a short period until this was corrected. (More detail: It was configured with a root zone consisting of the bind root.cache file. So the server considered itself authoritative for the root but did not have a correct root zone file.) Lesson learned: Differences in nsd operation to bind need to be documented even more explicitly than they already are. Daniel
- Previous message (by thread): Experiments on production DNS (was: Re: NS.EU.NET running NSD)
- Next message (by thread): Experiments on production DNS (was: Re: NS.EU.NET running NSD)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]