Kyle McDonald wrote: > James Carlson wrote: >> Dave Miner writes: >> >>> Kyle McDonald wrote: >>> >>>> Are these messages telling me something I'm not seeing? >>>> >>>> >>> Yes, it's obliquely telling you that the server doesn't think it's >>> actually 172.30.170.21. What does its hostname resolve to (i.e. getent >>> hostname)? >>> >> Dollars to doughnuts: it resolves to 127.0.0.1. ;-} >> >> > Not quite. But almost as bad. > > bge1 had also been configured in the past, but I didn't think it > mattered since I had blown away the DHCP config and recreated it since > disabling bge1. I figured any record DHCP had of that interface and IP > were wiped when the config was wiped. > > getent hosts `hostname` returned 172.30.172.21, which is what bge1 used > to use. > > I've always thought that decoupling /etc/nodename from > /etc/hostname.abcX was a good idea, but since Solaris did that, I've > often wondered what (other than 'hostname' and the login prompt) used > the contents of /etc/nodename in a way like this. I hadn't found > anything until today. It's good to know. >
It's arguably broken. The OWNER_IP feature is a good thing to use, as it makes your DHCP configuration system-independent. Dave _______________________________________________ networking-discuss mailing list [email protected]
