Archive of UserLand's first discussion group, started October 5, 1998.

Re: DNS problems

Author:Jason Levine
Posted:4/30/1999; 8:23:49 AM
Topic:DNS problems
Msg #:5462 (In response to 5450)
Prev/Next:5461 / 5463


Dig knows how to figure out what the hostname is and what the domain is; the error that I showed is a legitimate error of Network Solutions' root servers not acknowledging the validity of as a domain.

As an example, here's the exact same dig, but using another name server (the name server at Globix, my ISP):

$ dig

; <<>> DiG 2.2 <<>> ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 3, Addit: 3 ;; QUESTIONS: ;;, type = A, class = IN

;; ANSWERS: 86400 A

;; AUTHORITY RECORDS: 86400 NS 86400 NS 86400 NS

;; ADDITIONAL RECORDS: 3600 A 3600 A 3600 A

;; Total query time: 24 msec ;; FROM: aloha to SERVER: ;; WHEN: Fri Apr 30 11:24:33 1999 ;; MSG SIZE sent: 38 rcvd: 179

Now, I get a "NOERROR" response, and the actual IP address of the host.

Note that, as of right now, Columbia's nameservers still don't know anything about -- the DNS change is still propagating. (Also note that this is additional proof that the problem was at the root server level; making a change at that level, and then having it propagate out slowly, as TTLs expire on name servers around the world, is the only way that the problem could still exist in some places and not in others.)


There are responses to this message:

This page was archived on 6/13/2001; 4:49:39 PM.

© Copyright 1998-2001 UserLand Software, Inc.