Maybe not a cached page, but you're using cached DNS to get there, surely, as Network Solutions has changed the nameservers (see the whois record or query a root
nameserver) and pointed it at their pending delete page.
Try querying NS1.PENDINGRENEWALDELETION.COM -- query for the A record of any domain at all, and it returns a CNAME to
their little site.
user@server% dig @NS1.PENDINGRENEWALDELETION.COM foofooblahblah.net a
; <<>> DiG 9.2.3rc4 <<>> @NS1.PENDINGRENEWALDELETION.COM foofooblahbla
+h.net a
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40648
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;foofooblahblah.net. IN A
;; ANSWER SECTION:
foofooblahblah.net. 7200 IN CNAME resalehost.networksolu
+tions.com.
resalehost.networksolutions.com. 7200 IN CNAME resalehost.networksolu
+tions.com.
;; Query time: 11 msec
;; SERVER: 216.168.225.129#53(NS1.PENDINGRENEWALDELETION.COM)
;; WHEN: Fri Jan 21 13:35:43 2005
;; MSG SIZE rcvd: 95
UPDATE (Jan 24 2005): It looks like the domain was
renewed by the owner and the nameservers restored, so things
should be back to normal pending any DNS propagation.
|