[5844] in Athena Bugs
class HS & class IN NS/A records conflict in BIND
daemon@ATHENA.MIT.EDU (John T Kohl)
Fri Aug 24 18:05:39 1990
Date: Fri, 24 Aug 90 18:05:18 -0400
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
BIND doesn't seem to deal properly with the case of a client
caching-only server which has NS records in both IN and HS classes
pointing to a machine with the same name.
The caching server seems to lose track of the A record for the HS
server, even though a line is present in the cache file.
The named will spit out a line like 'no root nameservers for class 4' on
the first query to such a configuration.
The caching server then has other problems, like inability to resolve
CNAMES in the IN class.
Changing the name of the server in the HS class to something like
'foobar' and changing the A record in class HS likewise leads to a
working setup.
examples:
this does not work:
NS.DECWORLD.DEC.COM. 99999999 HS NS athena1.decworld.dec.com.
athena1.decworld.dec.com. 99999999 HS A 16.153.177.50
athena1.decworld.dec.com. 99999999 IN A 16.153.177.50
decworld.dec.com. 99999999 IN NS athena1.decworld.dec.com.
this works:
NS.DECWORLD.DEC.COM. 99999999 HS NS hesiod.decworld.dec.com.
hesiod.decworld.dec.com. 99999999 HS A 16.153.177.50
athena1.decworld.dec.com. 99999999 IN A 16.153.177.50
decworld.dec.com. 99999999 IN NS athena1.decworld.dec.com.
