Docs

Troubleshooting DNS

Common DNS problems and how to resolve them after pointing a domain at Velumi.

My domain still isn't working after I changed the nameservers

DNS changes take time to spread across the internet. This is normal and usually resolves within a few hours, but can take up to 48 hours. The delay is controlled by your registrar and global DNS — not by Velumi.

While you wait:

  • Double-check you entered both nameservers exactly as Velumi gave them, with no typos and no trailing dots.
  • Make sure you replaced the existing nameservers rather than adding the Velumi ones alongside them. Mixed nameservers cause unpredictable behavior.
  • Confirm you changed nameservers at the registrar (where you bought the domain), not at an old DNS host.

You can check what nameservers the world currently sees with a public tool like whatsmydns.net — search your domain for NS records.

My email stopped working after adding the domain

When you add a domain, Velumi scans and imports your existing DNS — including email (MX) records — so email usually keeps working through the switch. If it stopped, the scan most likely couldn't see one of your records.

Open DNS records and check your MX records are present and correct. If any are missing, add them — your email provider's documentation lists the exact values (including any TXT records for SPF/DKIM).

A subdomain that worked before is now broken

Same cause: the scan imports most records, but a few record types can't be discovered automatically. Add the missing record under DNS records.

My site shows a certificate warning

SSL certificates are issued automatically once DNS resolves to Velumi. If you see a certificate warning immediately after attaching a domain, it usually clears on its own within a short time as the certificate is provisioned. If it persists for more than a few hours after DNS has propagated, contact support.

I changed a record but the old value is still showing

DNS resolvers cache records for the duration of their TTL. If you lowered a record's value but an old one is still served, wait for the previous TTL to expire. For changes you know are coming, lower the TTL ahead of time so the switch takes effect faster.

Still stuck?

Reach out to support with your domain name and what you're seeing. Include the output of a public DNS lookup if you can — it helps us see what the rest of the internet sees.