Hi, well at last (after 5 days) register.com changed over the registered IP of my primary nameserver. This threw my plans for a graceful transition completely out the window, and the domains I am dns hosting on my server are not resolving at the moment.

dig tells me that I have a "Bad Server"

<<>> DiG 8.3 <<>> @ 209.123.61.15 cool.as
; Bad server: -- using default server and timer opts
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server default -- 209.123.167.10: Connection timed out

I don't know what the problem is. This problem has come up with the new IP number. Alas, my secondary name server is still registered to the old ip number so I know that trying to query NS2.NEATURL.COM will not work. I have just put in a ticket with register.com to change the IP for this one (as the old IP no longer reaches my server). Let's see if they can do this change in under five days?

Anyone have any ideas why my name server is so "bad"? :(

If it helps, here is my zone file for neaturl.com which is on the server

$ttl 38400
neaturl.com. IN SOA dylan.neaturl.com. hostmaster.neaturl.com. (
1003018251
10800
3600
432000
38400 )
neaturl.com. IN NS dylan.neaturl.com.
neaturl.com. IN MX 10 mail.neaturl.com.
neaturl.com. IN A 209.123.61.15
ns2.neaturl.com. IN A 64.247.26.192
ns3.neaturl.com. IN A 209.123.61.40
ns4.neaturl.com. IN A 209.123.61.39
*.neaturl.com. IN A 209.123.61.15
dylan.neaturl.com. IN A 209.123.61.15
ns1.neaturl.com. IN A 209.123.61.15

Don't worry I followed the golden rule:

REBOOT!

:)

Seemed to fix whatever the problem was.