| Author |
Message |
klhrevolutionist

Joined: 08 Jun 2005 Posts: 1124
|
Posted: Thu 15 Feb 2007, 21:23 Post subject:
How to specify which DNS servers your browser will use Subject description: OpenNic, OpenDNS and more |
|
Update your /etc/resolv.conf file by deleting the current contents adding these lines
nameserver 208.67.222.222
nameserver 63.226.12.96
nameserver 72.3.208.251
The first nameserver is that of OpenDNS: www.opendns.com
The second is that of OpenNIC: www.opennic.unrated.net
The third nameserver is UnifiedRoot: www.unifiedroot.com
open terminal and type w/out the quotation marks "cp /etc/resolv.conf /etc/resolv.conf.txt" restart your web browser for changes to take effect.
Now open /etc/rc.d/rc.local with your fav text editor (leafpad)
and add the following lines:
rm /etc/resolv.conf
cp /etc/resolv.conf.txt /etc/resolv.conf
It might be a good idea to make dhcp use the "-R" option when executing. Enjoy the rest of the web !
_________________ Heaven is on the way, until then let's get the truth out!
Last edited by klhrevolutionist on Sat 10 Nov 2007, 21:20; edited 1 time in total
|
|
Back to top
|
|
 |
GuestToo
Puppy Master
Joined: 04 May 2005 Posts: 4078
|
Posted: Thu 15 Feb 2007, 21:36 Post subject:
|
|
you could configure the resolv.conf file then turn off the writable permissions ... it's very easy using Rox 2.5 ... right click the file and click Properties ... or you can type:
chmod a-w /etc/resolv.conf
it might also work to keep a backup copy of the file, and copy it back every time Puppy boots ... for example, you might put something like this in rc.local:
cp -f /etc/resolv.confBAK /etc/resolv.conf
but it might be over written when you connect to the internet
opendns.com is very useful if your connection is not working and you are not sure whether it is a dns problem or not ... if you put the addresses of the opendns servers in resolv.conf, you connection should immediately start working if it is a dns problem ... if it doesn't help, it's probably something else
|
|
Back to top
|
|
 |
brad_chuck
Joined: 15 Aug 2005 Posts: 284 Location: Appalachian Mountains
|
Posted: Fri 16 Feb 2007, 16:14 Post subject:
worked for me |
|
This improved my speed a LOT!
I guess my ISP had a slow DNS server! ( Cable )
1. change files
2. edit "Properties" with ROX
3. restart web browser
|
|
Back to top
|
|
 |
klhrevolutionist

Joined: 08 Jun 2005 Posts: 1124
|
Posted: Fri 16 Feb 2007, 17:25 Post subject:
|
|
I changed permissions as well..
The file /etc/resolve.conf however gets overwritten so some kind of work a round is needed for that. I use 1.0.9 so not sure if that occurs in the newer pups..
_________________ Heaven is on the way, until then let's get the truth out!
|
|
Back to top
|
|
 |
GuestToo
Puppy Master
Joined: 04 May 2005 Posts: 4078
|
Posted: Fri 16 Feb 2007, 19:21 Post subject:
|
|
ok, you could play hardball and make the file immutable:
1) configure /etc/resolv.conf
2) chmod a-w /etc/resolv.conf
3) chattr +i /etc/resolv.conf
to set the permissions so that /etc/resolv.conf can be deleted or written to again:
1) chattr -i /etc/resolv.conf
2) chmod +w /etc/resolv.conf
immutable files
|
|
Back to top
|
|
 |
klhrevolutionist

Joined: 08 Jun 2005 Posts: 1124
|
Posted: Sat 10 Nov 2007, 21:23 Post subject:
|
|
Updated: post bump please read the first post: http://murga-linux.com/puppy/viewtopic.php?search_id=188696918&t=15464
_________________ Heaven is on the way, until then let's get the truth out!
|
|
Back to top
|
|
 |
Wolf Pup
Joined: 27 Apr 2006 Posts: 637
|
Posted: Sun 11 Nov 2007, 01:44 Post subject:
|
|
One can also create a script called "ip-up" in /etc/ppp
| Code: | # DNS servers
echo "nameserver 208.67.222.222" > /etc/resolv.conf
echo "nameserver 63.226.12.96" >> /etc/resolv.conf
echo "nameserver 72.3.208.251" >> /etc/resolv.conf |
this will update /etc/resolv.conf every time a PPP connection is brought up.
_________________
Visit The Repository - Helpful and hard-to-find treats for Puppy 3.
Click Here for Puppy Support Chat, + Helpful Links.
|
|
Back to top
|
|
 |
JustGreg
Joined: 24 May 2005 Posts: 651 Location: Connecticut USA
|
Posted: Tue 13 Nov 2007, 19:53 Post subject:
Subject description: It does work! |
|
I changed my /etc/resolv.cong to have the IP addresses given by kihrevolutionist. I also made the changed file immutable using the commands listed by GuestToo. It does help to speed things up. This does say something about the DNS services of the ISP. I did check by doing a reboot and connect to ensure that /etc/resolv.conf did not change. There were no changes. Thanks for the tip!
_________________ Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
|
|
Back to top
|
|
 |
tubeguy

