Thanks for sharing! I ran a few dig tests on damianroiz.com, and found:
- All DNS lookups for the domain are failing with
SERVFAIL.
- When I query Google’s public DNS (8.8.8.8), the authoritative name servers respond with
REFUSED, meaning they are actively rejecting external queries.
- Even NS lookups (
dig NS damianroiz.com) return no results, which means your domain the DNS is not responding to the internet which is why Vercel can’t verify or route traffic to your deployment.
This is likely caused by the domain’s name servers at the registrar are not set correctly.
Could you check the name servers? Maybe share a screenshot of your records?
I also ran a direct A record lookup:
This still returns SERVFAIL, with no A record or authority section at all. This confirms that it’s not just an A record missing... the domain’s DNS itself is failing to resolve.
So the root issue seems to remains the same: the authoritative DNS servers for your domain are not answering public queries. You’ll need to fix that at the registrar or DNS provider (Bluehost) before Vercel can verify the domain.