trouble getting domainname set

[howardt]

I'm stumbling around trying to get the domain name of my computer set properly, as well as getting the resolver to use the right domain name when hostname only is given.

The symptoms are that afer a reboot, the login prompt has "unknown domain" (something like that) after the host name; and I can't mount an NFS directory until I muck with resolv.conf.

As is policy for our network, I use DHCP to get network information (even though I have a static IP address). There are two DHCP servers, serving slightly different domains. I guess my machine address is known to both of them. But the one that answers first causes a resolv.conf to be written that has a search line with the wrong domain name in it (wrong in that if I use that I can't mount the NFS filesystem that I want to). I can manually edit resolv.conf after booting, change the domain, get my machine's dnsdomainname set properly, and then things are find until a reboot.

I've done a bunch of things. As I said, I'm stumbling around, and some of these are probably wrong/redundant/conflicting. I'm not very knowledgable in this area. Can someone please advise?

Here's what I think I've got on my current system:

/etc/dnsdomainname contains the one I want
/etc/conf.d/net has iface_eth0="dhcp", and I added net.eth0 to the default run level
I added dnsdomainname to the default run level (tried putting it at boot level - didn't help)
I put my static IP addr in /etc/hosts, with the FDQN I wanted beside it
I made an /etc/host.conf file containing "order hosts,bind"

[biznatch]

The login problem is caused by your hostname not being in DNS. If you update your DNS to include your hostname, it will fix the login saying "unknown domain".

If you are running a server, you should have a static IP and static settings rather then using DHCP host reservations to avoid problems like this. This way you cond have to worry about DHCPCD messing with your files. Alternatively, you can use the "-R option" in your /etc/conf.d/net file under the "dhcpcd_eth0" tag (man dhcpcd for more info).

Then we need to work on your DNS issues. Why on earth would you need 2 different DNS zones on the same subnet? I'm sure you have your reasons, but perhaps you need to alter they way they do lookups so that they reference each others zones or something.

Hope this info helps. Let me know if you need anything else.
_________________
While your waiting for your post to be answered, please help with unanswered posts.