[4406] in Athena Bugs
6.4R /etc/named
daemon@ATHENA.MIT.EDU (John Carr)
Mon Mar 5 05:06:02 1990
To: bugs@ATHENA.MIT.EDU, network@ATHENA.MIT.EDU
Cc: mar@ATHENA.MIT.EDU
Date: Mon, 05 Mar 90 05:05:35 EST
From: John Carr <jfc@ATHENA.MIT.EDU>
"network" gets a copy of this message because it points out an inconsistency
between the MIT name servers and BIND 4.8.? running on Athena.
An example will be clearer than further explanation:
# hostinfo athena.dialup.mit.edu
Desired host: athena.dialup.mit.edu
Official name: athena.dialup.mit.edu
Host address: 18.71.0.18
# hostinfo dialup.mit.edu
No such host 'dialup.mit.edu'.
# kill `cat /etc/named.pid`
# /etc/named
# hostinfo dialup.mit.edu
Desired host: dialup.mit.edu
Official name: RELAY.MIT.EDU
Alias: DIALUP.MIT.EDU
Host address: 18.71.0.9
# hostinfo athena.dialup.mit.edu
Desired host: athena.dialup.mit.edu
Official name: athena.dialup.mit.edu
Host address: 18.71.0.18
# hostinfo dialup.mit.edu
Desired host: dialup.mit.edu
Official name: RELAY.MIT.EDU
Alias: dialup.mit.edu
Host address: 18.71.0.9
The name servers for the domain dialup.mit.edu will reply "NXDOMAIN" to
requests for the name "dialup.mit.edu".
named considers an NS record for dialup.mit.edu to mean that it should query
the listed name servers to resolve the name "dialup.mit.edu". The MIT name
servers do not agree: they think they should be resolving dialup.mit.edu.
Depending on which record is received first (an A record for "dialup.mit.edu"
or NS record for domain "dialup.mit.edu") the results are inconsistent.
I don't understand the RFCs well enough to know who is right.
