Re: My hostname not being registered via DHCP

From: prg (rdgentry1_at_cablelynx.com)
Date: 02/01/05

  • Next message: John Fields: "Re: OT: Safe Riddles" 
    Date: 31 Jan 2005 15:13:09 -0800

    UncleStoner wrote:
    > Hello,
    > I'm a Linux newbie.
    > I have just installed Redhat Linux 8.0. I'm using DHCP to get a IP
    > address, DNS servers, etc. That's all working fine. The problem is,
    > the hostname of my linux box isn't being registered with DNS by DHCP.
    > The hostname of my Linux box is "seratonin", and I can't ping it from
    > other machines on my network (either by "seratonin" or
    > "seratonin.mycompany.com".

    Unless it's an IP/domain you registered, your ISP most likely
    automatically generates a name like 216-34-isps-subnet-domain. The ISP
    updates DNS servers and can't be bothered with naming conflicts unless
    you pay fer 'em.

    > Below are all the setup files that might be relevant
    >
    > /etc/hosts:
    > 127.0.0.1 localhost.localdomain localhost seratonin
    >
    > /etc/resolv.conf
    > ; generated by /sbin/dhclient-script
    > search mycompany.com
    > nameserver 10.9.3.23
    > nameserver 10.9.3.22
    >
    > /etc/sysconfig/network
    > NETWORKING=yes
    > HOSTNAME=seratonin.mycompany.com

    This name only useful on localhost and on your LAN only if _you_
    provide some kind of name resolution -- eg., /etc/hosts files or
    dnsmasq or running bind/named on your LAN.

    > /etc/sysconfig/network-scripts/ifcfg-eth0
    > DEVICE=eth0
    > BOOTPROTO=dhcp
    > ONBOOT=yes
    > USERCTL=no
    > PEERDNS=yes
    > TYPE=Ethernet
    > DHCP_HOSTNAME=3D"seratonin.mycompany.com"

    Just another form of client-id. The ISP likely ignores it in favor of
    your MAC address.

    > Note that for DHCP_HOSTNAME above I've tried "seratonin",
    > "seratonin.mycompany.com", 3D"seratonin", and leaving it out. I
    don't
    > know what the deal with the '3D' is, I saw it suggested somewhere.

    If you want to see the name the ISP is assigning to your computer you
    will have to _not_ assign a name yourself. The name you are assigned
    will be almost guaranteed ugly, very ugly, I mean really very ugly --
    and will vary as/if your IP changes.

    If you want a static IP and registered domain name, you will have to
    buy it from your ISP or someone they work with. dyndns may provide a
    way for you to have a publicly accessible name if you need that. See:
    www.dyndns.org/
    .
    hth
    prg
    email above disabled

  • Next message: John Fields: "Re: OT: Safe Riddles"

    Relevant Pages

    • Re: Networking problems (again) tough one
      ... The problem *only* occurs on my Linux machines. ... DNS numbers, ... all systems start working again whether setup manually or with DHCP. ... If theu are shoing good, and yet things dont work, you may have a misconfigured router. ...
      (comp.os.linux.setup)
    • Re: "Microsoft Location Finder" - how is it supposed to work ?
      ... Of course my home DSL points to my ISP located 12 ... >That might eventually work for DHCP settings - but not static. ... so they just convinced the RADIUS server to ... Using DNS for that is ridiculous. ...
      (alt.internet.wireless)
    • Re: Networking problems (again) tough one
      ... The problem *only* occurs on my Linux machines. ... DNS numbers, ... Turned out the only reason my manual settings had worked was simply because I had been fooling with it for two ... all systems start working again whether setup manually or with DHCP. ...
      (comp.os.linux.setup)
    • Re: Networking problems (again) tough one
      ... The problem *only* occurs on my Linux machines. ... DNS numbers, ... all systems start working again whether setup manually or with DHCP. ... I assume the linux machines are getting DHCP stuff right? ...
      (comp.os.linux.setup)
    • Re: dhcp startup
      ... The linux clients just about manage to find an IP ... DNS, domain name, ... They get whatever you tell them to get from a dhcp server. ...
      (alt.os.linux)
    Loading