I don't prefer it but I had to repeat my question,so here goes:
For using OpenDNS,should we use the instructions for Linux/Unix or for routers since the desktop is basically a machine on the private network while the router is the one which handles DNS addresses?
Regards, Easwar
Easwar Hariharan wrote:
I don't prefer it but I had to repeat my question,so here goes:
For using OpenDNS,should we use the instructions for Linux/Unix or for routers since the desktop is basically a machine on the private network while the router is the one which handles DNS addresses?
For Linux/Unix. http://www.opendns.com/start/unix.php
Regards.
Easwar Hariharan wrote: I don't prefer it but I had to repeat my question,so here goes:
For using OpenDNS,should we use the instructions for Linux/Unix or for routers since the desktop is basically a machine on the private network while the router is the one which handles DNS addresses?
Here is how I did local DNS cache with OpenDNS.
Hope others find it helpful.
// File /var/named/chroot/etc/named.conf
options { ..... ..... forward first; forwarders { 208.67.222.222 ; 208.67.220.220 ; }; };
// OpenDNS redirects www.google.com to their own server // http://blog.opendns.com/2007/05/22/google-turns-the-page/ // I do NOT like it, so following stops/corrects it
zone "google.com" { type forward; forwarders { 216.239.32.10; 216.239.34.10; 216.239.36.10; 216.239.38.10; }; forward only; };
zone "l.google.com" { type forward; forwarders { 209.85.139.9; 64.233.179.9; 64.233.161.9; 66.249.93.9; 209.85.137.9; 72.14.235.9; 64.233.167.9; }; forward only; };
Amish.
On 8/25/07, Amish Mehta amish.misc+ilug@gmail.com wrote:
Easwar Hariharan wrote: I don't prefer it but I had to repeat my question,so here goes:
For using OpenDNS,should we use the instructions for Linux/Unix or for routers since the desktop is basically a machine on the private network while the router is the one which handles DNS addresses?
Here is how I did local DNS cache with OpenDNS.
This is valid if you are running bind. Following the instructions at openDNS' page replaced mtnl's ip's with openDNS' addresses.
I added this line in dhclient.conf: prepend domain-name-servers 208.67.222.222,208.67.220.220;
My resolv.conf got overwritten accordingly: $ cat /etc/resolv.conf ### BEGIN INFO # # Modified_by: NetworkManager # Process: /usr/bin/NetworkManager # Process_id: 2967 # ### END INFO
nameserver 208.67.222.222 nameserver 208.67.220.220 nameserver 10.0.0.1
A sample traceroute to google.com traceroute to google.com (72.14.207.99), 30 hops max, 40 byte packets 1 10.0.0.1 (10.0.0.1) 0.630 ms 0.584 ms 0.621 ms 2 * * * 3 * * * 4 triband-mum-59.185.0.66.mtnl.net.in (59.185.0.66) 12.255 ms 13.138 ms 1 4.431 ms 5 59.160.0.138.static.vsnl.net.in (59.160.0.138) 15.198 ms 20.514 ms 21.3 68 ms 6 59.163.16.130.static.vsnl.net.in (59.163.16.130) 302.479 ms 303.239 ms 305.642 ms 7 * * * 8 209.85.130.8 (209.85.130.8) 290.823 ms 209.85.130.4 (209.85.130.4) 301.786 ms 209.85.130.8 (209.85.130.8) 294.364 ms 9 64.233.174.81 (64.233.174.81) 352.255 ms 352.909 ms 352.368 ms 10 72.14.236.20 (72.14.236.20) 371.041 ms 374.666 ms 375.442 ms 11 72.14.232.113 (72.14.232.113) 380.517 ms 381.600 ms 72.14.236.183 (72.14. 236.183) 382.507 ms 12 72.14.236.134 (72.14.236.134) 372.076 ms 66.249.94.50 (66.249.94.50) 379.8 67 ms 376.119 ms 13 eh-in-f99.google.com (72.14.207.99) 386.124 ms 386.976 ms 387.392 ms
Regards, Mohan S N
-
Amish Mehta -
Easwar Hariharan -
Mohan Nayaka -
Rohit V Bhute