[Dnsmasq-discuss] NXDOMAIN instead of NODATA-IPv6
e9hack
e9hack at gmail.com
Sat Sep 13 09:10:06 BST 2014
Hi,
I'm using dnsmasq for DHCP and DHCPv6. Name resolution doesn't work on a Windows8 PC for a
IPv4 only host on LAN, but it works for IPv4 only hosts on WAN.
If I compare the log entries, the answer of an AAAA query for a host on LAN is NXDOMAIN
and for a host on WAN NODATA-IPv6.
daemon.info dnsmasq[24299]: started, version 2.72rc1 cachesize 150
daemon.info dnsmasq[24299]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN
DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect
daemon.info dnsmasq[24299]: DNSSEC validation enabled
daemon.info dnsmasq[24299]: query[A] vbox-linux.lan from 192.168.102.2
daemon.info dnsmasq[24299]: /tmp/hosts/dhcp vbox-linux.lan is 192.168.102.50
daemon.info dnsmasq[24299]: query[AAAA] vbox-linux.lan from 192.168.102.2
daemon.info dnsmasq[24299]: config vbox-linux.lan is NXDOMAIN
daemon.info dnsmasq[24299]: query[A] www.thoralt.de from 192.168.102.2
daemon.info dnsmasq[24299]: cached www.thoralt.de is 79.140.41.184
daemon.info dnsmasq[24299]: query[AAAA] www.thoralt.de from 192.168.102.2
daemon.info dnsmasq[24299]: cached www.thoralt.de is NODATA-IPv6
Windows8 seems to cache negative replies. The first access to the local IPv4 only host
works, all following access fail. The access works again for one time, if the DNS cache is
flush manually.
Regards
Hartmut
More information about the Dnsmasq-discuss
mailing list