How long does it take to take effect changes in name servers? I ask because it is been 12 hours, since i change them from sedo parking to my hosting provider; the changes have not taken place.
Thanks for response,
hq12

Hi,

I have found that they usually take 24-48 hours to totally change over, but sometimes longer. We've had one of our clients change the nameservers of his domain and it took almost a week for the domain to update itself to the new namerservers. It most cases it only takes around 24 hours.

Mr. Anthony, thanks for the response. I appreciate it.

Hi,

No problem. Just trying to help out:).

it might take that long for changing the nameserver for old domain.
But how about for new domain?

i bought a domain(.com) from namecheap yesterday. I heard got reviews for them and decided to move to this registrar(my 1st domain with them). They have great tools and all in nice order.

Usually if i register a .com OR .net domain with other registrars i can start use the domain after 10min - 2 hrs.

But when i check whois information from the day i register until now, it still point to dns1.name-services.com.
whoisguard and registrar lock settings take effect when i check the whois. enable and disable many times.

Why my nameserver doesnt take effect. I set nameserver during registration.
Any idea?

Send a ticket, but still waiting them to reply.
Was thinking to change to dummy nameserver and try again. :P

never mind. i think i make some mistake.
I should update "Transfer DNS to webhost" :P

usually its 5 minutes to sync on the registry side, but upto 72hrs on the ISP side, you can always confirm it by checking the following websites:
www.dnsreport.com
www.dnsstuff.com

usually its 5 minutes to sync on the registry side, but upto 72hrs on the ISP side, you can always confirm it by checking the following websites:
www.dnsreport.com
www.dnsstuff.com

Bashar,

Good tools, do you know of any other useful tools that are free online?

:popcorn:

www.dnscheck.com
www.checkdns.net :)

Wonderful !

How long does it take to take effect changes in name servers? I ask because it is been 12 hours, since i change them from sedo parking to my hosting provider; the changes have not taken place.



What is the TTL on the NS records for the sedo name servers? This is the worst case how long you will have to wait.

There may be a delay at the registrar but overall none of them take 12 hours.
What you are seeing is the caching that is related to the NS records (coming from the glue records).

The root TTL for the NS records (for com and net domains for instance) is 2 days. So by default (if no other name server is found or contacted or can be reached) this will hold in memory for 2 full days.

But if your authoritative name servers is reached then that TTL is used in place. So it can be lower or greater than the TTL on the root namerservers.

Here is an example of the domain "example.com"

We will first query a com root name server you will notice that the TTL is 2 days (86400 * 2 = 172800 )

# dig -t ns example.com @m.gtld-servers.net.

; <<>> DiG 9.2.3 <<>> -t ns example.com @m.gtld-servers.net.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49720
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;example.com. IN NS

;; ANSWER SECTION:
example.com. 172800 IN NS a.iana-servers.net.
example.com. 172800 IN NS b.iana-servers.net.

;; ADDITIONAL SECTION:
a.iana-servers.net. 172800 IN A 192.0.34.43
b.iana-servers.net. 172800 IN A 193.0.0.236



Now we will query the authoritative name server directly:

# dig -t ns example.com @a.iana-servers.net.

; <<>> DiG 9.2.3 <<>> -t ns example.com @a.iana-servers.net.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26943
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;example.com. IN NS

;; ANSWER SECTION:
example.com. 21600 IN NS b.iana-servers.net.
example.com. 21600 IN NS a.iana-servers.net.

;; ADDITIONAL SECTION:
a.iana-servers.net. 21600 IN A 192.0.34.43
b.iana-servers.net. 21600 IN A 193.0.0.236

;; Query time: 99 msec
;; SERVER: 192.0.34.43#53(a.iana-servers.net.)
;; WHEN: Thu Jul 7 00:25:12 2005
;; MSG SIZE rcvd: 109


You will see that the authoritative TTL on the NS records is 21600 (6 hours).

This means that the longest someone will keep going to the old name servers is 6 hours. So even if the registrar makes the change right away in the root name servers people will may have to wait up to 6 hours to every find the new name server to query.

6 hours is actually quite small.
Some authoritative name servers are cheap and set the TTL to 3 to 5 days (save on queries) to save on bandwidth and processing.

Most authoritative name servers are set anywhere from 1 day to 2 days.


But this is why you may get different response times for domains when you change name servers.


Bottom line: It's not always the registrars fault. The previous authoritative name server may have had long TTLs on their NS records.

Thank you very much to each of you for the response. Have a good day.

Atte,

Hq12