IPv6 configuration issue

Question

Hi,

While testing our website https://www.csu.nl/ on Internet.nl, I noticed that IPv6 is not correctly configured. According to the report, the IPv6 address is not pointing to the server hosting the website.

Could you verify the current IPv6 configuration and advise what needs to be adjusted to properly support IPv6 and resolve this issue?

For reference, here is the test result: https://internet.nl/site/www.csu.nl/3853633/

Thanks in advance!

Bobby · Answer

Hi there, From the test results you shared, it looks like your AAAA record is correctly configured and pointing to an IPv6 address, but the issue is that the server is not reachable over IPv6 on ports 80/443. So this is likely not a DNS problem, but something on the server or network side. A few things to check: Make sure IPv6 is enabled and configured on the Droplet itselfYou can verify that the address 2a03:b0c0:2:d0::1293:8001 is actually assigned using ip -6 addr Check that your web server is listening on IPv6For example, in Nginx you should have:listen [::]:80; and listen [::]:443;Otherwise it will only accept IPv4 connections Verify firewall rulesMake sure IPv6 traffic is allowed on ports 80 and 443 (UFW, iptables, or DigitalOcean Cloud Firewalls). It’s quite common for IPv4 to be open while IPv6 is unintentionally blocked Test connectivity directly over IPv6For example:curl -6 http://www.csu.nlorcurl -6 http://[2a03:b0c0:2:d0::1293:8001] Check if services are binding only to IPv4Some setups bind to 0.0.0.0 but not ::, which results in exactly this behavior Since Internet.nl is specifically reporting the IPv6 address as unreachable, in most cases it comes down to either the web server not listening on IPv6 or IPv6 traffic being blocked by a firewall. If everything looks correct and it’s still not reachable, it might be worth reaching out to support so they can double-check the networking from their side as well:https://do.co/support

alexdo · Answer

Heya, You can check what your AAAA record is currently pointing to — it’s probably either missing or pointing to an old/wrong IPv6 address. You can verify with: dig AAAA www.csu.nl Then compare that to the actual IPv6 address assigned to your Droplet (or whatever is hosting the site). You can find the Droplet’s IPv6 address in the control panel under the networking section. If IPv6 is enabled on the Droplet but there’s no AAAA record, just add one in your DNS settings pointing to the Droplet’s IPv6 address. If there is one but it’s wrong, update it. Also make sure your web server (Nginx/Apache) is actually listening on the IPv6 address. For Nginx, your listen directive should include something like listen [::]:443 ssl; alongside the regular listen 443 ssl;. If you’re using a load balancer or Cloudflare in front, the AAAA record needs to point to their IPv6 address, not the Droplet’s directly. Regards

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

IPv6 configuration issue

Related questions

Request to unblock outbound SMTP ports 465 and 587

Using custom domain with app platform

Is it possible to point my domain to Digital Ocean app platform using a CNAME record?

Estimated Droplet Transfer Pool

I've submitted ticket over 20 hours ago, but haven't received a response yet.

Enable Outbound Traffic from Droplet through Reserved IP

Report this

IPv6 configuration issue

Related questions

Request to unblock outbound SMTP ports 465 and 587

Using custom domain with app platform

Is it possible to point my domain to Digital Ocean app platform using a CNAME record?

Estimated Droplet Transfer Pool

I've submitted ticket over 20 hours ago, but haven't received a response yet.

Enable Outbound Traffic from Droplet through Reserved IP