Skip to content
/ homerun Public

Dockerized Cloudflare dynamic DNS daemon for x86 / ARMv7 (Raspberry Pi support)

License

Notifications You must be signed in to change notification settings

ocanty/homerun

Repository files navigation

homerun

homerun is a tool which updates an A record on Cloudflare whenever your public IP changes

This is useful when you want to access services hosted on your home pc/homelab whilst having a dynamic IP

Installation

Docker

  1. Clone the repo:

    git clone https://github.com/ocanty/homerun.git
    cd homerun
    
  2. Build the Docker image, note the arguments

    • For x86 based OS's:

      sudo docker build . --build-arg SUBDOMAIN=homerun --build-arg DOMAIN=example.com --build-arg PROXY=false --build-arg UPDATE_EVERY=10 -t my-homerun
      
    • For armv7 based OS's:

      sudo docker build -f Dockerfile.armv7 . --build-arg SUBDOMAIN=homerun --build-arg DOMAIN=example.com --build-arg PROXY=false --build-arg UPDATE_EVERY=10 -t my-homerun
      
  3. Setup Cloudflare API keys

    1. Follow Cloudflare instructions to retrieve your API key.
  4. Run the image first to test, to see if everything is working correctly:

    sudo docker run -t -e "CF_API_EMAIL=<email>" -e "CF_API_KEY=<global API key>" my-homerun
    
  5. If so, set it up to fork to the background:

    sudo docker run -e "CF_API_EMAIL=<email>" -e "CF_API_KEY=<global API key>" my-homerun &
    
  6. (optional) If you do not want to pass Cloudflare keys as environment variables, you can follow Step 5 below, and then rebuild the image as before with .cloudflare.cfg in the project directory.

Manual

  1. Clone the repo:

    git clone https://github.com/ocanty/homerun.git
    
  2. Install dependencies:

    python3 setup.py install
    
  3. Edit config.yml and setup configuration (example below):

    ip_server: https://ifconfig.co/ip
    subdomain: homerun
    domain: example.com
    proxy: false
    update_every: 10
    
  4. Specify config options as you wish

    1. ip_server - A HTTP(S) service that when GET requested, returns the IP of the client (you probably won't need to change this)
    2. subdomain - The subdomain you want to point to your home IP
    3. domain - A Cloudflare site that is associated with your Cloudflare account
    4. proxy - Should we proxy this record through Cloudflare's system? (If this is true note that Cloudflare only supports some ports based on your plan)
    5. update_every - Check every x amount of minute for an IP change
  5. Setup Cloudflare API keys

    1. Follow Cloudflare instructions to retrieve your API key.

    2. Create a file named .cloudflare.cfg in the project directory (the folder with setup.py, requirements.txt...)

    3. The file should look like as follows:

      [CloudFlare]
      email = <your cloudflare email>
      token = <global api key>
      
    4. For more information about this click here.

  6. Setup the systemd service

    1. Edit homerun.service, changing WorkingDirectory to the path you placed the repo:

      [Unit]
      Description=homerun - dynamic DNS daemon for Cloudflare
      
      [Service]
      Type=simple
      WorkingDirectory=/home/ocanty/projects/homerun/
      ExecStart=python3 homerun.py
      ExecStop=pkill -f 'python3 homerun.py'
      
      [Install]
      WantedBy=multi-user.target
      
    2. Tell systemd to use the service:

      sudo ln -s homerun.service /etc/systemd/system/homerun.service
      systemctl enable homerun.service
      systemctl start homerun.service
      
  7. Your record should be up and running at subdomain.domain

FAQs

  1. What if I want it to point to the root? i.e just domain

    You should make use of Cloudflare's CNAME flattening feature to alias this subdomain to the root domain.

  2. What about other subdomains?

    Just use regular CNAMEs.

About

Dockerized Cloudflare dynamic DNS daemon for x86 / ARMv7 (Raspberry Pi support)

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •