"A" records missing for NS - suggest a sol

Joe Pruett joey at q7.com
Wed Feb 2 01:49:23 UTC 2000


i think he is talking about an issue i raised a few months back.  when
bind gets into a situation where it has NS records for foo.com, all of
which are in foo.com (like ns1.foo.com and ns2.foo.com), and it doesn't
have the corresponding A records.  it will then just deadlock on queries
for that domain and return an error.  i suggested that in that case, the
NS records be thrown away and the root servers be queried again.  someone
shot that down because it is throwing away supposedly more authoritative
info and then getting less authoritative info from the roots.  i think
that authoritative, but useless, info isn't worth keeping around and it
will eventually just time out and you go to the root servers anyway.  now
there are some worse cases that may not be trivial to detect (foo.com NS
ns.bar.com and bar.com NS ns.foo.com), but those are much more rare than
simple NS and no A records.

i've been meaning to dig in and make a patch, but haven't had the time
yet.




More information about the bind-users mailing list