Public nameservers or DNS servers

Posted by Anurag in utilities
Tuesday, October 31. 2006

Many times it happens that we are configuring network on a newly installed machine and forget what the DNS server addresses are.. or when your ISP's dns server just doesnt work.. If you find yourself in such situations frequently then its time you remember these easy to recall public dns servers.

4.2.2.1 - to - 4.2.2.6 (Verizon)
198.6.1.1 - to - 198.6.1.6 (GTI Internet)
128.100.100.128 (University of Toronto)
198.6.1.1 (UUNet)
8.8.8.8 and 8.8.4.4 (Google)

Though i should add a note of caution, use these dns servers to get to the net, search for your ISP's dns servers and add them instead. Its really not a good idea to trample on someone else's bandwidth.. Also while using a third party DNS server, one must understand that its very easy for them to redirect icicibank.com to any server they wish

Its also a good idea to install bind locally to get out of such situations.. in which case the only IP to be added is 127.0.0.1

[Update: Dec 3, 2009]
Google today announced the launch of their own public DNS servers. The IP addresses for using their DNS servers are 8.8.8.8 and 8.8.4.4

Comments (6) - Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

mehul - #1 - 2006-11-01 01:38 - (Reply)

I guess bind running locally is better. That's what I do most of the times cos of the pathetic hathway servers.
Is there any additional configration needed to get better performance?
BTW you mean DNS in the last line instead of IP na? Or is it IP?

Anurag - #1.1 - 2006-11-02 00:03 - (Reply)

yes, its better to run local nameserver, but its just that it will have to query the rootservers everytime for all the domains (which normally can take 3-8 seconds for fresh query) for that reason alone its good to use a popular/heavily used nameserver (like isp's nameserver)

i didnt understand what you meant by DNS in the last line instead of IP? just enter:
nameserver 4.2.2.2
in /etc/resolv.conf that's it!!

mehul - #1.1.1 - 2006-11-02 00:08 - (Reply)

this line in your post - in which case the only [(*IP*) to be added is 127.0.0.1
Is that IP or DNS?
But, my comp is on for almost 24/7 so I guess it's better to run a local nameserver for me. I know about the resolv.conf part. That's how I do it. Try to avoid GUI warna seekhunga kaise. Thoda thoda CLI bhi toh use karna chaiye.

Anurag - #1.1.1.1 - 2006-11-04 18:43 - (Reply)

that's the IP of your dns server. since you are running bind9 locally, all you need to enter in your /etc/resolv.conf is

nameserver 127.0.0.1

err, no.. do this.. System > Administration > Network Admin > DNS > Add > 127.0.0.1

mehul - #1.1.1.1.1 - 2006-11-05 02:56 - (Reply)

OK all rite.
I do know about the System => Networking blah blah blah

Anurag - #2 - 2006-12-02 16:37 - (Reply)

opendns ip address can also be used.

208.67.222.222
208.67.220.220

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. E-Mail addresses will not be displayed and will only be used for E-Mail notifications To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above: Standard emoticons like :-) and ;-) are converted to images. BBCode format allowed
	Remember Information? Subscribe to this entry