#3298: Mutt's way to get the FQDN is broken
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: mutt | Version: 1.5.20
Resolution: | Keywords:
---------------------+----------------------
Comment (by vinc17):
Replying to [comment:13 me]:
> Hinting from /etc/resolv.conf is still useful for the mobile/DHCP use
case where the DNS domain name is unlikely to resolve, but
/etc/resolv.conf may contain a useful value, but it should be the fallback
to the DNS lookup described in this ticket.
Note that there should not be problems with mobile/DHCP use case, as the
FQDN is not linked to some particular network interface. For instance, on
recent Debian installations, the FQDN typically resolves to 127.0.1.1
locally via /etc/hosts, which contains some line like:
{{{
127.0.1.1 node.domain node
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3298#comment:34>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
