Need AAAA records for ip6 server address for email deliverability
-
I see now. The check is only for PTR record . There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
-
I see now. The check is only for PTR record . There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
@joseph said in Need AAAA records for ip6 server address for email deliverability:
There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
Except that for DNS record for apps, if not properly set-up DNS propagation doesn't work and when using say Wildcare DNS, the docs clearly says we should set-up a A record but says nothing about AAAA record, neither for apps, nor for email config:
https://docs.cloudron.io/domains/#wildcard-dns
Given the number of issues we've seen on the forum with IPv6, I really think some tidying needs to happen to make Cloudron as neat with IPv6 as it is with IPv4, either in Cloudron back-end with automated set-up and checks, or in the Cloudron documentation.
-
@joseph said in Need AAAA records for ip6 server address for email deliverability:
There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
Except that for DNS record for apps, if not properly set-up DNS propagation doesn't work and when using say Wildcare DNS, the docs clearly says we should set-up a A record but says nothing about AAAA record, neither for apps, nor for email config:
https://docs.cloudron.io/domains/#wildcard-dns
Given the number of issues we've seen on the forum with IPv6, I really think some tidying needs to happen to make Cloudron as neat with IPv6 as it is with IPv4, either in Cloudron back-end with automated set-up and checks, or in the Cloudron documentation.
@avatar1024 said in Need AAAA records for ip6 server address for email deliverability:
either in Cloudron back-end with automated set-up and checks, or in the Cloudron documentation.
Both
-
@joseph said in Need AAAA records for ip6 server address for email deliverability:
There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
Except that for DNS record for apps, if not properly set-up DNS propagation doesn't work and when using say Wildcare DNS, the docs clearly says we should set-up a A record but says nothing about AAAA record, neither for apps, nor for email config:
https://docs.cloudron.io/domains/#wildcard-dns
Given the number of issues we've seen on the forum with IPv6, I really think some tidying needs to happen to make Cloudron as neat with IPv6 as it is with IPv4, either in Cloudron back-end with automated set-up and checks, or in the Cloudron documentation.
@avatar1024 said in Need AAAA records for ip6 server address for email deliverability:
to make Cloudron as neat with IPv6 as it is with IPv4
The entire internet is still coming to terms with IPv6, still! Personally, at this point, I think it's equally on users to choose VPS providers who offer/don't offer IPv6 as it is on companies like Cloudron. The issues equally stem from software not handling networking competently as it is servers not implementing IPv6 competently. Perhaps we need to share which VPSes are working without a hitch, and which aren't. For example, I was looking into Infomaniak a little while ago because they had a free 1TB storage offer on lowendbox, but I was too late, and now it seems there are hassles anyway with Infomaniak. I've had some servers in the past with network headaches... I just moved away from them.
A life lived in fear is a life half-lived
-
@avatar1024 said in Need AAAA records for ip6 server address for email deliverability:
to make Cloudron as neat with IPv6 as it is with IPv4
The entire internet is still coming to terms with IPv6, still! Personally, at this point, I think it's equally on users to choose VPS providers who offer/don't offer IPv6 as it is on companies like Cloudron. The issues equally stem from software not handling networking competently as it is servers not implementing IPv6 competently. Perhaps we need to share which VPSes are working without a hitch, and which aren't. For example, I was looking into Infomaniak a little while ago because they had a free 1TB storage offer on lowendbox, but I was too late, and now it seems there are hassles anyway with Infomaniak. I've had some servers in the past with network headaches... I just moved away from them.
@scooke Yet we live in a world where what we want or think matters less than what Google & Microsoft (and Meta) will allow us to do. Which in this case, is send email to "their" "users" (addicts).
-
@marcusquinn I agree with you. But since Cloudron, which works normally on many other servers, isn't on whichever you're using, why keep banging your head against a wall? Move to a server which works. In this regard you have the advantage that moving an entire Cloudron to a new server is straightforward.
A life lived in fear is a life half-lived
-
@marcusquinn I agree with you. But since Cloudron, which works normally on many other servers, isn't on whichever you're using, why keep banging your head against a wall? Move to a server which works. In this regard you have the advantage that moving an entire Cloudron to a new server is straightforward.
@scooke No wall head-banking here. I solved the problem. I was just sharing the solution here for others, and suggesting a notification could also help save others from the same issue.
Maybe there's some misunderstanding, but I don't need to move servers — and "easy" is relative, since I have a lot of apps and data moving around the clock, so it's no trivial to migrate without data loss during the migration, and my time is too precious to lose it to migrations that I don't need to, when there's no problem here that would need any migration.
-
I've been having issues with email deliverability to Google & Microsoft servers.
It seems that as well as now needing a PTR record for the ip6 on the host, we also need AAAA records for the subdomain (
mail.in my case), to point to that same ip6 address (any DNS proxying disabled, too).I only just learned of the ip6 option on the Network settings page. Perhaps there should be a warning when that's not set?
Probably something Cloudron DNS setup should be able to check and automate? @girish @nebulon
@marcusquinn PTR setup would require a bit deeper integration into various hosting provider API (if they even allow one to set PTR via API). Checking could indeed be automated.
-
I see now. The check is only for PTR record . There is no check for AAAA record (or A record) for that matter. In general, even for apps there is no such check i.e Cloudron is not polling periodically to check if the DNS records are in sync.
-
@joseph Right. But Cloudron does check for e-mail setup. It seems what's being asked for (and I agree) is ipv6 related mail health check as part of the periodic e-mail health check Cloudron does already.
@charlesnw yes, the OP is a recommendation to add this as a health check notification. I don't think it would be practical to try and automate the setup, when a simple notification to advise it is missing and needs the user to setup with their hosting would save from a lot of bounced mail head-scratching.
I solved this for myself through accidental discovery.
There's no greater crime than wasting someone's time, and any user not knowing this is needed could lose unlimited amounts of time not knowing this is the problem.
Basic need.
Basic solution.
No reason to debate if this is a good idea.
Just persuade that it would be a respectful thing to implement.
As I say, I'm alright.
I'm giving time to this thread to help save others from lost time from not knowing this is their issue.
