On Sun, Jan 24, 2021 at 04:55:25PM +0100, Florian Obser wrote:
> Are you sure you are running with the config you think you are running
> with? I can not reproduce and from the logging, especially the
> check_resolver_done bits it very much looks like you are running
> without any config at all.
I'm sorry, you are right wrt. to getting a synthesized AAAA answer:
that only happens with `dhcp' or `stub'.
> I don't know. So you find yourself in a IPv6 only network which does
> provide a NAT64 service, you'd rather not be able to reach IPv4-only
> services?
For user experience I'd say no, better do that and make things work.
On the other hand, when LAN resolvers are specifically disabled (not
enabled in `preferences {}') one might argue that NAT64 synthesis based
on the LAN's gateway should not be done either.
> Note that from the point of view of DNS you are talking to the right
> destination, we will only do synthesis if we are not receiving a bogus
> answer.
>
> From my point of view detecting presence of NAT64 and doing synthesis
> is independent of the resolving strategy preference. We are not asking
> dhcp or the stub to do resolving, we fire up one query to detect the
> NAT64 prefix.
Right.
> Are you saying you need to switch to turn off DNS64, or is it fine
> like this and you were just surprised?
It's fine and I've probably misinterpreted things in that I thought of
both detection and synthesis as part of the resolving strategy.
The diff is working and the code reads fine, thanks for your work and
feedback on this.
OK kn
