DNS verification
How verification works, what “ready” means, and what to check when validation is stuck.
DNS verification
DNS verification proves that you control a domain before Nimriz enables it for live use.
Why verification matters
Verification prevents someone from claiming a hostname they do not own. Until verification succeeds, Nimriz may keep that domain blocked for link creation, redirects, or both.
What to expect
- Add the domain in Nimriz.
- Nimriz shows the DNS record or records you need to publish.
- You add those records in your DNS provider.
- Nimriz checks DNS and marks the domain verified when the expected values are visible.
Propagation is not instant. A correct setup may still take a little time to appear worldwide.
What to check first
- The hostname in DNS exactly matches the hostname shown in Nimriz.
- You published the latest verification value from Nimriz, not an older one.
- The record type matches the instructions exactly.
- Your DNS provider has saved the change and the record is publicly visible.
Common failure modes
Wrong host
This is the most common issue. example.com, www.example.com, and go.example.com are all different hosts.
Propagation delay
If the record is correct but verification still fails, wait a little longer and try again. DNS propagation often resolves the issue without any product change.
Conflicting records
Duplicate or conflicting TXT records can cause validation to fail. Remove stale records from older attempts when they are no longer needed.
DNS provider flattening or proxy behavior
Some DNS providers rewrite, flatten, or proxy records. If you are using advanced DNS features, confirm that the final public DNS response still matches the value Nimriz expects.
If verification is stuck
Use this checklist:
- Copy the hostname from Nimriz and compare it character by character with your DNS record.
- Confirm the record type and value.
- Wait for propagation and re-run verification.
- Check whether you accidentally created the record on a parent or sibling host.
- Remove stale records from older setup attempts if they conflict.
After verification succeeds
Do a quick production check:
- create a test link on that domain
- open the short link in an incognito window
- check that a missing slug goes to the expected fallback page
When to escalate
Contact support if:
- the exact DNS record is visible publicly but Nimriz still cannot verify it
- the domain toggles between ready and not ready
- the host verifies but still cannot be used for redirects
Share:
- the hostname
- the record type and value you published
- the time of the last DNS update
- a screenshot from your DNS provider if possible