Networks which only have tunneled IPv6 access but still want to go
IPv6-only internally can use unbound's DNS64 module together with the
dns64-synthall or dns64-ignore-aaaa options to direct most traffic (any
dualstack domain) to their NAT64.
There is only one problem with this setup, currently domains with only AAAA
records will fail to resolve.
To allow for this use-case arrange for the A sub-query to make the AAAA
super query advance along the module stack when no records are returned.
The change looks good for me.
It does change current behavior but I think that the new behavior (when asked to synthesize but no A exists, fallback to the existing AAAA) makes sense for a default configuration.
However, I am not a DNS64 operator so if people here feel differently a new option could be introduced for that.
I already committed this (and the other patches, thanks!) to the repository and an extra option could be introduced in the future if people see the need for it.
The change looks good for me.
It does change current behavior but I think that the new behavior (when
asked to synthesize but no A exists, fallback to the existing AAAA) makes
sense for a default configuration.
I tend to agree I can't really think of a reason (other than debugging the
module?) to not want a fallback here.
I already committed this (and the other patches, thanks!) to the repository
and an extra option could be introduced in the future if people see the need
for it.
Excellent. I'll keep on hacking on the dns64 module then. I want to get to
about feature parity with BIND
