[Bug 340498] New: WRITE_HOSTNAME_TO_HOSTS doesn't
https://bugzilla.novell.com/show_bug.cgi?id=340498 Summary: WRITE_HOSTNAME_TO_HOSTS doesn't Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: peter@plord.co.uk QAContact: qa@suse.de Found By: --- The dhcp option WRITE_HOSTNAME_TO_HOSTS doesn't appear to do anything -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=340498#c1
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=340498#c2
--- Comment #2 from Peter Lord
https://bugzilla.novell.com/show_bug.cgi?id=340498#c3
--- Comment #3 from Peter Lord
https://bugzilla.novell.com/show_bug.cgi?id=340498#c4
--- Comment #4 from Peter Lord
https://bugzilla.novell.com/show_bug.cgi?id=340498#c5
--- Comment #5 from Peter Lord
https://bugzilla.novell.com/show_bug.cgi?id=340498
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=340498
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=340498
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=340498#c6
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=340498#c7
--- Comment #7 from Peter Lord
That's because you have DHCLIENT_SET_HOSTNAME="yes". You might want to turn that off.
I see what you mean - with this setup, ping `hostname` works. But I do endup with two hostnames ( one static and one from the dhcp server ) - I would rather let the dhcp server set everything. I guess this isn't the way yast likes to do things.
WRITE_HOSTNAME_TO_HOSTS="yes" is taking the hostname from /etc/HOSTNAME and writing it to /etc/hosts. It's responsible for the last line of /etc/hosts:
127.0.0.2 plordnote.internal plordnote
/etc/HOSTNAME (defined at install time) has:
plordnote.internal
So WRITE_HOSTNAME_TO_HOSTS is actually doing something. It seems the problem lies in the fact that there isn't complete agreement between the DHCP server and your machine over what your hostname should be. If you have control over your DHCP server, you should be able to set it to recognize your MAC address and give you a consistent name of your choosing.
I move this machine from network to network and want the local dhcp server to configure the machine. So this idea won't fly. One thing that is confusing here is that WRITE_HOSTNAME_TO_HOSTS is a dhcp configuration option ... but appears to have nothing to do with dhcp.
As I see it, the reported problem is INVALID, as WRITE_HOSTNAME_TO_HOSTS does do something, though perhaps it's not what you expected it to do. If your network is reliable, you shouldn't need to write the hostname to /etc/hosts. Conversely, if your network is so unreliable that you need to write your hostname to /etc/hosts, perhaps you probably shouldn't be getting your hostname from DHCP.
FYI, this isn't a reliability question but a performance one. I'm a software developer and I don't want my performance tests skewed by hostname resolution involving network traffic.
If you're saying that you want to be able to cache the hostname that is provided by DHCP (which in the above case is little more than an abbreviated IP address), that's another issue, but it seems like a real corner case.
Thanks for your help, really appreciate it :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com