Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider

Post by MrBuddyCasino » Thu, Sep 05, 2019, 2:47 PM UTC

alias_neo wrote: post #7

I wrote a little Go tool a few years back that can use your Digital Ocean account as a Dynamic DNS provider. It has been running on my EdgeRouter ever since with a cron job. https://github.com/2bytes/dodns

Post by turdnagel » Thu, Sep 05, 2019, 2:53 PM UTC

Post by heavenlyblue » Thu, Sep 05, 2019, 3:32 PM UTC

kissgyorgy wrote: post #8

This is not very efficient: - It updates the records every 30 seconds even if it doesn't have to. - It has to be run as a daemon, eating memory and CPU time constantly. - only checks one IP service (ipify) I have a more advanced version, which: - you can run as a cron job - only updates the records if the IP address actually changed. - checks multiple IP services (so in case multiple of them going down, it will still…

Post by nikisweeting » Thu, Sep 05, 2019, 3:56 PM UTC

    Helper script to update a DNS record on multiple providers.

    [domain]               The DNS domain you want to get or set (required)

    --domain=example.com   Same as passing [domain] directly as an argument
    -t=|--type=A           The DNS record type, e.g. A, CNAME, etc. (A default)

    -g|--get               Get the record value (the default)
    -s=|--set=value        Set the record value, e.g. 123.235.324.234 or the
                             special value 'pubip' to use current public ip


    -l=|--ttl=n            Set the record TTL to n seconds (overrides api default)
    -p=|--proxied          Set the record to be proxied through CDN (Cloudflare only)
    -a=|--api=cf,do        List of DNS providers to use, e.g. all (default) or cf,do
    -r=|--refresh=n        Run continusouly every n seconds in a loop
    -w=|--timeout=n        Wait n seconds before aborting and retrying
    
    -c=|--config=file      Path to a dotenv-formatted config file to load
    -e=|--config-prefix=X  Load config vars with prefix X e.g. X_VERBOSE=1

    ...

Post by miyuru » Thu, Sep 05, 2019, 4:02 PM UTC

judge2020 wrote: post #9

kissgyorgy wrote: post #8

This is not very efficient: - It updates the records every 30 seconds even if it doesn't have to. - It has to be run as a daemon, eating memory and CPU time constantly. - only checks one IP service (ipify) I have a more advanced version, which: - you can run as a cron job - only updates the records if the IP address actually changed. - checks multiple IP services (so in case multiple of them going down, it will still…

It would also probably be good to use Cloudflare's own ip lookup service, available on every CF website's "/cdn-cgi/trace" page. The only thing is that you need to find a ipv4-only CF website to get the v4 instead of v6.