Re: [Hampshire] Ubuntu Network Manager and local DNS zone no…

Top Page

Reply to this message
Author: Dominic Cleal
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Ubuntu Network Manager and local DNS zone not playing nice?
On 22/04/11 00:11, Imran Chaudhry wrote:
> My problem is that while I can ping by hostname...
>
> $ ping xenserver
> PING xenserver.imran.local (192.168.98.30) 56(84) bytes of data.
> 64 bytes from xenserver.imran.local (192.168.98.30): icmp_seq=1 ttl=64
> time=4.12 ms
>
> ...which I would expect to work given my search domain.
>
> I cannot ping by FQDN:
> $ ping xenserver.imran.local
> ping: unknown host xenserver.imran.local
>
> $ cat /etc/resolv.conf
> # Generated by NetworkManager
> search imran.local
> nameserver 192.168.98.3
>
> 192.168.98.3 is Debian Squeeze running bind9.
>
> What is going on? I suspect NetworkManager as this works OK
> from another standard Debian server on my network configured to use
> 192.168.98.3 as DNS.

[ snip ]
> [1] Yeah, I know it's probably not good to make up your own TLDs, I
> plan to use a .net domain in future.


This fact may be related as the .local domain is used (reserved?) for
Avahi and mDNS.

On Fedora, my /etc/nsswitch.conf file has the following:

hosts:      files mdns4_minimal [NOTFOUND=return] dns


I expect Ubuntu's is very similar, so if the mdns lookup fails the
entire host lookup will also fail. You could probably move
mdns4_minimal to the end of the line, so your DNS takes precedence:

hosts:      files dns mdns4_minimal


This might affect Avahi though, but if you don't care about it just
remove or disable the Avahi services entirely.

Or the best solution might be to change your internal domain sooner
rather than later! There are a few domains and TLDs reserved for
internal use:

http://tools.ietf.org/html/rfc2606#page-2

--
Dominic Cleal
dominic@???