-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simon Oosthoek wrote: > 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?
No. The only relevant one, to which there is no real solution, is machines changing their FQDN (X doesn't like this) while someone is logged in. 80% of the problems could (IMHO - I could be wrong of course) be solved by: - -asking for one hostname by default - -Setting this name as HOSTNAME in /etc/sysconfig/network - -Setting this name as DHCP_HOSTNAME in /etc/sysconfig/network-scripts/ifcfg-eth* - -Leaving /etc/tmdns.conf alone (it will be default use `hostname`, which is what you want in > 95% of the cases In advanced mode, you would want to: - -Be able to choose not to send a dhcp hostname (I have never needed this, but I assume since by default it is blank, that for some purposes you would not want to set it), or set a different hostname. This should be per-interface of course. - -Be able to set a different zeroconf hostname (though I don't know why, except maybe if your provider has DNS/DHCP and you want the hostname to match it but be visible on zeroconf machines with a different name?). Currently, By default, if a user doesn't use the "advanced" buttons, they end up with: - -localhost as hostname - -on a Dynamic DNS network (DHCP doing DNS registrations for clients on successful lease), even if they fix the hostname, they get no DNS entries, until they run drakconnect *again* to set the dhcp_hostname This is just plain backwards, and will result in a number of services either being misconfigured (ie not working from other clients) or complaining about it (postfix will complain if `hostname` == "localhost"). Regards, Buchan [Warly, Till thinks this issue should be fixed before final release, which is why you're getting 2 copies] - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/ayXlrJK6UGDSBKcRAhHKAKCMVZoE2GJeuMFxdEP59NjChxpljQCfYf6E Q1xFSLWlRXKJxvue93Q/5Co= =9bUU -----END PGP SIGNATURE----- ***************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *****************************************************************
