I use dnsmasq for DNS name caching. In dnsmasq.conf I have strict-order specified.
In /etc/resolv.conf are these directives:
I have www.slackbuilds.org listed in /etc/hosts:
When I use dig to test www.slackbuilds.org, the dnsmasq log shows only a localhost lookup. This is expected because no external DNS name server is needed. For example:
dig @localhost www.slackbuilds.org +short
Dec 7 16:52:22 dnsmasq: query[A] www.slackbuilds.org from 127.0.0.1
Dec 7 16:52:22 dnsmasq: /etc/hosts www.slackbuilds.org is 126.96.36.199
When I use dig to query a domain name not in /etc/hosts, the dnsmasq log shows the results of an expected external query. For example:
dig @localhost www.h-online.org +short
Dec 7 16:54:18 dnsmasq: query[A] www.h-online.org from 127.0.0.1
Dec 7 16:54:18 dnsmasq: forwarded www.h-online.org to 188.8.131.52
Dec 7 16:54:18 dnsmasq: reply www.h-online.org is 184.108.40.206
So far so good. Now for the quirk.
When I fetch the slackbuilds.org RSS feed with akregator, which uses the www.slackbuild.org domain, the dnsmasq log shows an external DNS server lookup:
Dec 7 16:55:04 dnsmasq: query[AAAA] www.slackbuilds.org from 127.0.0.1
Dec 7 16:55:04 dnsmasq: forwarded www.slackbuilds.org to 220.127.116.11
Dec 7 16:55:05 dnsmasq: reply www.slackbuilds.org is <CNAME>
Why does dnsmasq forward a lookup request to 18.104.22.168 when I use akregator but not with dig?
Edit: dnsmasq 2.52 on Slackware 13.1
because akregator asks for the AAAA record (ipv6) as you may see
Okay, thank you. I did not know what AAAA meant. :) I will have to learn more. Now that you've explained what is happening, why is akregator asking for an ipv6 address when an ipv4 address already exists?
Well, it's up to Akregator wich record to ask, maybe you may have a look to the settings. At the moment i find ipv6 pretty pointless so i just blacklist the module and i'm happy with that
Looks like the problem is AAAA lookups are performed before A. A possible solution is editing /etc/resolv.conf with 'options single-request'. Also, /etc/hosts has to be updated with a feedback loop for IPv6. I haven't worked my way through or tested all of this yet. For now, like you, I've gone back to disabling ipv6 system-wide.
|All times are GMT -5. The time now is 11:24 AM.|