Describe the bug
Due to a config bug, I had v4 not working on the domain but working on the subdomain well-known was pointing at. (Aka missing A record on the main domain).
However, as the well-known had been resolved via v6, the fedtester incorrectly reported everything was fine. Instead, it should at least warn about the fact that the well-known file cannot be resolved via v4.
To Reproduce
Have an AAAA only record on the main domain where well-known is at, and a and AAAA one on the domain it points to.
Expected behavior
Fedtester warns or reports that well-known cannot be reached while the server itself can. As this will break fed for v4-only servers trying to talk to this server.
Yep. Though with a different cause. #103 assumes there are dns records for both and only then it fails. While this assumes one dns record is missing entirely.
Describe the bug Due to a config bug, I had v4 not working on the domain but working on the subdomain well-known was pointing at. (Aka missing A record on the main domain).
However, as the well-known had been resolved via v6, the fedtester incorrectly reported everything was fine. Instead, it should at least warn about the fact that the well-known file cannot be resolved via v4.
To Reproduce Have an AAAA only record on the main domain where well-known is at, and a and AAAA one on the domain it points to.
Expected behavior Fedtester warns or reports that well-known cannot be reached while the server itself can. As this will break fed for v4-only servers trying to talk to this server.
Screenshots![image](https://user-images.githubusercontent.com/1374914/172054408-50c59bc7-94f4-4ee6-be8f-5be85988b3d0.png)