Arch Linux

justin-8

Member

From: Queensland, Australia

Registered: 2013-06-18

Posts: 53

mDNS resolution

Hey,

I've been using avahi and nss-mdns for local name resolution for a couple years now and it's mostly been working well.

In the past few months however search domains have broken with it. I'm not really sure where to look further to fix this, so some help would be much appreciated.

As for relevant configs currently:

My /etc/nsswitch.conf has (trimmed; the rest is default from the filesystem package):

hosts: files mdns_minimal [NOTFOUND=return] dns myhostname

/etc/resolv.conf has:

# Generated by resolvconf
search local dray.be
nameserver 192.168.1.1
nameserver 8.8.8.8

I'm using network manager to manage connections on this machine, but I have the same results on a machine using netctl and a DHCP ethernet interface.

If I try to ping hosts on my domain (dray.be) they resolve perfectly fine by using this shortname (i.e 'ping foo' for 'foo.dray.be). But not for .local

if I try to ping say 'example.local' it works as expected, finds the IP via mDNS and pings it. but if I just try to ping 'example' without the .local suffix it reports unknown host.

I haven't had much luck finding people with a similar problem, most of my search results seem to load me in circles to Ubuntu forums/bugtrackers which basically amount to people confusing mDNS with DNS.

Any ideas?

branch

Member

Registered: 2014-03-16

Posts: 209

Re: mDNS resolution

I'm surprised it ever worked. My machines have always required the .local suffix to resolve mdns names, and [1] states that since v0.9 (released in 2007) nss-mdns has ignored the domain search list in /etc/resolv.conf.

[1] http://0pointer.de/lennart/projects/nss-mdns/#news

justin-8

Member

From: Queensland, Australia

Registered: 2013-06-18

Posts: 53

Re: mDNS resolution

Interesting. I have no idea how it ever worked then

I'll try and figure something out then. Thanks for that.