Cloudflare returning 1004 error when updating via Dns-O-Matic

Comments

16 comments

  • Avatar
    rotblitz (Edited )

    See https://support.opendns.com/hc/en-us/community/posts/220008227/comments/360004868952
    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.

    -1
    Comment actions Permalink
  • Avatar
    opendns.mbux

    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.

    0
    Comment actions Permalink
  • Avatar
    opendns.mbux

    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.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "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.

    0
    Comment actions Permalink
  • Avatar
    capsiatech

    I've got the same error when trying to setup dns-o-matic for my cloudflare account. Hope it will be solved soon.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Hoping does not help.  You must open a support ticket to get it moved forward.

    0
    Comment actions Permalink
  • Avatar
    capsiatech

    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.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    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.

    0
    Comment actions Permalink
  • Avatar
    capsiatech

    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:

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Can you post also a screenshot of the history at DNS-O-Matic?

    0
    Comment actions Permalink
  • Avatar
    capsiatech

    This is the cloudflare history:

    All the others don't have errors

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    Very difficult. This must be investigated by staff.

    0
    Comment actions Permalink
  • Avatar
    mbux

    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.

     

    1
    Comment actions Permalink
  • Avatar
    swrobel

    Just got this response from DNS-O-Matic support after months of asking for an update/ETA:

    "Unfortunately, we aren't able to provide an ETA at this stage and I would recommend moving to a different provider if this is something that is required."

    0
    Comment actions Permalink
  • Avatar
    mbux

    got pretty much the same response a few days ago: no ETA

    0
    Comment actions Permalink

Please sign in to leave a comment.