Web Hosting Talk







View Full Version : Domain resolves sometimes, other times it does not.


PULSE
06-13-2003, 01:50 PM
Hello:

I'm wondering if anyone has had a similar problem with domains resolving inconsistantly on different ISP's.

I have a few domains registered with Enom, and the websites are on a dedicated server running redhat 7.2.

I use ComCast, and can resolve everything, all of the time. The same is true for Verizon. However, friends of mine using Earthlink and RCN can rarely get to the websites, and usually they get a 'Page Cannot Be Displayed' error.

I have contacted the all parties involved (host, registrar, isp's) and they all blame the other.

I have also run www.dnsreport.com when the site was not accessible (at my friends house) and seen no difference in the results from my own computer.

Has anyone seen this before?

jolly
06-14-2003, 04:29 AM
Its DNS problem of ISP. Best way to cross check is ping the site from diff countries.
:D

yellow_belly
06-14-2003, 07:24 AM
Hi - the one way to make sure it is DNS is to also try accessing the site by its IP address, if it works for just IP then its DNS if it doesnt work for both then its routing.

HTH

YB

Cirtex
06-14-2003, 08:45 AM
Yep, i use Earthlink Cable, usually takes longer for it to resolve for me than my friend using Verizon DSL, but i still love Earthlink's SPEED :D

PULSE
06-14-2003, 09:44 AM
Thank you all.

I thought that the problem was on the IPS's end. Your feedback has been very valuable.

eniki
06-14-2003, 12:04 PM
I had a problem that looked like an ISP problem, but infact I don't think it was.

Have you tired adding A entries for the namerservers the domains are on?

PULSE
06-14-2003, 12:41 PM
Yes, I 99% sure that my DNS settings are correct for the domain.

ToastyX
06-15-2003, 01:53 AM
Originally posted by PULSE
Yes, I 99% sure that my DNS settings are correct for the domain.

What is the domain? I might be able to diagnose the problem. Too many people are quick to blame the ISP experiencing the problem when more often than not, the problem is a DNS misconfiguration on the host's end.

MotleyFool
06-15-2003, 06:13 AM
Very often, domain resolving sometimes and sometimes not is a classical symptom of stale nameservers [i.e you may have 3 nameservers but only 2 have been updated with the latest zone records]

As Toasty said, if you give out the domain some one will help :)