问题原文
原帖链接 · Nils Toedtmann · CC BY-SA 3.0
... to compensate for broken DNS servers that are outside our control.
Our problem: We deploy embedded devices that collect sensor data at various, mostly IPv4-only sites. Some sites have poorly maintained networks, e.g. misconfigured or otherwise broken DNS caches and/or firewalls that either ignore AAAA queries altogether, or respond to them with broken replies (e.g. wrong source IP!). As an external supplier to the facilities department, we have next to no influence on the (sometimes reluctant) IT departments. The chances of them fixing their DNS servers/firewalls any time soon are minuscule.
The effect on our device is that with each gethostbyname(), the processes have to wait until the AAAA queries time out, at which point some processes have already timed out their connection attempts altogether.
I am looking for solutions that are ...
- system-wide. I cannot reconfigure dozens of application individually
- non-permanent and configurable. We need to (re-)enable IPv6 where/when it gets fixed/rolled out. Reboot is OK.
- If a solution requires a core library like glibc to be replaced, the replacement library package should be available from a known-to-be-well-maintained repository (e.g. Debian Testing, Ubuntu universe, EPEL). Self-building is not an option for so many reasons that I don't even know where to begin with, so I just don't list them at all...
The most obvious solution would be to configure the resolver library e.g. via /etc/{resolv,nsswitch,gai}.conf to not query AAAA records. A resolv.conf option no-inet6 as suggested here would be exactly what i am looking for. Unfortunately it is not implemented, at least not on our systems (libc6-2.13-38+deb7u4 on Debian 7; libc6-2.19-0ubuntu6.3 on Ubuntu 14.04)
So how then? One finds the following methods suggested on SF and elsewhere, but non of them work:
- Disabling IPv6 altogether, e.g. by blacklisting the ipv6 LKM in /etc/modprobe.d/, or
sysctl -w net.ipv6.conf.all.disable_ipv6=1. (Out of curiosity: Why is the resolver asking for AAAA where IPv6 is disabled?) - Removing
options inet6from /etc/resolv.conf. It wasn't there in the first place,inet6is simply enabled by default these days. - Setting
options single-requestin /etc/resolv.conf. This only ensures that the A and the AAAA queries are done sequentially rather than in parallel - Changing
precedencein /etc/gai.conf. That does not affect the DNS queries, only how multiple replies are processed. - Using external resolvers (or running a local resolver daemon that circumvents the broken DNS servers) would help, but is usually disallowed by the company's firewall policies. And it can make internal resources inaccessible.
Alternative ugly ideas:
- Run a DNS cache on localhost. Configure it to forward all non-AAAA queries, but to respond to AAAA queries with either NOERROR or NXDOMAIN (depending on the result of the corresponding A-query). I am not aware of a DNS cache able to do this though.
- Use some clever iptables u32 match, or Ondrej Caletka's iptables DNS module to match AAAA queries, in order to either icmp-reject them (how would the resolver lib react to that?), or to redirect them to a local DNS server that responds to everything with an empty NOERROR.
Note that there are similar, related questions on SE. My question differs insofar as it elaborates the actual problem i am trying to solve, as it lists explicit requirements, as it blacklists some often-suggested non-working solutions, and as it is not specific to a single application. Following this discussion, I posted my question.
- IPv6 DNS Lookup
- How to disable requesting AAAA records when I have no IPv6 address?
- Disable AAAA lookups in libcurl
已采纳解答
原帖链接 · MrDrMcCoy · CC BY-SA 4.0
For recent systems, there is an option that you can set to do this in /etc/resolv.conf:
no-aaaa (since glibc 2.36)
Sets RES_NOAAAA in _res.options, which suppresses
AAAA queries made by the stub resolver, including
AAAA lookups triggered by NSS-based interfaces such
as getaddrinfo(3). Only DNS lookups are affected:
IPv6 data in hosts(5) is still used, getaddrinfo(3)
with AI_PASSIVE will still produce IPv6 addresses,
and configured IPv6 name servers are still used.
To produce correct Name Error (NXDOMAIN) results,
AAAA queries are translated to A queries. This
option is intended preliminary for diagnostic
purposes, to rule out that AAAA DNS queries have
adverse impact. It is incompatible with EDNS0
usage and DNSSEC validation by applications.
This can be a helpful config setting for Docker containers in environments where the host is configured for IPv6, but Docker isn't.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
