I'm having a problem with domain resolution. I changed nameservers more than 48 hours ago. Domain has resolved on all of my servers on EV1 network as well as in another provider's datacenter in NYC. The problem is that domain doesn't resolve on my home computer that is connected to the Internet through Earthlink cable modem. I'm just wondering how that's possible and what I should do to fix the problem.

I tried using my server's IP address as DNS server for my home cable modem instead of default DHCP DNS server. Then, domain resolves correctly. However, default DHCP DNS server just doesn't recognize the new nameservers. I also tried using some other IP addresses as DNS server at home. They all resolve domain correctly too.

you maybe victim a long dns caching on your ISP side

try checking the status of the domain with the available tools at http://dnsstuff.com

regards

I am having the exact same problems. I had a Ensim server and just upgraded to Plesk box. So I setup new DNS servers on the Plesk server 1.5 weeks ago and users from Comcast and Earthlink can not get to my site. I can't even test their name servers because it won't allow me to connect to them.

I don't know what to do about this situation, it is quite frustrating. One of the domains I am having trouble with would be www.rc10b4.com.

It's a DNS caching issue at the local ISP Joor. There's really not a lot you can do about that, other than possibly complain to them. If you still have the old server you can change the DNS on that so that it points to the new server's IP's and that'll get it to resolve correctly for everybody, even if their ISP hasn't updated their DNS Cache yet.

Another thing I do, just so that I can see things immediately, is tweak the "hosts" file on my own computer so that it connects directly to the server IP's. The location of that file is going to depend upon your operating system, but a search on one of the search engines should get you instructions on doing that.

Thank you for the help, I just learned about the hosts file yesterday, typically I just change my DNS servers in XP but the hosts file is better in my opinion.

I found out the actual problem, it was 1 of these two things. Plesk by default when adding a domain name uses CNAME for the www instead of an A record. From what I have learned this is not typical practice (and I am using Plesk to setup my nameservers). The other thing I changed was in KISS 2.0 Firewall there was some code I needed to uncomment that allowed older bind servers pull data off. Those two things have fixed my issue and people can get tot he site now.

ahh...that could do it. Especially the Firewall blocking dns. Doing the www version of the site via CNAME shouldn't be much of an issue though.

FWIW, I also use my hosts file for blocking all of those little spyware/scumware, tracking, ads and other parasites one encounters out there on the wild, wild 'net. Works pretty darned well too!

Can you give me some more info about the server settings?

I've had a box for a few months now and it is strange for week or longer I can domains on the box then they will stop working. If I switch DNS servers on my local computer to different ones it might work for another week and then stop. I can then go back to the default ones my provider provides and it will work again. Back and forth. I had TSS setup the box. They say nothing is wrong but something has to be wrong since I can not access my sites.

I've tried ipconfig /flushdns and like I said switching my DNS servers to public ones the sites will work for so long and then stop.

Any help would be great.

Mark