[therocket954]

Hey guys.... thanks in advance for any help.. or even opinions!

I have a site www.exceptionalmetals.com that the company has chosen to host through a local company here in Saginaw, MI.

The hosting company says that all the DNS settings are correct. However the domain doesn't resolve if you try and visit the site without the "www" prefix. (Or trying to ping the site, I get the same results)

I've tried it at work and at home and it doesn't resolve either way... the website is not new, and we haven't made any changes to the hosting company or hosting services. I'm not sure how long this hasn't been working, I just noticed this and trying to correct it.

Correct me if I'm wrong, but isn't DNS settings all controlled by the web host? As the developer I don't know what I can do to fix it.

Any help would be greatly appreciated!

[bizzar528]

Depending on how your hosting is configured, you can make changes to your dns. In this case, the host is responsible for the settings, but it is the registrar that is responsible for making sure those changes are sent to the root servers and distributed accordingly. Typically, heavy duty dns changes can take 24-72 hours depending on your registrar and what changes with your dns.

An alternative is to use your registrar for a dns host. Most include some type of dns management of host records. i have seen a few thought that don't so it's a matter of who you registered your domain at. But the biggies like enom, network solutions, and godaddy have management tools.

By the way, I was able to resolve www.exceptionalmetals.com and exceptionalmetals.com to 68.22.255.180 if that's the right IP.

[mab]

I tried both versions of the url and reached the web site using both.

I checked at www.dnsreport.com and there are no basic problems with the A (host) records for the domain or the www.domain. http://www.dnsstuff.com/tools/dnsrep...onalmetals.com

There is an issue with a TCP connection that could be causing the symptoms you describe, if you happen to be behind routers/firewalls that are blocking UDP packets.

Other than that, it would indicate that you might have a cached DNS setting that is incorrect or corrupted. Perhaps a virus has put a setting into a LMHOSTs file on the computers you have been trying to connect with.

[therocket954]

Excellent. Thank you guys so much! You've both been very helpful and got me pointed in the right direction. (Before I hadn't a clue where to even start)

I've bookmarked that dnsreport.com Might come in handy again sometime.

Thanks!