On Fri, Sep 19, 2003 at 05:01:09PM +0200, Buchan Milne wrote: > >> IMHO, drakconnect's job is to ensure: > >> 1)The hostname is never set to localhost if there is any networking > >> device > >> attached to the machine in question > >> 2)Reverse lookups will always work. In the case of DHCP, drakconnect > >> should ensure that the hostname is sent as DHCP_HOSTNAME (in which > >> case we > >> hope the DHCP administrator has working DDNS), and doesn't touch > >> tmdns.conf. In the case of no DHCP, tmdns.conf is not touched (and we > >> hope > >> the other machines have working tmdns). > > Someone needs to take action, and advice from the community, on this for > 10 IMHO. I have to remember to use the advanced button twice in > drakconnect to get the behaviour I want (the default in Windows), and > enter the same hostname 3 times (instead of just once like in Windows).
There are some things to consider in this context - hosts that move about - hosts never connected to a network - hosts always connected to a single network - hosts connected to multiple networks A solution that comes to mind is to copy the concept of "nodename" from solaris. A machine is a node, regardless of its network connections, so that should always be the local machine (resolve to 127.0.0.1 and visa versa). Optionally this can overlap with the name associated with an internet connection. The FQDN (if it exists) of each connected network should be resolvable on the host, so either through /etc/hosts or a nameservice. The flexibility of laptops and desktop-pc's requires a totally different attitude towards network configuration than is common for server machines. Perhaps this is the basis for all the problems associated with network configuration on mandrake/linux? I hope a rewrite of drakconnect for ML++ will be addressing these issues! Cheers Simon
