Different results returned from GTLD, actual name servers

Dennis Julien djulien at mail.cloakware.com
Tue Dec 2 18:32:26 UTC 2003


X-no-archive: yes


Dearest bind-users:

I've got a strange problem that I'm hoping someone can shed some light on.  
Please see the footnote examples at the bottom of this message for dig 
results.

It seems that the GTLD group of servers[1] return different results for
'www.cloakware.com' than the primary/secondary name servers that hold
records for the domain[2], [3], [4].  The correct IP is 206.191.60.52,
whereas GTLD returns 207.61.93.166.

The 207.61.93.166 IP (formerly 'www.cloakware.com') was indeed a name
server for the domain in a previous life.  That information was changed at
the registrar months ago (presumably more than long enough for any
propogation to occur.  As far as I can tell, there is no domain (.com or
otherwise) that still references 'www.cloakware.com' as a name server --
yet GTLD won't let it go.

Network Solutions (I know, I know...) insists that things will
miraculously cure themselves in "45 to 90 days", but I'm skeptical.

Any help, recommendations, or suggestions would be sincerely appreciated.

__
Dennis


--[1]-----------
# dig @A.GTLD-SERVERS.NET www.cloakware.com

; <<>> DiG 9.2.1 <<>> @A.GTLD-SERVERS.NET www.cloakware.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35775
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;www.cloakware.com.             IN      A

;; ANSWER SECTION:
www.cloakware.com.      172800  IN      A       207.61.93.166
----------------

--[2]-----------
# dig @ns1.cloakware.com www.cloakware.com

; <<>> DiG 9.2.1 <<>> @ns1.cloakware.com www.cloakware.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57394
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;www.cloakware.com.             IN      A

;; ANSWER SECTION:
www.cloakware.com.      86400   IN      A       206.191.60.52
----------------

--[3]-----------
# dig @ns2.cloakware.com www.cloakware.com

; <<>> DiG 9.2.1 <<>> @ns2.cloakware.com www.cloakware.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21793
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3

;; QUESTION SECTION:
;www.cloakware.com.             IN      A

;; ANSWER SECTION:
www.cloakware.com.      86400   IN      A       206.191.60.52
----------------

--[4]-----------
# dig @mag2.magmacom.com www.cloakware.com

; <<>> DiG 9.2.1 <<>> @mag2.magmacom.com www.cloakware.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24126
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;www.cloakware.com.             IN      A

;; ANSWER SECTION:
www.cloakware.com.      86400   IN      A       206.191.60.52
----------------



More information about the bind-users mailing list