I have a RHEL7.0 host which has this standard entry in
127.0.0.1 localhost.localdomain localhost
$ ping localhost.localdomain PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
But trying to resolve the absolute version of the same fails:
$ ping localhost.localdomain. ping: unknown host localhost.localdomain.
And in general, trying to resolve absolute FQDNs against relative
/etc/hosts entries fails. Now, if I change the entry in
/etc/hosts to have a trailing period, I can then resolve the absolute FQDN. But then I can no longer resolve the relative FQDN. Seems if I want both absolute and relative forms to resolve, I have to explicitly include both forms of the FQDN in
Is this odd behavior described in an RFC or standard somewhere so I can understand it better? Is it configurable somehow?