DHCP seems to set hostname = Mac address, doesn't reverse lookup
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
DHCP seems to set hostname = Mac address, doesn't reverse lookup
So my hostname is auto-set on boot to something like x1-06-00-00-de-xi etc, as I heard will happen as Mandrake's Control Centre told me - but my hostname used to be of the format:
octet1-octet2-octet3-octet4.cable.ubrx.isp.com (I had problems when I ran XP too, my hostname = my computer name) I've tried the hostname command as root, and that works temporarily, although, I won't always know my hostname, the whole point is that it's assigned automatically of course.
Any idea how I stop it being assigned an address like my MAC?
If I want to have proFTPd running, I have to run hostname octet1-octet2-octet3-octet4.cable.ubrx.isp.com and then start it, and amaroK fails to start up altogether, says it timed out trying to contact 'amaroK'. Not sure whether it means the aRts server (which is running anyway)
I believe dynamic hostnames are given by DNS. Your ISP assigns you an IP address, and your machine looks up that IP address in DNS, and that is what shows. Your ISP may have changed policies recently...
You should still be able to FTP to just IP address (ie FTP XXX.XXX.XXX.XXX).
I understand that, but apparently MDK sets your hostname on boot or login (I'm unsure) to a name similar to the MAC address of the NIC, as opposed to letting DHCP do its job.
I can FTP *out*, but if I want proFTPd running, I have to run that hostname command above to get proFTPd to start up: It doesn't seem to like a hostname that doesn't reverse lookup to the IP. :-/
Edit: just re-read your post: I'll give the ISP a call tomorrow and ask if there's any reason the hostname is being changed on their part. I noticed running winipcfg on the dialup machine (I know, but it's not my machine, I can't install *nix on that one, sadly) said that the hostname was something which definitely wouldn't reverse lookup to the IP. Seemed to be about as random as XP's assigning of a new computername. :-/ Odd.
May be worth noting that the errors amaroK and others are dying out with in CLI mode use an IPv6 version of 127.0.1. :0.0 if I'm not mistaken.
Last edited by techsimian; 08-26-2004 at 06:59 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.