Github Pages 搭配 Route 53 报错：提示存在AAAA记录但未配置

Hey there, let's figure out why GitHub Pages is flagging an IPv6 (AAAA) record for your custom domain servicelead.com when you swear you didn't set one. DNS can be tricky with caching and hidden defaults, so let's walk through the most likely fixes:

1. Query Your DNS Records Directly (Don't Trust the Dashboard) #

Your domain provider's control panel might not show the full picture. Grab your terminal and run these commands to see exactly what DNS records are being served to GitHub's servers:

• Check for AAAA records specifically: dig AAAA servicelead.com +short
• See all active records: dig servicelead.com ANY +short

If an AAAA record pops up here that you don't recognize, that's the culprit. Sometimes registrars add default IPv6 records without telling you.

2. Flush DNS Caches (Local and Global) #

DNS caching can make you think changes have taken effect when they haven't, or show old records that no longer exist:

• Local machine:
  • Windows: ipconfig /flushdns
  • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Linux: sudo systemd-resolve --flush-caches
• Global propagation: Wait at least a few hours (check your domain's TTL setting—this tells you how long records take to update across the internet). GitHub's resolvers might also have cached old data, so patience helps here.

3. Check for Registrar-Added Default Records #

Many domain providers automatically enable IPv6 support for root domains by default. Log back into your registrar's DNS settings and look for any AAAA entries you didn't create. Look for toggles like "Default IPv6 Record" or "Automatic DNS" that might be turned on, and disable them if you don't need IPv6.

4. Rule Out Hidden Services Adding AAAA Records #

If you're using a CDN, redirect service, or CNAME flattening tool with your domain, these services might be adding AAAA records behind the scenes. For example, some CDNs enable IPv6 by default unless you explicitly turn it off. Check the settings of any third-party tools connected to your domain to see if they're injecting IPv6 records.

5. Double-Check Your GitHub Pages Configuration #

Head to your repo's Pages settings and confirm:

• You've entered the correct domain (no typos!)
• The "Enforce HTTPS" toggle is set correctly (misconfigured HTTPS can sometimes trigger misleading DNS errors)

If none of these steps turn up an AAAA record, reach out to your domain registrar's support team—they might have access to internal configuration that isn't visible in your dashboard.

内容的提问来源于stack exchange，提问作者RobC83