[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

Will Rouesnel 80900 at bugs.launchpad.net
Thu Jun 21 05:39:42 UTC 2012


Just ran into this myself with 12.04.

The problem is nsswitch.conf is:

hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4

which means looks up check hosts, mdns and if mdns reports a not found
then it doesn't go to DNS.

Switching it to

hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4

fixes it by having DNS get checked first. IMO this should be the out-of-
the-box configuration since the historical trend would be the DNS is
serving names and should get precedence anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/80900

Title:
  problems resolving fully qualified domain names in environments where
  .local is used as a TLD

Status in “avahi” package in Ubuntu:
  Triaged

Bug description:
  Install Kubuntu Feisty
  Set the ip address to dhcp for eth0 (ethernet port)
  make sure the host name and domain name are set
  Hostname computer1
  DomainName mydomain.local

  allow DHCP to assign the IP address

  Ensure the computer details are registered in DNS for
  mydomain.local...

  computer names registered in DNS (FQDN) 
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local

  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.

  if I issue the following comands on computer2 or computer3, it works
  correctly:

  ping computer2      (response received - ping good)
  ping computer3      (response received - ping good)
  ping computer2.mydomain.local       (response received - ping good)
  ping computer3.mydomain.local       (response received - ping good)

  if i issue the same commands from the feisty box (computer1), these
  are the results..

  ping computer2       (response received - ping good)
  ping computer3       (response received - ping good)
  ping computer2.mydomain.local       (unknown host)
  ping computer3.mydomain.local      (unknown host)

  for some reason if you try to ping the fully qualified domain name on
  feisty, it cant resolve it, yet it can resolve it using both static IP
  Addressing and DHCP addressing on Dapper. (i set the IP to static as
  well for the test) Static and DHCP on Dapper works fine. Static and
  DHCP wont resolve fully qualified domain names on Feisty. (computer1,
  computer2 and computer 3 are all Kubuntu machines. DNS Server is a
  Windows 2003 Server (that will be changed a kubuntu server very soon
  though!)

  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.

  cheers

  Rod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+subscriptions




More information about the foundations-bugs mailing list