This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
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): FW: IPv6 reverse DNS meeting at last IETF
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
Jim.Reid at nominum.com
Mon Jan 20 17:18:21 CET 2003
>>>>> "Wilfried" == Wilfried Woeber, UniVie/ACOnet <woeber at cc.univie.ac.at> writes: Wilfried> Could someone explain *what the real problem* is, if Wilfried> it exists/ed? In the DNS world, there are many "real problems". :-) For this particular example, it turns out that ns.eu.net *was* misconfigured for a while. [I'm not sure when or for how long.] This meant it gave incorrect answers. Once this was noticed, the problem was promptly fixed. It wasn't an implementation error in NSD or a difference of interpretation in the DNS protocol by the authors of BIND or NSD. Quite simply it appears to have been an example of administrative error causing garbage-in, garbage-out. In this case the garbage was the DNS data fed to NSD. The OP compounded matters by referring to connectivity problems which don't seem to exist. And not showing when and where the NXDOMAIN responses came from didn't help. We now return this discussion to yet another bout of ICANN-bashing...
- Previous message (by thread): Experiments on production DNS (was: Re: NS.EU.NET running NSD)
- Next message (by thread): FW: IPv6 reverse DNS meeting at last IETF
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]