Want workstation net speed: install bind

[octowaters]

For a comparison of net speed on my workstation, I tested the standard PCLinuxOS setup with and without *bind*.

Using bind improved speed noticeably. Maybe, forum users with a workstation will wish to install it, and if so, in order to get dynamic addresses, they will have to make their first DNS server 127.0.0.1 and put the replaced first address as their second DNS server.

The Shorewall firewall will need to have DNS service allowed.

That should give you faster responses through your own DNS server on your workstation.

Enjoy!

[coffeetime]

Yep, bind and bind-utils make everything much faster.

[YouCanToo]

I think that you would find that by changing your local dns ip to OpenDNS Ip you will gain speed and would not have to install bind itself. As for bind-utils that shouldn't make dns faster as they are a set of utilities such as dig, and those type of things, which really do not speed up DNS but are just tools.

[scoundrel]

I think that you would find that by changing your local dns ip to OpenDNS Ip you will gain speed and would not have to install bind itself. As for bind-utils that shouldn't make dns faster as they are a set of utilities such as dig, and those type of things, which really do not speed up DNS but are just tools.

how and where do you do that ?

[pinoc]

Hi Scoundrel,

you can find info on opendns here for many routers or other Internet connection setups. Simply use their DNS in the Internet setup configuration (in PCC) of your machine.

regards,
-p.

[scoundrel]

Hi Scoundrel,

you can find info on opendns here for many routers or other Internet connection setups. Simply use their DNS in the Internet setup configuration (in PCC) of your machine.

regards,
-p.

thanks P ...done and done..

[Xenaflux]

Simply use their DNS in the Internet setup configuration (in PCC) of your machine.

One:I found their DNS slower, and in a few cases I couldn't connect.
Two: configuring in PCC resulted in having to do that after every reboot...w.o.w : it didn't stick

Opening a terminal, su to root and run : adsl-setup: made my OpenDNS stick

I am using 2009.2 fully updated

[octowaters]

I think that you would find that by changing your local dns ip to OpenDNS Ip you will gain speed and would not have to install bind itself. As for bind-utils that shouldn't make dns faster as they are a set of utilities such as dig, and those type of things, which really do not speed up DNS but are just tools.

Installing BIND does not imply a lot of code. It's a small package. BIND-UTILS gives ones bind installation the full use of net tools that otherwise one would have to recur to on the net.

While OpenDNS is an option, I fail to see what advantages is gives one over an installed BIND on a workstation. The first, and foremost caveat would be privacy issues: giving away where you are going, putting more personal data on a another database with all your contact information with the downside that you are not guaranteed any protection against your web visiting habits,

Just my penny worth, but don't let this influence your decision making for that is up to each and everyone to make.

[scoundrel]

I think that you would find that by changing your local dns ip to OpenDNS Ip you will gain speed and would not have to install bind itself. As for bind-utils that shouldn't make dns faster as they are a set of utilities such as dig, and those type of things, which really do not speed up DNS but are just tools.

Installing BIND does not imply a lot of code. It's a small package. BIND-UTILS gives ones bind installation the full use of net tools that otherwise one would have to recur to on the net.

While OpenDNS is an option, I fail to see what advantages is gives one over an installed BIND on a workstation. The first, and foremost caveat would be privacy issues: giving away where you are going, putting more personal data on a another database with all your contact information with the downside that you are not guaranteed any protection against your web visiting habits,

Just my penny worth, but don't let this influence your decision making for that is up to each and everyone to make.

so your saying that using OpenDNS gives up all that info ??  just wanting to get your penny's worth straight

[YouCanToo]

I think that you would find that by changing your local dns ip to OpenDNS Ip you will gain speed and would not have to install bind itself. As for bind-utils that shouldn't make dns faster as they are a set of utilities such as dig, and those type of things, which really do not speed up DNS but are just tools.

Installing BIND does not imply a lot of code. It's a small package. BIND-UTILS gives ones bind installation the full use of net tools that otherwise one would have to recur to on the net.

While OpenDNS is an option, I fail to see what advantages is gives one over an installed BIND on a workstation. The first, and foremost caveat would be privacy issues: giving away where you are going,

If the nameserver (bind) that you are using doesn't know about the information your request it is going to go out to the tld root server(s) and ask so how is "giving away where you are going"  going to be any different?

putting more personal data on a another database with all your contact information with the downside that you are not guaranteed any protection against your web visiting habits,

What personal data?  Running your own dns doesn't guarantee "protection against your web visiting habits" either!

