The behavior I'm seeing it that any host with dnsmasq in it's query path when running dig returns an A record the response is NOERROR and the answer section has an A record which looks like
192.168.100.100. 0 IN A 192.168.100.100 If I perform a dig against the upstream server directly I receive an NXDOMAIN. I made the assumption that dnsmasq was creating this response was coming from dnsmasq. I'll do a more detailed investigation to validate that is true. On Wed, Mar 30, 2016 at 3:15 PM, /dev/rob0 <r...@gmx.co.uk> wrote: > On Wed, Mar 30, 2016 at 01:05:32PM -0400, Jeff Weber wrote: > > I'm using dnsmasq as a local dns cache on some servers and I've > > noticed recently (due to some buggy software) that if you dig for > > an ip address you get an A record back which is set to that ip > > The proper use of dig of an IP address (for example, 192.0.2.53) is > "dig -x 192.0.2.53". This changes the query to a type PTR for > 53.2.0.192.in-addr.arpa. > > By default dig queries for A, and "dig 192.0.2.53" will cause a > recursive server to ask the root servers for a "53" top-level domain. > The fact that ICANN has not yet tried to turn all-numeric TLDs into > money makers notwithstanding, there is no protocol reason why it > cannot be done. > > > address. I went through the manual and wasn't able to find an > > option which seems like it could make this configurable. Is there a > > way to turn this response into an NXDOMAIN instead of returning the > > synthesized A record? > > > > I'm using dnsmasq verision 2.66 on a Centos 7 machine. > -- > http://rob0.nodns4.us/ > Offlist GMX mail is seen only if "/dev/rob0" is in the Subject: > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
