[18559] in Athena Bugs
Re: linux 8.4.17: hostname set to (none) sometimes on boot with DHCP
daemon@ATHENA.MIT.EDU (Camilla R Fox)
Tue Nov 28 20:26:30 2000
Message-Id: <200011290126.UAA04908@ops-2.mit.edu>
To: bugs@MIT.EDU
cc: mpp@MIT.EDU, jweiss@MIT.EDU, network@MIT.EDU
In-reply-to: "[18542] in Athena Bugs"
Date: Tue, 28 Nov 2000 20:26:26 -0500
From: Camilla R Fox <cfox@MIT.EDU>
> What's wrong:
> Hostname is sometimes set to "(none)".
>
> This is likely to happen if you get assigned an IP address that isn't
> in the host table. For reasons I don't completely understand the
> MITnet DHCP servers sometimes give out IP addresses like this. The
> next time this happens can you see if this is the problem?
I've had this happen to me on the machine's home network, when it has
been given the correctly resolving IP address for it (ie. the one I
registered as). I've also had it happen from other networks, on which
I got an address that resolved correctly.
(I believe Mike mentioned to me that this has been the case for him,
too.)
It's intermittent, and I haven't noticed a correlation with network
hosage. (I was surprized to have everything work correctly when I
booted up during a known hosage issue.)
I think we're looking at two unrelated problems here.
-Camilla
