DNS provider - Vercel does not match app's IP. (Custom domain)

Phoenix
,
1

I got in troubles with using custom domain.

I’m having a domain in vercel and added A and AAAA records from flyctl ips list -a myapp

image
image2478×1104 172 KB

$ flyctl certs show -a myapp myapp.com
The certificate for dasisu.com has not been issued yet.

Hostname                  = myapp.com
DNS Provider              = vercel-dns
Certificate Authority     = Let's Encrypt
Issued                    = 
Added to App              = 18 minutes ago
Source                    = fly
A Record (76.76.21.123) does not match app's IP (66.241.125.90)
Address resolution (76.76.21.123) does not match app's IP (66.241.125.90/2a09:8280:1::42:b8bf)
Address resolution (76.76.21.164) does not match app's IP (66.241.125.90/2a09:8280:1::42:b8bf)
You are creating a certificate for dasisu.com
We are using lets_encrypt for this certificate.

You can direct traffic to dasisu.com by:

1: Adding an A record to your DNS service which reads

    A @ 66.241.125.90

You can validate your ownership of dasisu.com by:

2: Adding an AAAA record to your DNS service which reads:

    AAAA @ 2a09:8280:1::42:b8bf

Obviously, I followed all the steps right with How to do Custom Domains with Fly · The Fly Blog

FYI)
flyctl certs list

Host Name                 Added                Status
myapp.com                29 minutes ago       Awaiting configuration

image
image2504×696 152 KB

Is there anyone having same issues?

2

looks like you did an incomplete job of redacting your domain (it shows up in the terminal output). but we can snoop on DNS using dig

$ dig some-domain-goes-here.com @1.1.1.1 # 1.1.1.1 is cloudflare's dns, 8.8.8.8 is google's, i like checking both when dealing with dns

when i do that i see the A record you expect “A 66.241.125.90”. for the www subdomain (www.your-domain.com), though, the record doesn’t look quite correct: 60 IN SOA ns1.vercel-dns.com. hostmaster.nsone.net. 1702038503 43200 7200 1209600 60

DNS can take a white to propagate, especially if the TTL was high, are you still seeing issues with this?

1 Like