Welcome to WebmasterWorld Guest from 54.197.171.28

Forum Moderators: buckworks & webwork

Message Too Old, No Replies

dns propagation

dns propagation

   
7:24 pm on Apr 21, 2008 (gmt 0)

5+ Year Member



hi, new here and hope to get some help from you
i have moved some 22 days ago to a new hosting, till now some of my sites doesnt work sometimes, just some of them, the 2 large ones work fine, but the others how i said sometimes no, the webhosting support are telling me that is related with my ISP cache, how i have found in the web the propagation may take no mere than 78 hours, is this possible to take so long for dns propagation please ? 21 days already !
many thanks in advance
12:34 am on Apr 22, 2008 (gmt 0)

5+ Year Member



DNS changes should not take more than 24 hours to fully propagate.
2:24 pm on Apr 22, 2008 (gmt 0)

10+ Year Member



Hi bou3lam and welcome to webmaster world!

i had a similar issue once... turned out to be an issue with the "authorative" dns record or something like that. i'm weak in the dns area. but im pretty sure that might be the problem.

2:43 pm on Apr 22, 2008 (gmt 0)

5+ Year Member



many thanks dbdev
can you please give more explanations, the problem is some of the sites are working sometimes and sometimes no, opening in usa and not in europe
2:56 pm on Apr 23, 2008 (gmt 0)

5+ Year Member



please anyone who had a similr issue :( !
7:24 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



im the only one having this issue in the web history or what :( the webhosting keeping telling me that is isp problem, the isp told me that they update their cache every 12 hours, i dont know what to do:(
9:02 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



check the questionable sites through some proxies, to see if they show properly.
9:15 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



creeking the sites work fine in usa and north america but not in other countries, some of them work here in europe fine, but after some hours they stop responding
9:25 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



who runs the dns?

if your domain registrar offers free dns management, try using that with one of the problem sites.

9:38 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



yes i can change my domains dns, but try what ?
9:56 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



I was thinking, that if you changed nameservers (dns), it might help troubleshoot the problem.

who runs the dns?

10:01 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



godaddy but changing them to what ? :)?
10:50 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



hmmm. that registrar should have good dns. changing should not be necessary. ask their support to look at the dns settings for those problem domains.
11:01 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



godaddy support or my hosting support please ?
11:11 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



godaddy support.
11:14 pm on Apr 24, 2008 (gmt 0)

5+ Year Member



you think the problem my come from them ?
12:21 am on Apr 25, 2008 (gmt 0)

5+ Year Member



just trying to troubleshoot by looking at the possibilities.

good luck.

12:26 am on Apr 25, 2008 (gmt 0)

5+ Year Member



i sent them a mail already, many thanks for your kindless
11:29 am on Apr 29, 2008 (gmt 0)

5+ Year Member



i once had a similar problem long ago, dns wasn changing, i got so fed up with the domain registrar i change the domain registrar and it start working fine, not sure what it was.
you can always try zoneedit.com for free to see if that helps.
4:54 pm on May 4, 2008 (gmt 0)

WebmasterWorld Senior Member jtara is a WebmasterWorld Top Contributor of All Time 5+ Year Member



Technically, DNS changes should not take longer than TTL (time-to-live) to propagate.

Not: 24 hours, 48 hours, or any other fixed figure.

YOU control TTL (or you should, if your registrar or other DNS provider gives you the full control over your records that you should).

If you make a move that is pre-planned, you can reduce TTL to a lower value - say, 5 minutes - then wait for the previous TTL before changing the records. Once you make the change, it should be accomplished within that time (e.g. 5 minutes). Once the lower TTL has expired, you would then kick it back up to the more typical 1-2 days.

A refinement would be to lower the TTL in stages.

Inevitably, some routers will fail to expire their cache, and hang onto the old address. There's nothing you can do about this, though, other than to contact the owner of the router if you can identify the router. (Sometimes possible if it is a major backbone router.) In any case, by reducing the TTL you will find out about any such situation that much sooner.

9:34 pm on May 4, 2008 (gmt 0)

5+ Year Member



thanks a lot , some of the domains was not loading because of a mistake of the webhosting support, some of hem because of my isp , when i nslookup(ed) some of them i god some isp's dns servers not answering
 

Featured Threads

Hot Threads This Week

Hot Threads This Month