ForumGarden

We installed DNS on a 2003 server on Thursday. Saturday morning I got a call that reporters couldn't get onto the internet to update the news, right?

I had no trouble connecting remotely, yet once inside, was unable to browse anywhere in the greater world beyond our walls...

The pisser is that the damned thing was working fine all day Friday. And after I changed my preferred DNS server to point back to its old settings...voila!

Went to work and changed everyone... everyone was fine.. now I get paged 15 minutes ago that they can't get online or get email..

I just got in fine, but once again cannot browse beyond the building...

Assuming that I am a moron, can someone tell me what the heck is going on? :-5:-5

Don't everyone jump on this at once...:rolleyes:



:wah:

Is DNS the new TV stuff? I still have black and white sets............:wah:

I found this, dunno if it will help?

To find out whether DNS is a potential culprit when you're having trouble connecting to a site, first ping the site to which you can't connect by issuing the ping command at the command prompt, like this:

ping www.computerworld.com

If the site is live, you'll get an answer like this (Note: text below has line breaks inserted to fit into the Web page display):

Pinging www.computerworld.com

[65.221.110.98] with 32 bytes of data:

Reply from 65.221.110.98: bytes=32

time=22ms TTL=235

Reply from 65.221.110.98: bytes=32

time=23ms TTL=235

Reply from 65.221.110.98: bytes=32

time=23ms TTL=235

Reply from 65.221.110.98: bytes=32

time=24ms TTL=235

Ping statistics for 65.221.110.98:

Packets: Sent = 4, Received = 4,

Lost = 0 (0% loss),

Approximate round trip times in

milli-seconds:

Minimum = 22ms, Maximum = 24ms,

Average = 23ms

If it's not, you'll get a response like this:

Ping request could not find host.

Please check the name and try again.If you ping a site and it's live but you can't connect to it with your browser, a DNS problem might be the reason. If you suspect you're having a DNS problem, take the following actions:

Check your HOSTS file

If your HOSTS file contains an incorrect or outdated listing, you won't be able to connect. Even if you don't recall adding listings to a HOSTS file, it still might contain listings, because some Internet accelerator utilities edit them without telling you. Open your HOSTS file with Notepad and see if the site you can't connect to is listed there. If it is, delete the entry, and you should be able to connect.



Check your DNS settings

Make sure your DNS settings are correct for your ISP or network. If you've changed your DNS settings to use a service such as OpenDNS, for example, you might have entered them incorrectly.

Find out from your ISP or network administrator what your DNS settings are supposed to be, or check the OpenDNS site (or another DNS service) for their server settings. Once you've done that, you'll need to make sure that you've entered the DNS settings properly.

Then change the DNS servers to the proper ones, or choose "Obtain DNS server address automatically" if your ISP or network administrator tells you to use that setting.

Flush your DNS cache

The problem might be related to your DNS cache, so flush it out. To flush the cache, type ipconfig /flushdns at a command prompt.

Find out if your ISP is having DNS problems

Your ISP could be the source of the problem. One possibility is that one of its DNS servers is down and you're trying to access the downed server. If you know the addresses of the DNS servers, ping each of your ISP's DNS servers, and if any of them don't respond, remove them from your DNS list.

If you don't know the address of the DNS servers and you're supposed to use the choose "Obtain DNS server address automatically" setting, you'll have to call your ISP to see whether its DNS servers are having problems. Alternately, you can use the OpenDNS servers instead of your ISP's DNS servers.

Dunno if it helps im not up on DNS im afraid Diane