You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With PREF64 being available, some networks might only provide PREF64 and do not use DNS64, as the latter has a number of disadvantages, such as breaking DNSSEC and not working if the host has custom DNS
servers configured.
So do you think it's worth adding some text saying that some Ipv6-only
or, more likely, IPv6-mostly networks might only deploy PREF64 w/o DNS64?
I think we need to clarify that clients need to send an A query in addition to a AAAA query if PREF64 is available, to ensure that the network doesn't need to run DNS64.
Maybe we treat this scenario similar to how we handled hostnames with broken AAAA records in HEv2 ? (Try AAAA first and if that doesn't work then try A? Or are we expecting PREF64 without DNS64 to be common and expected?
(copying from an email I sent to the authors)
With PREF64 being available, some networks might only provide PREF64 and do not use DNS64, as the latter has a number of disadvantages, such as breaking DNSSEC and not working if the host has custom DNS
servers configured.
So do you think it's worth adding some text saying that some Ipv6-only
or, more likely, IPv6-mostly networks might only deploy PREF64 w/o DNS64?
See https://www.ietf.org/archive/id/draft-link-v6ops-6mops-00.html#name-dns-vs-dns64
The text was updated successfully, but these errors were encountered: