Timeline for Convince android to use AAAA records when VPN has IPv6 but main connectivity doesn't
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 4 at 2:47 | comment | added | cth451 | @IanB No documentation as I am aware of, but this behavior does make some sense. If you don't have a IPv6 default route you most likely aren't connected to the wider IPv6 address space (by extension the Internet). No point to resolve an AAAA if it can't be routed. In my case, the VPN route a IPv6 internal network w/ a local AAAA resolver that only resolves some internal domains into ULAs. I think android can still attempt to resolve AAAA and fallback to A records if it turns out to match no routes IMHO, but google is google. | |
| Jul 2 at 11:50 | comment | added | IanB | Thanks, this solved the problem for me. I'm curious to understand the reasoning for this behaviour. Do you know if there is any documentation about it? | |
| Sep 6, 2023 at 18:48 | review | Late answers | |||
| Sep 6, 2023 at 20:14 | |||||
| S Sep 6, 2023 at 18:32 | review | First answers | |||
| Sep 6, 2023 at 20:10 | |||||
| S Sep 6, 2023 at 18:32 | history | answered | cth451 | CC BY-SA 4.0 |