An A query for an AAAA only name should return a 0 answer NOERROR (so "there is an answer, but no value")
nweaver% dig ipv6.l.google.com ; <<>> DiG 9.6.0-APPLE-P2 <<>> ipv6.l.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59724 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ipv6.l.google.com. IN A ;; Query time: 4 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon Apr 25 05:10:54 2011 ;; MSG SIZE rcvd: 35 > version.bind. 0 CH TXT "dnsmasq-2.51" AAAA records are queried for SEPARATELY, as a separate rtype. If a computer wants both records, it needs to query for them both. If you are indeed getting NXDOMAIN and not 0-answer NOERROR I suspect its not DNSMASQ but the upstream resolver. On Mon, Apr 25, 2011 at 3:17 AM, Modem Man <modem-...@gmx.net> wrote: > Hi, > > didn't found anything at the Kellys Web Site, so I hope you have the > same issue... > > - My hardware is a Linksys NSLU2 > - My OS is Linux "OpenSLUG 5.3/LE" + optware + dnsmasq (2.47-r0 via opkg) > - So I have *no* IPv6 stack on the NSLU2 > - my (Windows XP as well as Debian Squeeze) PCs are querying a DNS name > which only has IPv6 "AAAA" record (I know, it only has a IPv6 record, it > is: "v6.testmyipv6.com" ) > > => Problem: dnsmasq answers with NX record > > Is this intentional? The AAAA content of DNS record is - for my > understanding - also included in IPv4 based queries. So I expect the > NSLU2/dnsmasq will ask the ISP's DNS server, get an answer and deliver > it to my PC, regardless of "A" or "AAAA" content. The PC then can decide > if using AAAA or A record. So, there is no need to have IPv6 kernel > module in NSLU2, or am I wrong? > Or is my dnsmasq 2.47-r0 from optware feed somehow stripped down to only > IPv4? Where can I see this? > > unsure, > Modem Man > > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >