Public services over IPv6: DNS, web, mail and load balancers
Publish dual-stack DNS, web and mail services. Meet mail-delivery expectations for IPv6 including reverse DNS and authentication (RFC 5321, RFC 8501). Preserve the client's IPv6 address through proxies and load balancers.
Take the quiz · pass mark 70% · 9 questions
Explanation
Publishing a service over IPv6 is more than adding an address: DNS, certificates, mail reputation and load-balancer behaviour all have IPv6-specific requirements.
DNS: AAAA and PTR
A service is reachable over IPv6 only when it has a AAAA record (DNS type 28, RFC 3596) alongside its A record, served by dual-stack authoritative name servers (the name servers themselves should have AAAA and answer over IPv6). Equally important is reverse DNS: a PTR in ip6.arpa mapping the address back to the name. RFC 8501 covers how to manage IPv6 reverse DNS, including for the large, sparse space a server network occupies. Publish AAAA, confirm the authoritative servers answer over IPv6, and set PTRs for anything that initiates connections (especially mail).
Web
A dual-stack web server listens on IPv6 as well as IPv4, presents a certificate valid for the name (the cert is name-based, so it already covers the IPv6 endpoint), and is fronted by IPv6-capable CDNs/proxies. Test from an IPv6-only client, not just dual stack, so Happy Eyeballs (L6.08) does not hide a broken AAAA.
Mail: the strict case (RFC 5321)
Mail is the least forgiving service over IPv6. SMTP (RFC 5321, server port 25) delivery between organisations now expects, for IPv6 senders:
- A PTR (reverse DNS) for the sending IPv6 address that resolves, and ideally matches forward DNS (FCrDNS). Many receivers reject IPv6 mail with no PTR outright.
- Valid authentication records (SPF listing the IPv6 senders, plus DKIM/DMARC) covering the IPv6 path.
So turning on IPv6 for outbound mail without first setting PTR and SPF for the IPv6 addresses will worsen deliverability. Set reverse DNS and authentication first, then enable IPv6 sending.
Load balancers and proxies: preserve the client address
Behind a proxy or load balancer, the backend otherwise sees the proxy's address, not the client's — breaking logging, geo, rate-limiting and abuse handling, and discarding the very IPv6 address you wanted to see. Preserve it: use the PROXY protocol (L4) or X-Forwarded-For/Forwarded headers (L7), store the address canonically (L6.07), and make sure the LB health-checks and forwards over IPv6. Do not let an IPv4-only LB collapse all IPv6 clients into one logged address.
ictNetworks scenario
ictNetworks publishes its site and mail domain dual-stack: AAAA records on dual-stack authoritative servers, PTRs in ip6.arpa per RFC 8501 for every host that initiates connections, and for mail (RFC 5321) a matching IPv6 PTR plus SPF/DKIM/DMARC covering the IPv6 senders before enabling IPv6 delivery. Its HAProxy front end forwards over IPv6 and preserves the client IPv6 address with the PROXY protocol and Forwarded, and everything is tested from an IPv6-only client.
Drawing diagram…
Worked examples
Example 1: The record that enables IPv6
A service becomes IPv6-reachable when it has a AAAA record, DNS resource-record type 28 (RFC 3596), served by name servers that themselves answer over IPv6.
Example 2: Reverse-DNS granularity
A single host's full reverse name in ip6.arpa uses all 32 hex nibbles of the 128-bit address (one label per nibble). Servers that initiate connections — especially mail — need a working PTR at that name (RFC 8501).
Example 3: The mail port and its gate
Inter-organisation SMTP delivery uses port 25 (RFC 5321); for IPv6 senders many receivers require a resolving PTR (and matching forward DNS) or they reject the mail, so reverse DNS and SPF must precede enabling IPv6 outbound mail.
Lab
Goal: Publish a dual-stack site and mail domain and verify them from IPv6-only and IPv4-only clients.
You need: containers for authoritative DNS (BIND/Knot/PowerDNS), a web server (nginx), a mail server (Postfix) and a load balancer (HAProxy); an IPv6-only and an IPv4-only test client. (All of these vary by version — check the docs.)
- Serve AAAA (and A) for the site and mail host from dual-stack authoritative DNS; confirm the name servers answer over IPv6.
- Set PTR records in
ip6.arpa(RFC 8501) for the web and mail hosts; verify FCrDNS for the mail host. - Put HAProxy in front of nginx, forwarding over IPv6 and preserving the client IPv6 address (PROXY protocol /
Forwarded); confirm the backend logs the real client address canonically. - Configure Postfix to send/receive over IPv6 with SPF/DKIM/DMARC covering the IPv6 path; show a message delivered over IPv6 with the PTR check passing.
- Verify the site and mail from both the IPv6-only and IPv4-only clients (not just dual stack).
What to submit: the DNS (AAAA/PTR), HAProxy, nginx and Postfix configuration, evidence of client-address preservation, the IPv6 mail delivery with PTR/SPF, and the IPv6-only/IPv4-only client results.
Summary
- Publish AAAA (type 28, RFC 3596) on dual-stack authoritative DNS, and set PTRs in ip6.arpa (RFC 8501).
- Mail (RFC 5321, port 25) is strict: set an IPv6 PTR (matching forward DNS) and SPF/DKIM/DMARC before enabling IPv6 sending, or deliverability drops.
- Load balancers/proxies must forward over IPv6 and preserve the client IPv6 address (PROXY protocol / Forwarded), logging it canonically.
- Always verify from an IPv6-only client so fallback does not hide a fault.
- Next lesson (L7.08): operating IPv6 — monitoring, measurement and SLAs.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.