Joined: 28 Aug 2009 Posts: 1278 Location: Park Ridge IL USA
|
Posted: Fri 28 Aug 2009, 21:16 Post subject:
Worked for me too |
|
Thanks very much for this!
Puppy 4.2
Toshiba Satellite A25-S207
Network
IP Connections
Connections
127.0.0.1:631 LISTEN 0.0.0.0:* tcp
192.168.0.100:38669 ESTABLISHED 209.85.225.17:443 tcp
192.168.0.100:54827 ESTABLISHED 209.85.225.19:443 tcp
0.0.0.0:631 0.0.0.0:* udp
DNS Servers
Name servers
208.67.222.222
63.226.12.96
72.3.208.251
|
|
Back to top
|
|
 |
puppyite

Joined: 23 Jul 2009 Posts: 758 Location: U.S., Midwest, Central Time Zone, GMT-6
|
Posted: Sat 29 Aug 2009, 11:07 Post subject:
|
|
In order to know how fast or slow a given DNS is via my ISP at my current geographic location I find it useful to test it in the CLI with the following command:
ping 63.226.12.96
To limit the number of pings sent to five add: -c 5
ping -c 5 63.226.12.96
To discover who owns a given DNS you can do a reverse IP lookup at ZoneEdit. Other sites offer this free service too. Be certain not to enter anything but the IP address in the search field at ZoneEdit or the search will be invalid.
I prefer to use the primary and secondary DNS from a single company. One possibility is OpenDNS:
208.67.222.222
208.67.220.220
Obviously you may use any DNS that is available to you and not just those supplied by your ISP.
As of this writing ping reports 0 packets received, 100% packet loss for 72.3.208.251 but YMMV.
_________________ Learn more about Puppy Linux: Puppy Linux FAQ
Protect your privacy: Scroogle.org - Ixquick
|
|
Back to top
|
|
 |
henryfranz2005
Joined: 26 Sep 2009 Posts: 35 Location: Philippines
|
Posted: Sat 10 Oct 2009, 09:51 Post subject:
|
|
nice one ! thanks for this!
|
|
Back to top
|
|
 |
Helghan
Joined: 26 Apr 2010 Posts: 2
|
Posted: Tue 27 Apr 2010, 08:08 Post subject:
|
|
wow; just WOW it worked
I added
nameserver 208.67.222.222
nameserver 63.226.12.96
nameserver 72.3.208.251
and now I can use the browser, why is information like this not easier to find?, I had to check a trillion threads on this, tried almost everything, but here we have a thread from 2007 and it fixed my problem, jesus.
Anyway..WOO!, anyone having problems with puppy linux 4.3.1, where it connects success over wireless, but the net browser doesn't work, put these values into /etc/resolv.conf and save.
Still blows my mind how long it took just to get the internet working.
|
|
Back to top
|
|
 |
edoc

Joined: 07 Aug 2005 Posts: 3938 Location: Southeast Georgia, USA
|
Posted: Fri 02 Jul 2010, 12:00 Post subject:
|
|
Anyone tried these tweaks with Wary 030?
I understand that opendns includes content filtering - does that all have to be set up manually or is there an existing "system" somewhere that blocks the garbage?
_________________ Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Multiple computers - currently running Puppy Exprimo ver. 5x15
|
|
Back to top
|
|
 |
edoc

Joined: 07 Aug 2005 Posts: 3938 Location: Southeast Georgia, USA
|
Posted: Tue 06 Jul 2010, 09:23 Post subject:
|
|
The only non-commercial/open-source content filtering for Linux I have found is router-based, in my case for a Netgear WNR3500L.
The problem is that while the Netgear marketeers found it profitable to market the device as open-source they are not only ill-equipped to answer questions their reps on their support forum can be downright surly about anyone using anything other than a proprietary MS version of windows.
The comment from one was "If you insist on using Linux then you ought to be able to figure it out."
Anyhow, OpenDNS appears to have the capacity in some cases of speeding Internet performance (as prior posts have demonstrated) and to serve as the basis for content filtering.
I have not yet succeeded with either because I first have to resolve a corrupted save file ... sigh.
_________________ Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Multiple computers - currently running Puppy Exprimo ver. 5x15
|
|
Back to top
|
|
 |
mdisaster2
Joined: 22 Dec 2006 Posts: 107 Location: Rome, Italy
|
Posted: Sun 14 Nov 2010, 19:59 Post subject:
How to do it without touching resolv.conf |
|
1) Create a text file named /etc/resolv.conf.head
2) Put the alternative nameservers in that file, making sure that the last line ended with a line break. My /etc/resolv.conf.head looks like this.
| Code: | nameserver 208.67.222.222
nameserver 63.226.12.96
nameserver 72.3.208.251
|
3) Save the file, rebooted, rejoice
At connect time the contents of resolv.conf.head (ie the new nameservers) are dynamically inserted into resolv.conf before the nameserver that comes from the ISP, so they are queried first.
Works great for me with Lupu 501 (not sure about older versions).
Pages now open really fast and don't timeout anymore (yes, my ISP is that bad)
Notes:
The alternative nameservers can also be put into resolv.conf.tail in order to make them be queried after the ISP nameserver.
(possibly as a fallback if your ISP's DNS server is fast but unreliable).
To revert to the original status just delete the file(s) you created, or rename them something else.
Not ending the last line of /etc/resolv.conf.head with a line break results in having the contents of said line being prefixed to the ISP nameserver command. I didn't experiment with that, but it stands to reason that appending to resolv.conf.head a unterminated line containing some junk text such as the word DISABLED (or possibly even the # character) would disable the original ISP nameserver for good.
|
|
Back to top
|
|
 |
|