Old DNS cache
I've adquired a "new" domain from Hostinger, but the MX records are being propagated from Cloudflare. I think this error is related with an old cache, but I don't have any way to solve it.
Anyone knows how can I ask to remove a DNS cache from Cloudflare?
Thank you in advance.
16 Replies
What domain?
And what exactly makes you think that the error (with the propagation) originate from Cloudflare?
Hi @DarkDeviL
The domain is "clubdeleonespuentealto.cl":
clubdeleonespuentealto.clServer: dns.google Address: 8.8.8.8 clubdeleonespuentealto.cl MX preference = 6, mail exchanger = route3.mx.cloudflare.net clubdeleonespuentealto.cl MX preference = 50, mail exchanger = route1.mx.cloudflare.net clubdeleonespuentealto.cl MX preference = 96, mail exchanger = route2.mx.cloudflare.net Respuesta no autoritativa: clubdeleonespuentealto.cl MX preference = 5, mail exchanger = mx1.hostinger.com clubdeleonespuentealto.cl MX preference = 10, mail exchanger = mx2.hostinger.com clubdeleonespuentealto.cl MX preference = 6, mail exchanger = route3.mx.cloudflare.net clubdeleonespuentealto.cl MX preference = 50, mail exchanger = route1.mx.cloudflare.net clubdeleonespuentealto.cl MX preference = 96, mail exchanger = route2.mx.cloudflare.net Respuesta no autoritativa: clubdeleonespuentealto.cl MX preference = 5, mail exchanger = mx1.hostinger.com clubdeleonespuentealto.cl MX preference = 10, mail exchanger = mx2.hostinger.com I see that MX records are being propagated from Cloudflare and Hostinger. Hi @Leo
clubdeleonespuentealto.cl has four DNS servers in the parent registry.
DNS resolvers such as e.g. Google (as you're apparently using 8.8.8.8), will be taking one random one of them to ask, and asking it what it knows about the given (sub-)domain.
You will therefore need to coordinate the name severs properly, through (or together with) your domain registrar, in order to ensure that only the ones you wish to use, actually exist for your domain name.@DarkDeviL that is right, but this domain is not "hosted" by Cloudflare. In addition, the domainf was free for may months and I adquired it by Hostinger.
Then you need to get the name servers for Cloudflare removed.
That's done through your domain registrar.
I don't have any service with Cloudflare, so I don't undertand how I can ask for remove these records.
I only have access to DNS records in Hostinger
The errornous propagation you spoke about is there, but it is not from Cloudflare's side.
The error comes from the domain owner's (and their registrar), and their misconfiguration.
so, this problem is generated from Hostinger side?
(I am the owner od this record)
I bought it a week ago
If you have paid Hostinger for the domain, and you do not see the name servers through their control panel, then you would need to contact Hostinger Support for further assistance.
If Hostinger (e.g. your domain registrar) cannot fix it themself, they can at least, as your registrar, escalate it to the domain registry.
The domain registry, e.g. the parent servers for
cl is exposing all the above name servers.I see the correct records in hostinger configuration
I got it
then, I will ask for Hostinger to escalate this misconfiguration
Thank you a lot
Interestingly, it seems like Domain WHOIS is only showing the two
ns1.dns-parking.com and ns2.dns-parking.com.
However, the DNS hierarchy is also giving the Cloudflare ones.
^ Giving this result, when it randomly "round-robin" between through the 4 name servers in the delegation.is this common problem?
I guess that depends on the definition of common, or how far that reaches.
There are quite a few people from time to time, when on-boarding their domain to Cloudflare, that are (incorrectly) adding Cloudflare name servers, but not removing the old ones.
(It won't pass Cloudflare's validation though, before the old ones are removed though).
That said, -
ðŸ«
A mess up like this, and then not actually being caused by the domain owner (e..g you), as you say, doesn't seem as common as the above though.
But the mismatch between Domain WHOIS and the DNS hierarchy have been seen before.
Thank you @DarkDeviL
Right now I am asking for support to Hostinger... I noticed that the problem is not common for them
so, your explanation was very useful