So, how do DNS work?

[glen]

TW RR is my ISP.
Many times, pages that I am sure are up, such as www.drudgereport.com, give me the DNS failed message.
Then the same thing happens when I use a Trace route utility, I use UOTrace.
If one DNS server is not working for a page, why can't my browser automatically try a different DNS server?
Why does TW RR suck?

 

[pulse8]

<< If one DNS server is not working for a page, why can't my browser automatically try a different DNS server? >>

I believe this is the way it usually works. Most ISPs have more than one DNS server. I believe there might be more free servers out there you can add to your list.

I'm sure someone correct me if I'm totally off the mark.

 

[notfred]

You're browser uses the DNS servers that roadrunner supplies to you. Pacific bell has DNS servers running at 206.13.31.12 and 206.13.28.12 if you want to try those. Your browser doesn't have a list of all the DNS servers on the internet, it has to use the ones that windows knows about. If you're using DHCP, then those are the servers that the DHCP server supplied to you.

 

[glen]

notfred,
Can you elaborate?
I don't understand.
Does MSIE have a built in set of pointers to a set of DNS servers?
IS that in addition to the ones provided by the ISP?
What is DHCP?

 

[pulse8]

DHCP is the connection info you get from your ISP.

It's the gateway, ip address, DNS servers, etc. You'll usually get two DNS servers when your computer gets this info from your ISP. If one doesn't work, your computer will try the next one. It's completely independent of MSIE or any other software. It's built into the OS.

If you're running 2k or XP, go to Start -> Run -> type "cmd" (no quotes) -> click Ok

When it brings up the command prompt, type "ipconfig /all" and you'll see all of the info that's retrieved from TW.

 

[iamwiz82]

your DNS servers are part of your ISP. Most ISPs are now dynamic IPs, which means when you connect to your ISP, their DHCP server(Dynamic Host COnfiguration Protocol) assigns you an IP and then directs you to your DNS server. This DNS servers puts the name of a site with it's address.

example: with DNS typing hotmail.com will take you to hotmail, without, you will get nothing, but if you type 64.4.43.7(hotmail's IP, one of them) it will still take you there.

with DNS you can ping hotmail.com to resolve its IP, without DNS, you could not ping hotmail.com, because your computer doesnt recognize it as an address.

 

[glen]

I am assuming that when a site, like Drudge is up, but I can't get to it, it is a DNS server problem.
I think I confirmed this by using a proxy server to reach the website, so I know it is up.
Now, are there other work arounds?
And, once I am on a site, how do I get the IP?
If I use favorites to save the IP, will that work around "bad" DNS servers?

 

[Descartes]

<< Does MSIE have a built in set of pointers to a set of DNS servers? >>



No, MSIE uses the same information every other network application uses. Usually, you'll have both a primary and secondary dns server associated with a given network interface. If both of these are down, you will no longer have DNS resolution.



<< IS that in addition to the ones provided by the ISP? >>



No, as noted above.



<< What is DHCP? >>



In short, dynamic host configuration protocol works by sending out a broadcast udp packet on port 67 which a dhcp server will grab, fill out all the appropriate fields in the packet (ip address, dns information, and gateway you should use, usually), and send it back to you.

[edit]Damn you all are quick [/edit]

 

[Descartes]

<< I am assuming that when a site, like Drudge is up, but I can't get to it, it is a DNS server problem. >>



Not necessarily. There are countless reasons why you may not be able to access a site.

And, once I am on a site, how do I get the IP?[/i] >>



A few ways to get the IP of a site...

ping it (ping yourdomain.com)
netstat -a (you'll see the connection to yourdomain.com)



<< If I use favorites to save the IP, will that work around "bad" DNS servers? >>



I can't imagine that you would actually have to go through this trouble, as a "bad" DNS server rarely happens, especially with a large ISP. I don't think I've ever had an instance where the DNS servers of my ISP were done, at least not for very long. But, to answer your question, yes, you could do that.