Re: Installfest this Saturday - PLUG website dead?

Top Page
Attachments:
Message as email
+ (text/plain)
+ signature.asc (application/pgp-signature)
+ (text/plain)
Delete this message
Reply to this message
Author: Joseph Sinclair
Date:  
To: Main PLUG discussion list
Subject: Re: Installfest this Saturday - PLUG website dead?
Pretty much all DNS servers forward requests upstream. The critical configuration is what is upstream.
If you want true results, the safest is to set the root nameserver anycasts as the upstream, but that's not nice, as it adds unwarranted load to the root servers, which are a limited global resource.

You can connect any system (DNS in IpCop, NAT router, local DNS server, or just the resolv.conf) to a variety of DNS services. The tricky part is finding a reliable and trustworthy resolver besides the root nodes.

Most people connect to their ISP because DHCP sets it up. If you're willing to type it in, though, there are several anycast DNS services available.
Google, for instance, runs a lighting fast public DNS at 8.8.8.8 and 8.8.4.4 anycast that returns absolutely compliant results (including NXDOMAIN for failed lookups, instead of false results).

There are many other open resolvers. Most do the same redirect-failure-to-ads trick that Cox is doing now, however.


Craig White wrote:
> On Sun, 2010-02-28 at 10:34 -0700, Eric Shubert wrote:
>> Running your own caching resolver is pretty trivial on RHEL/Fedora. Just
>> need to install the caching-nameserver package (which pulls in deps when
>> you use yum to install it). You then need to have:
>> nameserver 127.0.0.1
>> first in your /etc/resolv.conf file so it gets used. If your computer is
>> directly attached to the cox modem, that'll be a pain as dhcp resets
>> your resolv.conf file. If you're using cox, you really should have a
>> router with nat between your computer and the cox modem though, so your
>> computer isn't sitting on a public address.
>>
>> I don't know off hand how to set up a local resolver on Ubuntu. I don't
>> really need one myself because my IPCop is my resolver. ;)
> ----
> in the configuration of your network adaptor, you can turn off DHCP
> client changes to /etc/resolv.conf
>
> PEERDNS = no
>
> various ways to accomplish this depending upon whether you are using
> NetworkManager or not, which distro, etc.
>
> I thought ipcop provided dns forwarding to the DNS servers set up within
> ipcop and didn't actually provide any DNS resolution by itself so if you
> use DHCP on ipcop on a Cox connection, you are back on Cox's name
> servers.
>
> Craig
>
>


---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss