FWG: Cloudflare DDNS configured, missed something..
Have pihole running and pointed to cloudflare under DNS but no traffic seen under cloudflare page analytics.
on FWG, nslookup resolves my domain to my WAN IP
Went through configuration as follows:
Registered new domain on cloudflare and configured to A record for both www, and ****.com pointed to my WAN IP.
configured docker container .yaml file with the below:
(this docker network is different than my pihole docker network)
version: '2'
services:
cloudflare-ddns:
image: oznu/cloudflare-ddns:latest
restart: always
container_name: cloudflareddns
environment:
- API_KEY=****
- ZONE=****.com
- PROXIED=false
networks:
default:
driver: bridge
ipam:
config:
# your chosen docker network here
- subnet: 172.15.0.0/30
Started:
cd /home/pi/.firewalla/run/docker/cloudflareddns
sudo systemctl start docker
sudo docker-compose pull
sudo docker-compose up --no-start
sudo ip route add 172.15.0.0/30 dev br-$(sudo docker network inspect cloudflareddns_default |jq -r '.[0].Id[0:12]') table wan_routable
sudo docker-compose up --detach
Persistance .sh:
sudo systemctl start docker
sudo systemctl start docker-compose@cloudflareddns
sudo ipset create -! docker_wan_routable_net_set hash:net
sudo ipset add -! docker_wan_routable_net_set 172.15.0.0/30
-
As soon as i put in my DNS entries in compose, my ip was updated on cloudflare to reflect my actual WAN ip.
version: '2'
services:
cloudflare-ddns:
image: oznu/cloudflare-ddns:latest
restart: always
container_name: cloudflareddns
environment:
- API_KEY=****
- ZONE=****
- PROXIED=true
dns:
- 172.16.0.2 (pihole)
- 127.0.0.1
networks:
default:
driver: bridge
ipam:
config:
# your chosen docker network here
- subnet: 172.15.0.0/24
Please sign in to leave a comment.
Comments
3 comments