Skip to content

Document intersection of nss-myhostname and nss-resolve #1605

@fsateler

Description

@fsateler

While testing out nss-resolve, I discovered that after enabling it, myhostname becomes useless:

  • *.localhost maps to 127.0.0.1 and ::1
  • The local hostname resolves to the public addresses of the host
  • gateway resolves to the routing gateway address

All three tested with getent ahosts $1, having disabled myhostname. Has nss-myhostname become superfluous when nss-resolve is installed? Or is this result only sometimes applicable? The documentation doesn't say, and in particular nss-resolve(8) does not mention that one should expect this behavior.

systemd 227-2 from debian (plus enabling nss-resolve).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions