hehe, so … if you ever change the hostname of a Linux machine, you really really ought to double-check /etc/hosts to make the same hostname change there

it’s surprising just how much will break if a machine’s own hostname isn’t resolvable to a 127.x.x.x address :P

  • otacon239@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    12 days ago

    Interesting. I’ve changed my hostname on a few machines throughout the past and never ran into this. Good to know of I ever run into this in the future.

  • monovergent@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    12 days ago

    Lost my mind a few years ago over this quirk. Now I always change both files when I want to change the hostname.

  • limelight79@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    11 days ago

    This reminds me… My server demands to be known as hostname.local on my network. The other machines just respond to just hostname. I really should figure out why that is.

  • Hawke@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    10 days ago

    It’s always been wild to me how the seemingly-simplest change (“what is the name of this computer”) has so many little gotchas and quirks.

  • alastel@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    12 days ago

    If you have myhostname set for hosts in /etc/nsswitch.conf it shall take care of this for you (should be the default on most systemd distros I believe? not sure)

    • jokeyrhyme@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      i’m guessing a few things somehow consume /etc/hosts mappings without going through nss /shrug