The ipv6 records hosted by Cloudflare point to the wrong destination server.
======================== dig @173.245.58.111 `webmail.imap.cfored.com` AAAA +short
2606:4700:30::6812:2ac6
2606:4700:30::6812:2bc6
========================
dig @173.245.59.97webmail.imap.cfored.com AAAA +short
2606:4700:30::6812:2ac6
2606:4700:30::6812:2bc6
========================
Whereas, the ipv4 records point to the correct server
======================== $ curl -4 https://webmail.imap.cfored.com:2096 -k
How do I update the ipv6 records to point to the correct destination server?
On the Cloudflare side can you try going to the “Network” portion and try disabling “IPv6 Compatibility” as I believe that is what is causing ipv6 to come in to play in this situation. It also looks like they may require that this be done via their API so I’ve added some documentation for that below:
Can we create a Cloudflare firewall rule for the hostname: webmail.imap.cfored.com to allow traffic; then, create AAAA record for the subdomain webmail.imap?
How do I create a new host on the Cloudflare DNS services that resolves directly to the imap.cfored.com server and does not go through Cloudflare’s protections?.