beethoven
msg:3631892 | 12:34 am on Apr 22, 2008 (gmt 0) |
DNS changes should not take more than 24 hours to fully propagate.
|
dbdev
msg:3632316 | 2:24 pm on Apr 22, 2008 (gmt 0) |
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.
|
bou3lam
msg:3632347 | 2:43 pm on Apr 22, 2008 (gmt 0) |
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
|
bou3lam
msg:3633252 | 2:56 pm on Apr 23, 2008 (gmt 0) |
please anyone who had a similr issue :( !
|
bou3lam
msg:3634424 | 7:24 pm on Apr 24, 2008 (gmt 0) |
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:(
|
creeking
msg:3634505 | 9:02 pm on Apr 24, 2008 (gmt 0) |
check the questionable sites through some proxies, to see if they show properly.
|
bou3lam
msg:3634514 | 9:15 pm on Apr 24, 2008 (gmt 0) |
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
|
creeking
msg:3634516 | 9:25 pm on Apr 24, 2008 (gmt 0) |
who runs the dns? if your domain registrar offers free dns management, try using that with one of the problem sites.
|
bou3lam
msg:3634529 | 9:38 pm on Apr 24, 2008 (gmt 0) |
yes i can change my domains dns, but try what ?
|
creeking
msg:3634545 | 9:56 pm on Apr 24, 2008 (gmt 0) |
I was thinking, that if you changed nameservers (dns), it might help troubleshoot the problem. who runs the dns?
|
bou3lam
msg:3634549 | 10:01 pm on Apr 24, 2008 (gmt 0) |
godaddy but changing them to what ? :)?
|
creeking
msg:3634582 | 10:50 pm on Apr 24, 2008 (gmt 0) |
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.
|
bou3lam
msg:3634592 | 11:01 pm on Apr 24, 2008 (gmt 0) |
godaddy support or my hosting support please ?
|
creeking
msg:3634600 | 11:11 pm on Apr 24, 2008 (gmt 0) |
godaddy support.
|
bou3lam
msg:3634603 | 11:14 pm on Apr 24, 2008 (gmt 0) |
you think the problem my come from them ?
|
creeking
msg:3634634 | 12:21 am on Apr 25, 2008 (gmt 0) |
just trying to troubleshoot by looking at the possibilities. good luck.
|
bou3lam
msg:3634636 | 12:26 am on Apr 25, 2008 (gmt 0) |
i sent them a mail already, many thanks for your kindless
|
MiniAlex
msg:3637506 | 11:29 am on Apr 29, 2008 (gmt 0) |
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.
|
jtara
msg:3641498 | 4:54 pm on May 4, 2008 (gmt 0) |
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.
|
bou3lam
msg:3641617 | 9:34 pm on May 4, 2008 (gmt 0) |
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
|
|
