Web lists-archives.com

Re: Why does resolv.conf keep changing?




Gene Heskett composed on 2017-10-24 22:52 (UTC-0400):

>> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote:

>>>and made immutable. Particularly is the fact that /etc/resolv.conf
>>> isn't a link to something else but contains:

>>>nameserver 192.168.XX.1
>>>search 	host	dns
>>>domain coyote.den
...
> Now, since my home net is host file based, about 8 machines and a printer 
> these days, I make resolv.conf into a real file, and 
> once /etc/network/interfaces is similarly setup to work, both are then 
> made immutable, at which point resolvconfig and N-M can be like a steer, 
> try, but cannot tear down a working circuit, that it can never bring 
> back to life despite continueing efforts. Both N-M and resolvconfig are 
> solutions looking for a problem I don't have anymore.
...
> Your turn Mike, but lets see the facts as to why its wrong, not just an 
> argument for the sake of arguing.  The list doesn't need that, it needs 
> tutorials. 

Apparently no one else is interested in tutoring, so I'll offer this:

1-My LAN is configured essentially the same as yours, including a 2k hosts file.

2-My lines 1 are always the search lines, each starting with the word "search",
followed by domain(s) to be searched, e.g. "search mylan.net coyote.den
someother.biz"

3-My lines 2[3,4,...] are always nameserver lines, containing only the string
"nameserver" followed by one IPV4 address.

4-I have no lines starting with string "domain", but as a result of this thread,
that may soon change.

NAICT from the man page, Mike's objection to yours is your search line should
contain neither the string "dns" nor the string "host", and probably ought to
contain at least the string "coyote.den" following the string "search".
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/