Cloudflare returning 1004 error when updating via Dns-O-Matic
Hi had been using DNS-O-Matic to update my dynamic IP on my Cloudflare DNS record for over a year. I have been using the DDNS facility on my Synology NAS to call DNS-O-Matic to update my IP for a few months, then DNS-O-Matic (used to) make the update on CloudFlare.
Suddenly on 12th March 2019 I started getting from DNS-O-Matic notifications of CloudFlare response "err DNS Validation Error (1004)" every time it attempted to update CloudFlare.
No single attempt to update CloudFlare via DNS-O-Matic has been successful since.
I had made no change on either CloudFlare or DNS-O-Matic set up before this started happening.
From my research it would seem that a CloudFlare validation error means the call made to Cloudflare API (by DNS-O-Matic in this case) is somewhat not in the expected format.
I contacted DNS-O-Matic support a couple of times over a couple of weeks, but I've had no response so far.
Has anyone come across a similar communication breakdown between DNS-O-Matic and CloudFlare? has anyone found a solution?
This could be related. No matter what, your best bet is to raise a support ticket. We other users are hardly in the position to help.
I've read the other post. It doesn't seem to apply to my case, since I only have 1 A record to update on CloudFlare and it used to work fine.
Still no answer from DNS-O-Matic... wondering if they ever respond to anyone who opens a ticket or there's just a problem sending replies to me.
See this: https://community.cloudflare.com/t/community-tip-fixing-code-1004-dns-validation-error/46697
That's even more puzzling because I get error 1004 DNS Validation Error, which does not seem to match with the codes and descriptions on that post: they say "DNS Validation Error: invalid or missing name (Code: 9000)" or “Error 1004: Host Not Configured to Serve Web Traffic” or “Error 1004: DNS is still propagating”. Anyway it seems that post is about "while working on the Cloudflare dashboard", not using the API to update a record, as DNS-O-Matic should be doing.
Also, it says " Look for additional details in the error message you are presented", which only DNS-O-Matic seems to be able to see.
I've googled for a number of posts about Cloudflare error 1004 and no one seemed to relate to my situation.
I've also gone through Cloudflare API documentation and attempted to replicate a record update via API using Postman, and I actually succeded without any error.
So I tend to think there is an issue with DNS-O-Matic, but obviously I don't have an idea of how they use Cloudflare API and cannot replicate it.
Using DNS-O-Matic used to be quite convenient, but since their support are not responding and noone seems to be experiencing the same issue... I'm considering giving up on DNS-O-Matic and/or Cloudflare and looking for alternative methods to update my dynamic IP on my domain.
"Also, it says " Look for additional details in the error message you are presented", which only DNS-O-Matic seems to be able to see."
And you while visiting your DNS-O-Matic control panel to click on the notepad icon beside the CloudFlare service.
I understand you have created a support ticket. Well done! Staff will care about, no matter if this a DNS-O-Matic problem or a problem on your end. It can take up to three business days, sometimes more, depending on the number of tickets they got.
Yes, sorry I didn't said that, I've already opened a support ticket but nobody answered yet.
I've also tried to copy-paste the ip from dns-o-matic to cloudflare, but cloudflare answers with error 1004:
This DNS record cannot be proxied - click the cloud icon to turn it grey to proceed (Code: 9041)
After that I've tried to greycloud the record and I've got this error:
Content for A record is invalid. Must be a valid IPv4 address (Code: 9005)
It seems like the ip isn't valid, but when I type it in works.
Why do you post this here? Doesn't this belong into the CloudFlare forum or to CloudFlare support?
Also, I got the impression that you do not know what you want to do. Are you using CloudFlare as a CDN with DNS for a website of yours or just as authoritative DNS service for your domain? Also, how can we know if the IP address is valid if you don't post it here? If you want further help from us other users here, you must post all relevant information like the domain names and IP addresses in question. Else no help can be given.
1) It seemed the same error that DNS-o-matic reported when attempting to update dns in Cloudflare, both were 1004.
2) Actually I don't know the difference between CDN with DNS and authoritative DNS, I've pointed my nameservers to Cloudflare from my registrar (Freenom) and I've tried to use DNS-o-matic to update the dns.
3) This is a screenshot of all my configurations:
For DNS-o-matic:And for Cloudflare:
I'm the OP. I've had a problem with my account, had to change it and then I was getting an error when trying to log in with the new one.... sorted a few minutes ago, that's why I couldn't reply before.
I am getting the same errors as capsiatech.
I received a response from DNS-O-Matic support on 8th April and after some chasing on my behalf:
Hi, there is a change on 13-March 2019 at our end that could explain Cloudflare dynamic IP stop updating via dnsomatic. I have reported the issue to the engineering team to review it. That said, please set the expectation this will take some time before we will get some response. If it is affecting your service, please consider other workarounds for the time being.
Apologize for the inconvenience caused.
The issue is still ongoing as of now. So apparently making DNS-O-Matic work with Cloudflare is not high in their priorities list and maybe, being this a free service, they put very very limited resources in maintenance and error fixing.
Other users opening tickets might help... but not sure to what extent.
I followed their advice and found a workaround... basically it's a hack on my Synology NAS that adds the ability to update Clouldflare DNS directly, by customising a shell script and running it on the NAS. It really is a workaround: it requires monitoring and maintenance because OS updates from Synology may mess up with/overwrite this script and then I need to realise it's not updating the DNS any longer (it happened once) and re-install the script.
But unfortunately there are no other options... DNS-O-Matic is currently useless for me.
When you add it to Synology use the following format.
Service Provider: DNS-O-Matic
Hostname: myip (or whatever host record you are using, NOT the FQDN)
Username: Your username for DNS-O-Matic (typically an email address)
Password: Password for DNS-O Matic
Now click OK
My DNS-O-Matic record is as follows...
Email: My Cloudflare email
API Token: Is the Account ID on the cloudflare overview page.
I had completely given up, and I started using a different solution to update my Cloudflare DNS record from my Synlogy device (pretty much based on this: https://github.com/mrikirill/SynologyDDNSCloudflareMultidomain).
But then found out recently that DNS-O-Matic started working again. For some reason I just reactivated the set up that used to work years ago and now it was working again.
Meanwhile I had received no update from DNS-O-Matic support. I had almost forgotten about the support request I had opened, as well as this thread that I opened.
I actually kept my new solution for updating, since it seemed more straightforward (less "moving parts" without DNS-O-Matic in the middle).
Also, it now appears that the new major release DSM 7.0 of Synology's OS dropped support for DNS-O-Matic (https://www.synology.com/en-global/releaseNote/DSM#7_0). Although I have not yet upgraded, I will obviously keep using the new solution.
So bye bye DNS-O-Matic.
Please sign in to leave a comment.