Hosts contains a local translation from an url (like reviews.cnet.com) to an ip-address (like 126.96.36.199). It's the first place the browser looks if you type in the url. If it isn't found there, the browser goes on and asks the DNS-server that's configured or assigned to it at the moment (see ipconfig /all).
DNS is just a translation table, distributed all over the Internet. So I think nobody is responsible if any particular DNS-server (or, in your case, probably more of them) doesn't contain the right information temporarily or more permanently.
All you can do is ask the company that hosts the server to get it's DNS on order. Or find another one, if they can't fix it. It's their responsibility to have your sites available to all the world. Definitely not yours. Any lawyer will get all money back you payed them, and more, to cover the costs you make for the switch. Only if just one ISP can't find it (with perhaps a few percent of your customers) it's a problem of that ISP.
- http://www.dnsreport.com/ (compare info for your site with another one)
- maybe (although I found earlier versions to be difficult to use) a freeware program called cyberkit
I am having trouble accessing my company's server (and associated domain names) from different locations. Some computers can see our websites fine, others can't (even without firewall on or site blocking on)
Having been through many DNS discussions with our server hosts and our ISP the only solution that works is to 'hard wire' the IP address and domain names in to WINNT/System32/Drivers/ETC/Hosts file (on PC) or to enter them into the sudo_vi_hosts file (on MAC) to force the domain recognition each time.
Can anyone advise on why this is happening? Obviously we cannot ask our clients to do the above steps just to view our website! Our ISP and server hosts have failed to find any problems their end.
What is a HOST file exactly and is there anyway to get round this?