Dnsmasq randomly returns "no answer" on OpenWrt 19.07

Installing and Using OpenWrt
1

I noticed that dnsmasq seems to randomly return "No answer" for DNS queries on the router:

root@OpenWrt:~# nslookup twitter.com
Server:		127.0.0.1
Address:	127.0.0.1#53

Name:      twitter.com
Address 1: 104.244.42.1
Address 2: 104.244.42.129
*** Can't find twitter.com: No answer
root@OpenWrt:~# nslookup google.com
Server:		127.0.0.1
Address:	127.0.0.1#53

Name:      google.com
Address 1: 172.217.171.238
Address 2: 2a00:1450:4006:808::200e

The log shows:

Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 95 127.0.0.1/40459 query[A] twitter.com from 127.0.0.1
Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 95 127.0.0.1/40459 cached twitter.com is 104.244.42.1
Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 95 127.0.0.1/40459 cached twitter.com is 104.244.42.129
Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 96 127.0.0.1/40459 query[AAAA] twitter.com from 127.0.0.1
Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 96 127.0.0.1/40459 forwarded twitter.com to 8.8.8.8
Fri Dec 25 15:20:46 2020 daemon.info dnsmasq[2951]: 96 127.0.0.1/40459 forwarded twitter.com to 8.8.4.4
Fri Dec 25 15:20:47 2020 daemon.info dnsmasq[2951]: 96 127.0.0.1/40459 reply twitter.com is NODATA-IPv6

In this case I am using 8.8.8.8 and 8.8.4.4 for upstream DNS on the LAN interface:

root@OpenWrt:~# cat /tmp/resolv.conf.auto
# Interface lan
nameserver 8.8.8.8
nameserver 8.8.4.4

DNS resolution on Wi-Fi client hosts is working fine otherwise, but I'm wondering what is going on here. My router is running an OpenWrt 19.07 snapshot that I built.

2

This looks normal, it just happens that "twitter.com" does not have an IPv6 address.

3

OK I installed bind-dig and the output is much more user friendly. The error message from nslookup is misleading. This was my first and last time ever using nslookup! Thanks.

1 Like
4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.