Just my penny worth, but don't let this influence your decision making for that is up to each and everyone to make.

[octowaters]

so your saying that using OpenDNS gives up all that info ??  just wanting to get your penny's worth straight
[/quote]

I did not say "gives up" but has available on its server records all your queries which lead to sites visited. As a corollary, this information is available for inspection, government requisitioning, information hacking and so on. Because it is open does not mean there is any guarantee of confidentiality in the strict sense of the word, it is just a service - I can't help wonder who finances its service and why because "free" is not so free behind the scenes in most cases.

[YouCanToo]

so your saying that using OpenDNS gives up all that info ??  just wanting to get your penny's worth straight

I did not say "gives up" but has available on its server records all your queries which lead to sites visited. As a corollary, this information is available for inspection, government requisitioning, information hacking and so on. Because it is open does not mean there is any guarantee of confidentiality in the strict sense of the word, it is just a service - I can't help wonder who finances its service and why because "free" is not so free behind the scenes in most cases.
[/quote]

The founder is a person named David Ulevitch, he also started EveryDNS prior too OpenDNS.
OpenDNS is donation and ad-supported

DNS is inherently insecure and vulnerable to all sorts of issues. IE: cache poisoning for example. 

[scoundrel]

so your saying that using OpenDNS gives up all that info ??  just wanting to get your penny's worth straight

I did not say "gives up" but has available on its server records all your queries which lead to sites visited. As a corollary, this information is available for inspection, government requisitioning, information hacking and so on. Because it is open does not mean there is any guarantee of confidentiality in the strict sense of the word, it is just a service - I can't help wonder who finances its service and why because "free" is not so free behind the scenes in most cases.

The founder is a person named David Ulevitch, he also started EveryDNS prior too OpenDNS.
OpenDNS is donation and ad-supported

DNS is inherently insecure and vulnerable to all sorts of issues. IE: cache poisoning for example. 
[/quote]

so the OpenDNS port numbers/addys are going through their servers instead of the service I have ??

[YouCanToo]

so your saying that using OpenDNS gives up all that info ??  just wanting to get your penny's worth straight

I did not say "gives up" but has available on its server records all your queries which lead to sites visited. As a corollary, this information is available for inspection, government requisitioning, information hacking and so on. Because it is open does not mean there is any guarantee of confidentiality in the strict sense of the word, it is just a service - I can't help wonder who finances its service and why because "free" is not so free behind the scenes in most cases.

The founder is a person named David Ulevitch, he also started EveryDNS prior too OpenDNS.
OpenDNS is donation and ad-supported

DNS is inherently insecure and vulnerable to all sorts of issues. IE: cache poisoning for example.  

so the OpenDNS port numbers/addys are going through their servers instead of the service I have ??

Normally when you setup your system the DNS numbers used are those of your ISP. If you look at most gateways that number appears as 192.168.1.1 (the router in the case of Linksys) or 192.168.0.1 (Netgear) at this point the the router is usually set to aquire the dns from your ISP.  Most ISP that I have seen and used have terrible DNS services. Usually very slow to resolve the name to ip (bind/DNS) or they will resolve some but not all domains. If you check the forums here you will see that happens a lot!  When you setup your network you have the choice to choose the dns service that will be used. In PCC it is normally checked to "Get DNS servers from DHCP" If this is selected your DNS than will come from your ISP. The other way is to "un-check" the Get DNS from DHCP box. At that point you have to enter the IP numbers for the DNS servers that you want to use. In the case of OpenDNS those numbers are 208.67.222.222 and 208.67.220.220  When you finish your network setup, from them on you are using the OpenDNS Servers for name resolution.

When you browse the web and request a domain name, lets say google.com for example. Your system uses DNS. Your computer uses your dns setup and sees if it knows where google.com lives on the internet (74.125.45.100). Remember that your computer does not understand the name google.com, it only knows the IP address 74.125.45.100. If you computer does not have that IP locally cached it than requests that information from whoever provides your DNS services. If they happen to know it that your are displayed the website. If they don't know where google lives than they request it from their uplink dns server or a TLD Name Server and than that information is passed back and than you see the website. Please understand this is a very simplistic explanation of bind/DNS. The number of requests between you that bind may make can be a few or many. Most of the time it all happens very very quickly and you really don't notice. Sometimes though it may take what seems like forever.

I hope that this has helped in the information that you are seeking.

[scoundrel]

thanks dude.. answered