Why is my DNS record still not working?

You've just created a DNS record from your cPanel (an A, CNAME, MX, TXT record...) but nothing happens. The site doesn't load, the email doesn't send, the subdomain still can't be found. Before you worry, there are two simple things to check: are your DNS servers actually pointing to us? and have you given propagation enough time to do its job?

1. First, check that your DNS is with Hodi

This is the basic requirement. If you modify your DNS zone from cPanel, your domain name still needs to actually use our DNS servers. Otherwise, it's a bit like changing the address on your mailbox while the mail carrier keeps delivering to your old neighbor.

How to check:

1. Log in to your Hodi client account
2. Go to "My account" then "My domains"
3. Click the three dots at the end of your domain's line, then "Manage Nameservers"
4. Look at what's shown. If your domain was purchased at the same time as your hosting, the "Use default nameservers" option should be selected - that's a sign your domain is indeed using our servers. If your domain came from elsewhere and custom servers are listed, check that they're actually ours (for example ns1.hodi.host, ns2.hodi.host, ns3.hodi.host)

If it's neither of these, it's normal for your change made from cPanel to have no effect. Your domain is still querying the DNS of another provider (your previous registrar, Cloudflare, etc.), which knows nothing at all about the record you just created with us.

If your DNS servers aren't ours and you'd still like to manage your DNS zone from cPanel, you'll need to point them to our servers. You'll find the steps to follow in our article How do I change a domain name's DNS servers?.

2. Understanding DNS propagation

If your DNS is indeed with us and the record was created correctly, there's one last factor to take into account: propagation.

The internet isn't a single, centralized directory. It's a huge network of DNS servers spread all over the world, each keeping in memory (this is called a "cache") the information it has retrieved, so it doesn't have to ask for it again every time. This is what makes the internet fast.

The problem is that when you modify a record, all these servers around the world don't update instantly. Each one refreshes its memory at its own pace, based on a lifespan called TTL (Time To Live), set on each record. Until that time has elapsed, some parts of the world will see the new information while others will keep showing the old one - a bit like newspapers printed the day before that keep circulating before being replaced by the new edition.

This is what's known as DNS propagation, and depending on the case, it can take anywhere from a few minutes to 24-48 hours in the slowest cases.

3. Checking the progress of propagation

Good news, you don't have to sit around waiting and reloading your site every five minutes. There are free tools that query DNS servers from all over the globe to show you, in real time, how far your record's propagation has come.

The best known is whatsmydns.net; here's how to use it:

1. Go to the site
2. Enter your domain name (or subdomain)
3. Choose the relevant record type (A, CNAME, MX, TXT...)
4. Click "Search"

You'll then see a world map appear with green checkmarks (the server already sees the correct value) or red crosses (the server is still showing the old value, or nothing at all). As long as not every point is green, it simply means propagation is still ongoing somewhere in the world - nothing abnormal about that.
A technical tip if you're comfortable with it: also clear the DNS cache on your own computer or browser, since it's sometimes the real culprit behind a record that seems "not to be working" when it's actually already well propagated everywhere else.

Still nothing after 48 hours?

If despite all this your DNS record still isn't working after this time, there may be an error in the configuration itself (wrong value, wrong record type, typo). Don't hesitate to contact us via chat or by email at technique@hodi.host, letting us know the domain and record involved. We'll check your DNS zone with you to identify the problem.

Updated on: 17/07/2026