Our DNSMasq is not able to resolve A, CNAME nor Alias records from public domains that specify private IP addresses.
$ nslookup > server 172.16.1.1 Default server: 172.16.1.1 Address: 172.16.1.1#53 > www.work-domain.com Server: 172.16.1.1 Address: 172.16.1.1#53 Non-authoritative answer: Name: www.work-domain.com Address: 55.77.XXX.XXX > server-b.work-domain.com Server: 172.16.1.1 Address: 172.16.1.1#53 Non-authoritative answer: *** Can't find server-b.work-domain.com: No answer
But switching to a public DNS works fine:
$ nslookup > server 126.96.36.199 Default server: 188.8.131.52 Address: 184.108.40.206#53 > www.work-domain.com Server: 220.127.116.11 Address: 18.104.22.168#53 Non-authoritative answer: Name: www.work-domain.com Address: 55.77.XXX.XXX > server-b.work-domain.com Server: 22.214.171.124 Address: 126.96.36.199#53 Non-authoritative answer: Name: server-b.work-domain.com Address: 10.1.XXX.XXX
server-b.work-domain.com entry properly resolvs to a non-routable IP address of
10.1.XXX.XXX? That's my problem, that does not work with my local dnsmasq on the local network.
These IP addresses are part of our Amazon AWS private subnets, and we have VPNs to gain access to them.
This is all 100% consistent of all 200+ servers registered with 4 different public domains across several subnets, all using a private non-routable IP address. But yet, all other records using public routable IP addresses work just fine, on the same domain!
Everything else is 100% working normally with local dnsmasq:
- resolves all public domains
- resolves all IP reverse lookups of public IPs
- resolves all internal private domain and hosts
- resolves all IP reverse lookups of private IPs and DHCP leases
It's just public records using private non-routable IPs.
I must be missing some option that I am unable to interrupt reading the MAN page.
Dnsmasq version 2.73 # (part of AdvancedTomato)
Configuration (removed sensitive entries, left example ones):
# dhcp-option=lan,3,172.16.1.1 cache-size=8192 log-async=25 strict-order #local=/lan/ #domain=lan,172.16.1.0/24,local expand-hosts domain-needed # network devices address=/router-gateway.lan/172.16.1.1 address=/router-office.lane/172.16.1.2 ...and so on x 70 # arpa entries ptr-record=188.8.131.52.in-addr.arpa,"router-gateway.lan" ptr-record=184.108.40.206.in-addr.arpa,"router-office.lan" ...and so on
Local resolvs on AdvancedTomato spits out:
# cat /etc/resolv.conf nameserver 127.0.0.1 # cat /etc/resolv.dnsmasq nameserver 220.127.116.11 nameserver 18.104.22.168
Again.. Everything works perfectly with local LAN on Windows, OSX and Linux clients resolving public and internal domains and LANs and even hosts without the domain suffix (server-xyz -> resolves to server-xyz.lan).
It's just public domains that use non-routable IPs.