When updating /etc/conf.d/domainname and entering a domain name in the DNSDOMAIN line, resolv.conf gets generated like this: search blah.com domain blah.com This is wrong; only "search blah.com" should be generated, as the first key on that line equates to the machines own DNS domain. The domain line is primarily used for NIS/YP operations and is not needed unless the NISDOMAIN line is filled in. Also, there should be a DNSSEARCHPATH or similar to allow users to have domains appended after the primary DNS domain on the search line. -A
Well, I'm not totally sure about that, but I think that the next stable baselayout will differ in the way it deals with resolv.conf. If I understood everything well, the resolv.conf will not be generated anymore by /etc/init.d/domainname script. Instead, net.eth0 will use a new package : net-misc/resolvconf-gentoo (maybe inspired by the same debian package ?), which should do the job ? Or maybe I'm just wrong, I don't have much time to verify now ;) But anyway, the new baselayout does not use /etc/init.d/domainname anymore.
As long as it gets the distinction that "domain" is a NIS related directive, and that "search" is DNS related; and that "seach" can take multiple keys, where the first is the machine's primary DNS domain suffix. -A
(In reply to comment #2) > As long as it gets the distinction that "domain" is a NIS related directive, > and that "search" is DNS related; and that "seach" can take multiple keys, > where the first is the machine's primary DNS domain suffix. Read the resolv.conf man page and it clearly states that while search and domain are mutually exclusive neither are NIS related. Infact NIS isn't even mentioned. the domainmame script has been punted from baselayout-1.12 in favour of conf.d/net controlling resolv.conf like so dns_domain_lo="foo.com" dns_search_lo="foo.com bar.com" dns_servers_lo="127.0.0.1"
