IP Dynamic : Dns O Matic update CloudFlare

Comments

18 comments

  • Avatar
    rotblitz

    First read this: https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/

    Now how to proceed: you make the A record for myweb.com a CNAME pointing at dynamic.myweb.com, and then you continue to update dynamic.myweb.com.
    CloudFlare will show an A record for myweb.com with your dynamic IP address which is what you want, thanks to "CNAME Flattening".  So easy!

  • Avatar
    rotblitz

    Ok, then easier:

    1. Delete this:   Type: A            |  Name:  myweb.com    |  Value: points to XXX.XXX.XXX.XXX
    2. Create this:   Type: CNAME  |  Name:  myweb.com    |  Value: is an alias of dynamic.myweb.com

    I don't see this being complicated in any way...

  • Avatar
    caseyj

    Hello,

     I really thank you a lot dear rotblitz. U just show how and that is SIMPLE. But u have to GET it before.

    I am sure that you like having cookies with tea as I do. You know how to cook some cookies ? Me? No... But a "Chef cuisine" can tell you, here the receipt, do it... So easy ! ... :)...

     

  • Avatar
    peternm22 (Edited )

    I have the exact same problem as xjsv24.

    Earlier today my router triggered a DNS-O-Matic update, and then the wrong domain name in my Cloudflare account had it's IP address changed.

    I have two domains using Cloudflare. One that DNS-O-Matic updates and the other which has a hard coded IP address that doesn't change.

    I happen to be using the site that had it's DNS changed by mistake when this occurred, so luckily downtime on this site was minimal. I manually changed the IP address back in Cloudflare, and then disabled DNS-O-Matic to be on the safe side.

    I also posted on the Cloudflare forums about this problem: https://community.cloudflare.com/t/dynamic-dns-problem-with-dns-o-matic-today-anyone-else/72397

    I'm not 100% sure whether Cloudflare or DNS-O-Matic is at fault here, but I am strongly leaning towards DNS-O-Matic based on what the person in the Cloudflare forum has said.

    I've sent a support request to DNS-O-Matic to see what they say.

    I've been using this setup for a few years without issue until today.

  • Avatar
    peternm22

    Heard back from DNS-O-Matic about the problem. Here is what they said:

    "There is a change in March 2019 at our end that could explain the issue you're facing. And currently, our engineer is looking into an issue with DNS-O-Matic and Cloudflare.

    I will be in touch with you when I hear back from them or if we require any additional information."

  • Avatar
    caseyj

    Sorry, I dont get all... Here I have in CL :

    type A   | name dynamic  |  value : point to 100.50.50.10 

    type A   | myweb.com       |  value : point to 100.50.50.11  (not good ip!) 

    CNAME update | value : is an alias of myweb.com 

    Q1 = " you make the A record for myweb.com" = ?? A record accept ONLY ip .. 185.52.32.1xx

    Q2 = "CNAME pointing at dynamic.myweb.com" = ?? Exemple please...

    Sorry it VERY COMPLICATE for me as i am totally noob for it.... 

     

  • Avatar
    caseyj

    Hello, help me please .... :(

  • Avatar
    xjsv24

    I am very late to this party but I have a question regarding your answer caseyj

    Is it not possible to have 2 A records and have only 1 updated?

  • Avatar
    rotblitz

    What would be the purpose of two A records for a hostname but have only one updated?

    At least it is not possible to do this through DNS-O-Matic, because you can specify the hostname only, not a specific A record.

     

  • Avatar
    xjsv24

    Thank you for the clarification on DNS-O-Matic, I guess I have to find another provide that allows me to do that.

    As for the reason why, I have a free domain from Freenom that I am using to get my home routers IP (ip.example.com).
    This is the A record that I want to keep up to date via DDNS.
    The catch is that in order to maintain a free domain from Freenom, it is required that it is public facing.
    I had my domain registration canceled 4 times in the past because it was not accessible.
    To avoid this I have a public facing site on it (A: example.com & CNAME: www.example.com). All of this is on CloudFlare.
    I don't want the A record for example.com to be changed, as it points to my hosting provider. 

  • Avatar
    rotblitz (Edited )

    I’m baffled! If even the CloudFlare API doesn’t support updating a specific A record, how could a 3rd party provider offer it for CloudFlare?

    And your router IP address is public facing.

    Freenom is crap, not an orderly domain registrar. Keep your fingers away from them. You won’t be happy with them.

  • Avatar
    xjsv24

    Thanks for the clarification on CloudFlare, I actually never looked into their API and did not know what it was capable of.

    I know my routers IP is public facing but when I'm away on business I need to VPN into my home network. And because I have a dynamic IP, it might change so I use ip.example.com to get it.

    And yes Freenom is total crap but it's free and I don't use it for anything serious. I've had my free domain registered for about 4-5 years now without issues except the cancellations when it was not public facing.

     

  • Avatar
    rotblitz

    So you are saying that ip.example.com has two A records?  I do not see a need for this, as long as example.com points at an existing and running website.  You should not have troubles with Freenom then.

  • Avatar
    xjsv24

    No not 2 A records.

    Example.com points to the IP of the hosting provider.

    Ip.example.com should point to my home routers IP.

    My setup is as follows:

    Type: A | Name: example.com | Value: points to 111.111.111.111
    Type: A | Name: ip | Value: points to 222.222.222.222
    Type: CNAME | Name: www | Value: is an alias of example.com

    111.111.111.111 - Being the hosting provider
    222.222.222.222 - Being my home router

     

  • Avatar
    rotblitz

    Ah, this makes sense now and renders your orginal question meaningless.

    "Is it not possible to have 2 A records and have only 1 updated?"

    There are not two A records for a hostname, so this is the wrong question.  You can indeed update the (one) A record of ip.example.com with using DNS-O-Matic and leave the (one) A record of example.com unchanged.

    Hostname: ip
    Domain: example.com

    At CloudFlare you must disable handling for ip.example.com, so that it is not being proxied.

  • Avatar
    xjsv24 (Edited )

    The problem that I was having is that DNS-O-Matic was updating the wrong domain. So I had to turn DDNS off. I had this running without issues for about a year now. The correct A record was being updated without issues. Only recently I noticed that it started to update the wrong domain which did not make sense to me so I started playing with the configuration in DNS-O-Matic. This all started around March 16th.

    Instead of the domain configured in the Domain field (as you have explained), it was updating what appeared to be the first domain I configured in CloudFlare.

  • Avatar
    rotblitz

    In case you are still facing troubles, I believe this issue must be investigated by staff.  We other users cannot really help here, because we cannot look into your account.  Open a support ticket, link "Submit a request" above.

  • Avatar
    xjsv24

    Thank you, will do, I just fist wanted to make sure it was not caused by my bad configuration or some other user error.

Please sign in to leave a comment.