Re: /etc/resolv.conf and /etc/named.conf

"D. Hugh Redelmeier" <[email protected]>
Newsgroups gmane.network.freeswan.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----


| From: Michael Richardson <[email protected]>

| - From /etc/dhclient.conf (for ISC dhclient):
| 
| prepend domain-name-servers 127.0.0.1;
| 
| This results in for me in:
| 
| search sandelman.ottawa.on.ca
| nameserver 127.0.0.1
| nameserver 192.139.46.30
| nameserver 207.176.162.14
| nameserver 66.11.170.98
| nameserver 192.139.46.1
| nameserver 192.139.46.33
| 
| so, I still get to try what the DHCP server told me, in the event that my
| local DNS can't cope.

As I understand it, this will multiply the resolver's timeout by a
factor of 6: one for each entry.  Supporting evidence, from
resolver(5):

	If there are multiple servers, the resolver library queries them in
	the order listed.

It also has the effect of generating an even more tangled set of
holds.  And each time you try a query, you exercise a different path
so you may get a different behaviour, making it harder to debug.

This seems like a very bad idea.  Why not fix your local DNS?

Hugh Redelmeier
[email protected]  voice: +1 416 482-8253

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBPjwixMFAuQPManGZAQHrRgQApa2g1yHRNFnpmglQlq5Av/IIz/BG4X44
ZpqxpXo7LMVp0WR6vmElG8f/3RNjtd1epRk8Xhq8coEHqp4jKTRJN0XxrselAwFQ
2ZZe7g9mc9t7eNW/6f6QXZUhKdoR9AyP6Kh6GTaW4U5BY4J+ar23izUA8VvukD62
/5k3kAyHiVw=
=JPpY
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.