Question about strange DNS issues

Hello,

Some customers are reporting that our site is inaccessible while the majority have no problems. This is what the DNS entries look like for those that cannot access however:


saeven@saevenstar:~$ dig whoiscart.net @ns1.prtc.net

; <<>> DiG 9.2.2-P3 <<>> whoiscart.net @ns1.prtc.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22028
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0

;; QUESTION SECTION:
;whoiscart.net. IN A

;; AUTHORITY SECTION:
net. 36747 IN NS B.GTLD-SERVERS.net.
net. 36747 IN NS C.GTLD-SERVERS.net.
net. 36747 IN NS D.GTLD-SERVERS.net.
net. 36747 IN NS E.GTLD-SERVERS.net.
net. 36747 IN NS F.GTLD-SERVERS.net.
net. 36747 IN NS G.GTLD-SERVERS.net.
net. 36747 IN NS H.GTLD-SERVERS.net.
net. 36747 IN NS I.GTLD-SERVERS.net.
net. 36747 IN NS J.GTLD-SERVERS.net.
net. 36747 IN NS K.GTLD-SERVERS.net.
net. 36747 IN NS L.GTLD-SERVERS.net.
net. 36747 IN NS M.GTLD-SERVERS.net.
net. 36747 IN NS A.GTLD-SERVERS.net.

;; Query time: 138 msec
;; SERVER: 196.28.61.145#53(ns1.prtc.net)
;; WHEN: Sat Apr 17 11:45:32 2004
;; MSG SIZE rcvd: 252
Is this the famous bind 9.1 verisign hijack for which a patch exists on later versions?

Cheers.
Alex

 

 

 

 

Top