Bug #13033
closedDNS lookups using DNS forwarder yields invalid cache entries in systemd-resolved
0%
Description
I have configured a wildcard record in DNS forwarder, supplied in the "custom options" like the following:
address=/example.com/10.0.0.1
and host overrides:
example.com -> 10.0.0.1
a.example.com -> 10.0.0.1
b.example.com -> 10.0.0.2
On a Ubuntu 18.04 machine, running a lookup specifying IPv6
systemd-resolve -6 b.example.com
yields:
b.example.com: resolve call failed: 'a.nowhow.ch' does not have any RR of the requested type
This request adds, however, an entry in the cache of systemd-resolved:
#011b.example.com IN CNAME a.example.com
(this can be seen from running "sudo killall -USR1 systemd-resolved" and looking at the syslog.)
Running
systemd-resolve -4 b.example.com
now results in
b.example.com: 10.0.0.1 (a.example.com)
This behaviour seems to be new to 2.6.0 and resulted in wrong DNS lookups, as systemd-resolved seems to aquire both IPv4 and IPv6 addresses by default (according to man pages)
Related issues
Updated by Jim Pingle over 2 years ago
- Status changed from New to Duplicate
Looks like a duplicate of #12902
Updated by Jim Pingle over 2 years ago
- Is duplicate of Bug #12902: DNS Forwarder creates a loop when "Use local DNS, ignore remote DNS servers" is selected added
Updated by Philipp Hoppen over 2 years ago
Not sure about this being a duplicate, since we have "Use local DNS, fall back to remote DNS servers" configured in pfsense, as is the default setting.
Updated by Flole Systems over 2 years ago
I'm pretty sure it's not a duplicate. It could be a duplicate of #12901 though....