4 ms·

So if a domain only has a AAAA record, and for whatever reason a user can’t use IPv6, what sort of error message would the user see?

strbean 3y ago
Found https://test-ipv6.com https://test-ipv6.com and: https://ipv6.ams2.test-ipv6.com/ip/?callback=?&testdomain=test-ipv6.com&testname=test_aaaa https://ipv6.ams2.test-ipv6.com/ip/?callback=?&testdomain=te... I get the following from Chrome: > This site can’t be reached > Check if there is a typo in ipv6.ams2.test-ipv6.com. >DNS_PROBE_FINISHED_NXDOMAIN
- miyuru 3y ago
  >>DNS_PROBE_FINISHED_NXDOMAIN This is because your OS is not querying AAAA records. I am gonna guess that your using macos. The most common error would be a "connection time out".
  - strbean 3y ago
    I'm not sure, but I believe I was on Windows 10 at the time. Shortly after this, I checked the appropriate boxes on my router (UDM-PRO) and my home network now supports IPv6. Passed all the tests on that website at least.
pravus 3y ago
The client shouldn't even attempt to get an AAAA record unless they have an IPv6 stack available. In that case, their client should try to look up an A record and get an NXDOMAIN error which the browser usually shows as "IP address could not be found". If the client does attempt IPv6, you'll get a stack error when trying to connect to the remote host because the kernel will reject the address family and you'll get something like "network is unreachable". Some clients will also degrade from AAAA to A on error so you'll get the NXDOMAIN error as above.
- MayeulC 3y ago
  I wrote this a few years ago, but I feel like putting a dedicated IPv4 like 66.66.66.66 in the A record would inform the web browser or other software that the website is only reachable via IPv6, and a more informative error message could be displayed. This would require a proper RFC of course, with support from IANA and web browsers.

strbean 3y ago

Found https://test-ipv6.com https://test-ipv6.com and: https://ipv6.ams2.test-ipv6.com/ip/?callback=?&testdomain=test-ipv6.com&testname=test_aaaa https://ipv6.ams2.test-ipv6.com/ip/?callback=?&testdomain=te... I get the following from Chrome: > This site can’t be reached > Check if there is a typo in ipv6.ams2.test-ipv6.com. >DNS_PROBE_FINISHED_NXDOMAIN

miyuru 3y ago
>>DNS_PROBE_FINISHED_NXDOMAIN This is because your OS is not querying AAAA records. I am gonna guess that your using macos. The most common error would be a "connection time out".
- strbean 3y ago
  I'm not sure, but I believe I was on Windows 10 at the time. Shortly after this, I checked the appropriate boxes on my router (UDM-PRO) and my home network now supports IPv6. Passed all the tests on that website at least.

pravus 3y ago

The client shouldn't even attempt to get an AAAA record unless they have an IPv6 stack available. In that case, their client should try to look up an A record and get an NXDOMAIN error which the browser usually shows as "IP address could not be found". If the client does attempt IPv6, you'll get a stack error when trying to connect to the remote host because the kernel will reject the address family and you'll get something like "network is unreachable". Some clients will also degrade from AAAA to A on error so you'll get the NXDOMAIN error as above.

MayeulC 3y ago
I wrote this a few years ago, but I feel like putting a dedicated IPv4 like 66.66.66.66 in the A record would inform the web browser or other software that the website is only reachable via IPv6, and a more informative error message could be displayed. This would require a proper RFC of course, with support from IANA and web browsers.