ub3r
02-03-2005, 06:06 PM
so, here's something funny.
-bash-2.05b$ dig sc. ns
; <<>> DiG 9.2.4rc6 <<>> sc. ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62486
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 169419 IN NS TLD1.ULTRADNS.NET.
sc. 169419 IN NS TLD2.ULTRADNS.NET.
sc. 169419 IN NS NS1.NIC.sc.
;; Query time: 44 msec
;; SERVER: 64.81.45.2#53(64.81.45.2)
;; WHEN: Thu Feb 3 13:39:05 2005
;; MSG SIZE rcvd: 92
Run a query at the root servers asking for the nameservers that the .sc ccTLD uses It returns tld1.ultradns.net tld2.ultradns.net and ns1.nic.sc
-bash-2.05b$ dig sc. @tld1.ultradns.net ns
; <<>> DiG 9.2.4rc6 <<>> sc. @tld1.ultradns.net ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41619
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD1.ULTRADNS.NET.
sc. 86400 IN NS TLD2.ULTRADNS.NET.
;; Query time: 3 msec
;; SERVER: 204.74.112.1#53(tld1.ultradns.net)
;; WHEN: Thu Feb 3 13:39:30 2005
;; MSG SIZE rcvd: 70
run the same query at tld1.ultradns.net it only returns tld1.ultradns.net and tld2.ultradns.net .
-bash-2.05b$ dig sc. @tld2.ultradns.net ns
; <<>> DiG 9.2.4rc6 <<>> sc. @tld2.ultradns.net ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57434
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD2.ULTRADNS.NET.
sc. 86400 IN NS TLD1.ULTRADNS.NET.
;; Query time: 8 msec
;; SERVER: 204.74.113.1#53(tld2.ultradns.net)
;; WHEN: Thu Feb 3 13:39:44 2005
;; MSG SIZE rcvd: 70
Run the same query at tld2.ultradns.net it returns the same results: tld1.ultradns.net and tld2.utlradns.net .
-bash-2.05b$ dig sc. @ns1.nic.sc ns
; <<>> DiG 9.2.4rc6 <<>> sc. @ns1.nic.sc ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47569
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD2.ULTRADNS.NET.
sc. 86400 IN NS TLD1.ULTRADNS.NET.
;; ADDITIONAL SECTION:
TLD2.ULTRADNS.NET. 119509 IN A 204.74.113.1
TLD1.ULTRADNS.NET. 119509 IN A 204.74.112.1
;; Query time: 695 msec
;; SERVER: 202.72.100.47#53(ns1.nic.sc)
;; WHEN: Thu Feb 3 13:40:03 2005
;; MSG SIZE rcvd: 102
run that query at ns1.nic.sc, low and behold - it returns the same tld1.ultradns.net / tld2.ultradns.net .
So, now we owners of .sc domains are experiencing wide-spread domain resolution failure in various chunks of the internet.
-bash-2.05b$ dig sc. ns
; <<>> DiG 9.2.4rc6 <<>> sc. ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62486
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 169419 IN NS TLD1.ULTRADNS.NET.
sc. 169419 IN NS TLD2.ULTRADNS.NET.
sc. 169419 IN NS NS1.NIC.sc.
;; Query time: 44 msec
;; SERVER: 64.81.45.2#53(64.81.45.2)
;; WHEN: Thu Feb 3 13:39:05 2005
;; MSG SIZE rcvd: 92
Run a query at the root servers asking for the nameservers that the .sc ccTLD uses It returns tld1.ultradns.net tld2.ultradns.net and ns1.nic.sc
-bash-2.05b$ dig sc. @tld1.ultradns.net ns
; <<>> DiG 9.2.4rc6 <<>> sc. @tld1.ultradns.net ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41619
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD1.ULTRADNS.NET.
sc. 86400 IN NS TLD2.ULTRADNS.NET.
;; Query time: 3 msec
;; SERVER: 204.74.112.1#53(tld1.ultradns.net)
;; WHEN: Thu Feb 3 13:39:30 2005
;; MSG SIZE rcvd: 70
run the same query at tld1.ultradns.net it only returns tld1.ultradns.net and tld2.ultradns.net .
-bash-2.05b$ dig sc. @tld2.ultradns.net ns
; <<>> DiG 9.2.4rc6 <<>> sc. @tld2.ultradns.net ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57434
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD2.ULTRADNS.NET.
sc. 86400 IN NS TLD1.ULTRADNS.NET.
;; Query time: 8 msec
;; SERVER: 204.74.113.1#53(tld2.ultradns.net)
;; WHEN: Thu Feb 3 13:39:44 2005
;; MSG SIZE rcvd: 70
Run the same query at tld2.ultradns.net it returns the same results: tld1.ultradns.net and tld2.utlradns.net .
-bash-2.05b$ dig sc. @ns1.nic.sc ns
; <<>> DiG 9.2.4rc6 <<>> sc. @ns1.nic.sc ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47569
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;sc. IN NS
;; ANSWER SECTION:
sc. 86400 IN NS TLD2.ULTRADNS.NET.
sc. 86400 IN NS TLD1.ULTRADNS.NET.
;; ADDITIONAL SECTION:
TLD2.ULTRADNS.NET. 119509 IN A 204.74.113.1
TLD1.ULTRADNS.NET. 119509 IN A 204.74.112.1
;; Query time: 695 msec
;; SERVER: 202.72.100.47#53(ns1.nic.sc)
;; WHEN: Thu Feb 3 13:40:03 2005
;; MSG SIZE rcvd: 102
run that query at ns1.nic.sc, low and behold - it returns the same tld1.ultradns.net / tld2.ultradns.net .
So, now we owners of .sc domains are experiencing wide-spread domain resolution failure in various chunks of the internet.
