Anachoreta Posted May 31, 2021 Posted May 31, 2021 Hi! Had changed/added some records yesterday and today, mx, cname, txt for Yandex Email. They still have not propagated and Dig says: http://heliohost.grd.net.pl/dns-checker/ That the nameservers still respond with the old records or a mishmash. Server Tommy, Account Anchor. Kindest regards, Anachoreta Quote
Anachoreta Posted May 31, 2021 Author Posted May 31, 2021 Anachoreta.pp.ua and anachoreta.eu.org Plus the two surname domains from pp.ua and EU.org Quote
wolstech Posted May 31, 2021 Posted May 31, 2021 I was afraid it was going to be those. The pp.ua and eu.org TLDs are both on the list of domain registrars that are not fully compatible with us. Put simply, these domain do not work right with our name servers because the registrars do not conform to industry standards for DNS configuration. We see issues with these TLDs a lot. If cPanel lets you set the records successfully, our system worked and the issue is on their end for refusing to propagate them. While we don't usually recommend it, the only solution I can think of here is Cloudflare. You could try setting that up using a full zone configuration, let it copy the working records from us, change your name servers to CF's provided ones, then go to CF's site and edit the records you want after it's working. Others have said that these weird providers tolerate CF better than our servers, so it might work well enough to do what you want. Keep in mind though that if you do that, the DNS options in cPanel won't function any longer, and you'll need to manually create DNS records in CF if you do things like add subdomains. Quote
Anachoreta Posted May 31, 2021 Author Posted May 31, 2021 What is interesting, with the third.pp.ua, the same procedure of changing the dns records had worked without any problems a fortnight ago. Well, will wait a bit longer, else I will try it with cloudflare. Quote
Anachoreta Posted May 31, 2021 Author Posted May 31, 2021 Grr, mea culpa, found the problem, had accidentally set a second CNAME entry for the Mail. Subdomain. So not nic.eu.org nor nic.pp.ua are to blame, they only needed the workaround over DNS.he.net for adding in cpanel. Removing the redundant one, et voilá DNS gets propagated again. Quote
wolstech Posted May 31, 2021 Posted May 31, 2021 That’ll do it. The standards do say that you cannot have more than one CNAME for a given domain (though multiple A records would’ve been fine). Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.