Vercel DNS ALIAS records resolving to incorrect non-Vercel IP addresses

Help
1

Problem

The default ALIAS records created by Vercel DNS for balancehospitalityscheveningen.nl are pointing to internal hostnames that resolve to non-Vercel IPs.

Current Behavior

  • Apex domain ALIAS → 8fa12a182d744c5f.vercel-dns-017.com → resolves to 208.91.112.55 (not a Vercel IP)
  • Wildcard ALIAS → cname.vercel-dns-017.com → resolves to 64.29.17.65 (not a Vercel IP)

Evidence

Running nslookup against Vercel nameservers returns the incorrect IP:

nslookup balancehospitalityscheveningen.nl ns1.vercel-dns.com

This returns 208.91.112.55 instead of the expected Vercel IP (76.76.21.21).

Impact

A manually added A record for 76.76.21.21 is being overridden by these broken default ALIAS records, causing the domain to route to incorrect servers.

Root Cause

This appears to be a Vercel infrastructure/DNS bug where the internal vercel-dns-017.com ALIAS targets are resolving to IPs outside Vercel’s network.

Resolution Needed

Vercel engineering needs to fix or remove the broken ALIAS records. The user was unable to submit a support case due to Hobby plan restrictions on DNS Configuration topics, despite this being an infrastructure defect on Vercel’s side.

5

Hi @software368, welcome to the Vercel Community!

The DNS check and nslookup are looking good to me. Can you check again?

nslookup balancehospitalityscheveningen.nl ns1.vercel-dns.com
Server:		ns1.vercel-dns.com
Address:	2620:4d:4000:6259:7:13:0:1#53

Name:	balancehospitalityscheveningen.nl
Address: 76.76.21.21
6

Thanx for the quick response,

DNS is resolving correctly now, but the SSL certificate for balancehospitalityscheveningen.nl is returning SEC_E_UNTRUSTED_ROOT. Can you re-provision the SSL certificate?

1 Like
7

I’m glad DNS is working now. About the cert: it’s loading correctly for me. Can you do a DNS flush on your side and try private browser tab?