Why are only some hosts resolved using DNS?

0

I have a DD-WRT router configured with DNSmasq. The config is

local=/myhome.local/
expand-hosts
addn-hosts=/jffs/hosts.dnsmasq

This way I can resolve network hosts (e.g. ping macbookair), but other hosts does not work. The following hosts work:

  • The router itself
  • My two macs

while the following do not work

  • my AppleTV
  • my Time Capsule
  • iPhones/iPads
  • my RaspberryPI (raspbian)

All hosts display their hostnames under the LAN status page on DD-WRT, so I assume the macs and the router do something special to set things up. Another difference is that the PI does not seem to pick up my local domain name (myhome.local).

What am I missing here?

Krumelur

Posted 2013-09-16T21:56:04.353

Reputation: 587

you got everything up to date on the router & DNSmasq?http://superuser.com/questions/50372/snow-leopard-doesnt-like-dnsmasq

– Logman – 2013-09-16T22:07:49.720

1why won't you show your /jffs/hosts.dnsmasq as well? – Alex P. – 2013-09-16T23:03:42.307

/jffs/hosts.dnsmasq only contains a localhost entry pointing to 127.0.0.1 – Krumelur – 2013-09-17T08:57:12.327

Answers

1

The TLD .local is being used and abused by OSX, and other MDNS services. Trying to use .local on a devices that also run Bonjour(OSX)/Avahi(Linux) is going to be problematic.

Zoredache

Posted 2013-09-16T21:56:04.353

Reputation: 18 453

I will try to change my local domain into something else and see if it helps. – Krumelur – 2013-09-17T08:59:23.713

I finally got around to fixing this. It turned out the hosts worked if I appended a period '.'. Changing DNS suffix so as not to conflict with mDNS will probably solve the problem, but for now I settled with just adding a .ssh/config host alias for the pi (i.e. to 'pi.') (which is the only non-mac I need to access ATM). Thanks! – Krumelur – 2013-09-28T14:50:49.100