Ubuntu avahi-daemon creates problem resolving FQDNs ending with .local
I have started to use .local dns extension for my local network. After changing my complete network configuration I realized that some of my Ubuntu machines can resolve the FQDNs ending with .local (Ex: testhost.digitalpains.local ) correctly.
ali@advance17:/home/ali$ ping testhost.digitalpains.local ping: unknown host testhost.digitalpains.local ali@advance17:/home/ali$ ping testhost PING testhost.feasiblesolutions.local (192.168.7.2) 56(84) bytes of data. 64 bytes from 192.168.7.2: icmp_seq=1 ttl=64 time=1.02 ms 64 bytes from 192.168.7.2: icmp_seq=2 ttl=64 time=1.12 ms
After some research it turned out that avahi-daemon was interfering the DNS resolve process and FQDNs ending with .local extension wasn’t being resolved.
After I stopped the avahi-daemon service I was able to resolve
ali@advance17:/home/ali$ sudo stop avahi-daemon avahi-daemon stop/waiting ali@advance17:/home/ali$ ping testhost.feasiblesolutions.local PING testhost.feasiblesolutions.local (192.168.7.2) 56(84) bytes of data. 64 bytes from 192.168.7.2: icmp_seq=1 ttl=64 time=2.05 ms 64 bytes from 192.168.7.2: icmp_seq=2 ttl=64 time=1.16 ms 64 bytes from 192.168.7.2: icmp_seq=3 ttl=64 time=4.25 ms
After reboot avahi-daemon service will start automatically. On Ubuntu Karmic edition adding the following line to you r /etc/avahi/avahi-daemon.conf file will solve the problem permanently.
AVAHI_DAEMON_DETECT_LOCAL=0
Related posts:
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
