


$ dig badconnections.net NS
; <<>> DiG 9.2.1 <<>> badconnections.net NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13903
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;badconnections.net. IN NS
;; ANSWER SECTION:
badconnections.net. 109767 IN NS ns1.badconnections.net.
badconnections.net. 109767 IN NS www.badconnections.net.
;; ADDITIONAL SECTION:
ns1.badconnections.net. 109767 IN A 65.28.8.144
www.badconnections.net. 109767 IN A 65.28.11.91
;; Query time: 3 msec
;; SERVER: 192.168.0.3#53(192.168.0.3)
;; WHEN: Sun May 18 08:37:38 2003
;; MSG SIZE rcvd: 104
$ dig @65.28.11.91 www.badconnections.net
; <<>> DiG 9.2.1 <<>> @65.28.11.91 www.badconnections.net
;; global options: printcmd
;; connection timed out; no servers could be reached
dig @65.28.8.144 www.badconnections.net
; <<>> DiG 9.2.1 <<>> @65.28.8.144 www.badconnections.net
;; global options: printcmd
;; connection timed out; no servers could be reached





ThePreacher wrote:I assume that I must change my host server information before my site will be visible to the internet again. Otherwise I followed your directions and within 72 hours I should know whether everything is working. By the way my secondary dns server is down, so I pointed ns2.badconnections.net at 65.28.11.91 as well.

Users browsing this forum: No registered users and 0 guests