Page 3 - Help on DNS issue

hmmm..now I seem to back at where I was when I first came here. Wouldn't worry me if it was just my isp, but everyone that has had this problem has a different isp than me..

Oh well...I guess I will just have to live with it. May change all my links round to ip as I never have the problem when I direct people to use ip address instead of name.

Thanks for you help anyway

Well you could always change DNS hosts and see if that works.

I had another idea too. Do you have access to manipulating the TTL of your NS records? if not, then you definately need to change domain hosts.

I'll take that into consideration...thanx

nah, take it under more than simple consideration. I had finally decided to throw your domain into a very useful tool called dnsreport. It had only one significant thing to say about your domain and that was related to TTL values. It said that this was a potential serious problem. It's the only thing it ever mentions that I had no previous knowledge of. I quote:

----------------------
NS TTL discrepancy

Warning: Your NS records at your authoritative DNS servers have TTLs that do not match what the parent servers report:

ns4.aaawebonline.net. [TTL 172800 at parent; 14400 at 63.247.74.137]
ns3.aaawebonline.net. [TTL 172800 at parent; 14400 at 63.247.74.137]

In some cases, this can cause some serious problems. For example, if the parent servers have a 172800 second TTL (48 hours), and your authoritative DNS servers report a TTL of 3600 seconds (1 hour), you are saying that the parent DNS servers do not have the correct information. But, after 1 hour your DNS records may time out. At that point a DNS resolver will need to get fresh NS records. This can cause a serious problem in some cases.
----------------------

This is the only possible thing I can see that could be wrong. TTL values is the one thing DNS Crawler does not display, so I keep missing this one. So it's a choice between a broken domain or switching services. If you wish, you can contact the owner of that server and see if they'll fix it.

Would you believe I actually used that tool before coming to this forum, and sent the results to my host..who came back and said it wasn't the problem..and pointed out a little clause that was at the bottom of the DNS report..




But I think I will push this issue with him again..and tell him to fix that. What I have got to loose. I'll let you know how I get on.

oh yeah, that wasn't the only warning on there. But it was the only warning I would call significant. It has a poor idea of what's fatal and whats a warning I think. I just read what it has to say and determine for myself what's important. Ordinarily I would ignore that warning also, but you're having problems and I haven't a clue what else it could be. Setting TTL values on your NS records is painless. I did it for my domains, he can do it for yours if he wants your business.

Besides, it used the words "possible" and "often" in that quote of yours. I think you meet the "possible" and "rare".

TTL values have now been changed, so will see how we go from here...

Oh well, if nothing else, tis a good learning session