#964 prosodyctl check should handle the case where the IPv4 is local and the IPv6 global
Reporter
Link Mauve
Owner
Nobody
Created
Updated
Stars
★★ (2)
Tags
Status-NeedInfo
Priority-Medium
Type-Defect
Link Mauve
on
What steps will reproduce the problem?
1. Have a server behind an IPv4 NAT.
2. Have a domain name correctly configured in Prosody.
3. Have an A record pointing to the external IPv4 of your NAT, and an AAAA record pointing to your server’s IPv6.
4. Run `prosodyctl check`.
What is the expected output?
No complaint.
What do you see instead?
Checking DNS for host linkmauve.fr...
linkmauve.fr. A record points to unknown address 82.226.255.187
Host linkmauve.fr. does not seem to resolve to this server (IPv4)
Only some targets for linkmauve.fr appear to resolve to this server.
What version of the product are you using? On what operating system?
Prosody 0.10 as of 7386:39188851811c, on ArchLinuxARM.
Please provide any additional information below.
N/A
Zash
on
Changes
tags Status-Accepted
Zash
on
I can't reproduce. Is this still an issue? There have been many improvements to this area over the years since this was filed
What steps will reproduce the problem? 1. Have a server behind an IPv4 NAT. 2. Have a domain name correctly configured in Prosody. 3. Have an A record pointing to the external IPv4 of your NAT, and an AAAA record pointing to your server’s IPv6. 4. Run `prosodyctl check`. What is the expected output? No complaint. What do you see instead? Checking DNS for host linkmauve.fr... linkmauve.fr. A record points to unknown address 82.226.255.187 Host linkmauve.fr. does not seem to resolve to this server (IPv4) Only some targets for linkmauve.fr appear to resolve to this server. What version of the product are you using? On what operating system? Prosody 0.10 as of 7386:39188851811c, on ArchLinuxARM. Please provide any additional information below. N/A
I can't reproduce. Is this still an issue? There have been many improvements to this area over the years since this was filed
Changes