resolving .local addresses
glgxg at sbcglobal.net
Sun Jun 28 15:54:03 UTC 2009
On 06/26/2009 10:42 PM, Bill Moseley wrote:
> I'm moving to zeronconf discovery for my host names on the LAN.
> I added search paths for my domain and also "local".
> $ cat /etc/resolv.conf
> domain hank.org
> search hank.org local
> nameserver 192.168.1.1
> "bumby2" has a zeroconf host name bumby2.local, so with the above I see:
> $ host -v bumby2
> Trying "bumby2.hank.org"
> Trying "bumby2.local"
> Trying "bumby2"
> Host bumby2 not found: 3(NXDOMAIN)
> Received 99 bytes from 192.168.1.1#53 in 17 ms
> $ ping bumby2.local
> PING bumby2.local (192.168.1.5) 56(84) bytes of data.
> 64 bytes from bumby2.local (192.168.1.5): icmp_seq=1 ttl=64 time=1.68 ms
> $ cat /etc/nsswitch.conf | grep hosts
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
> Tried changing the order, but no luck. Anyone know if I can get host names
> qualified with .local?
[problems resolving fully qualified domain names in environments where
.local is used as a TLD]
are of interest.
More information about the ubuntu-users