DNS Setup Taking a Looooong Time


#1

New customer here…Switched from another host…It’s been over 13 hours and my DNS replication has already taken place and all the nameservers are now pointing at the newdream.net ns’s…However, it does not appear that the records have been put into the DNS servers yet.

Anybody else experience problems with this taking a super-long time?


#2

Depending on the registrar (and what top level domain your domain is within), it can take a day or two before the records are updated at the authoritative servers for that TLD. Most TLDs have a 2 day TTL (time to live) for the nameserver records, so even when they update there, some sites may still have the old nameservers for another couple of days after that (unless you get your old provider to delegate the domain to us in the meantime).


#3

Problem is that it seems that the records aren’t even in the nameservers here…

If I do an nslookup and use any of the three ns’s I get an error saying it doesn’t exist…


#4

What’s the domain? We’re not psychic. :>


#5


eesf.com
and evboard.com


#6

Yah - sorry - just got your private message on here.

This has been fixed.

jazz% dig @ns.newdream.net belchak.com

; <<>> DiG 9.3.0s20021217 <<>> @ns.newdream.net belchak.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24121
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;belchak.com. IN A

;; ANSWER SECTION:
belchak.com. 7200 IN A 66.33.213.171

;; AUTHORITY SECTION:
belchak.com. 7200 IN NS ns2.newdream.net.
belchak.com. 7200 IN NS ns3.newdream.net.
belchak.com. 7200 IN NS ns.newdream.net.

;; ADDITIONAL SECTION:
ns.newdream.net. 7200 IN A 66.33.206.6
ns2.newdream.net. 7200 IN A 209.17.93.93
ns3.newdream.net. 7200 IN A 66.33.216.16

;; Query time: 11 msec
;; SERVER: 66.33.206.6#53(ns.newdream.net)
;; WHEN: Wed Feb 5 10:41:45 2003
;; MSG SIZE rcvd: 158

[ same for the others ]