On Dec 9 2008, Davenport, Steve M wrote:
I noticed that one of our nameservers is no longer responding with the
correct address externally. The server is ns-2.hosp.utmck.edu and is
listed as a server in the registration record for utmck.edu. The address
should be 165.6.6.27 but a dig/nslookup from an external site returns
165.6.144.1. We do not have 165.6.144.1 in any of the zone files, but
this address is the external address of a broadband service manager in
our network. Using dig/nslookup on the local network verifies that
165.6.144.1 is not in the zone files or cache of our nameservers. The
name and address of our ns-2 resolve correctly internally. Can someone
please tell me how to identify and correct this problem.
It's probably coming from the glue at the GTLD nameservers:
$ dig +norec +nostats +nocmd anything.utmck.edu @a.gtld-servers.net
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 346
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;anything.utmck.edu. IN A
;; AUTHORITY SECTION:
utmck.edu. 172800 IN NS harley.mc.utmck.edu.
utmck.edu. 172800 IN NS ns-2.hosp.utmck.edu.
;; ADDITIONAL SECTION:
harley.mc.utmck.edu. 172800 IN A 165.6.131.32
ns-2.hosp.utmck.edu. 172800 IN A 165.6.144.1
^^^^^^^^^^^^^
Try fixing your registration there.
--
Chris Thompson
Email: [EMAIL PROTECTED]
_______________________________________________
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
