-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Any comment on this???
Buchan Milne wrote: > Damien Chaumette wrote: > > >>Well, there are mutliples cases : >> >> o static IP >> you set your HOSTNAME (/etc/sysconfig/network) >> >> o DHCP >> you can ask a name to your DHCP server (DHCP_HOSTNAME), and it'll >> return either this one or another, then initscripts use it as >> your HOSTNAME. > > > What if the dhcp server returns > dhcp-vlan-adsl-xxx-xxx-xxx-xxx.myisp.mydomain.com and the user doesn't > want to have hostname dhcp-vlan-adsl-xxx-xxx-xxx-xxx as hostname? > > >>Then you have zeroconf which is subdivided in two parts : >> >> o zcip which handle the IP dynamic configuration (only with DHCP) >> o tmdns always installed, to resolve names. >> >>Zeroconf hostname (/etc/tmdns.conf) is set to your real hostname value >>by default or one you specified in drakconnect. > > > IMHO this is wrong. Hostname should be set, tmdns will use `hostname` if > you don't set it manually in the config file. There is no case where you > will want a different hostname taken by tmdns than `hostname`, so IMHO > drakconnect should leave tmdns.conf alone. > BTW, I think this issue is also causing problems for samba, since often HOSTNAME is unset, so `hostname` gives localhost. Then, samba uses this hostname, and clients try to connect to \\localhost, which obviously does not work. Also, this breaks the winbind setup, since 'smbpasswd -j' will either try and join to a pre-made account (in the case of a non-admin join), as localhost (which will not work), or it will try and create a new account (in the case of an admin-join), which will only work for the first machine joined this way (if at all). Finally, a number of packages generate self-signed certificates, either during installation or for first startup, and then the cert will have 'CN=localhost', so if ther use changes the hostname, they will have to regenerate or live with the complaints. This is a really major issue. No machine should *ever* use localhost as it's hostname if it is connected to a network, especially if running samba, cups, apache etc etc. I think I must file a bug on drakconnect, but I haven't had time to test this myself. > >>Let user set a hardcoded hostname when using dhcp will only lead to >>unresolved names. >> > > > No, that's precisely *why* tmdns will *default* to using the set > hostname!!! It's fine if the IP resolves to multiple hostnames, but it's > better that it resolves to the name the user wants (but this should be > an advanced configuration). Please consider this issue ... it should not be necessary to touch tmdns.conf. Ever. Regards, Buchan - -- |--------------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/Rgq4rJK6UGDSBKcRAjapAJ9eRcvbmR0p0FsEuCy+fcC/o6Y7FQCfVcaw nHghL4RJf3qvjDMHNLYjKf0= =CI2/ -----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. *****************************************************************
