Bug: domain resolution results in another IP #270

New Issue

saavagebueno · 2025-11-20T04:22:11-05:00

saavagebueno commented

2025-11-20 04:22:11 -05:00

Originally created by @Master-Robot on GitHub (Apr 17, 2023).

Originally assigned to: @qdm12 on GitHub.

TLDR: public IP read wrong, constantly updating CF

Is this urgent: No
DNS provider(s) you use: Cloudflare
Program version:

Running version latest built on 2023-04-13T17:47:03Z (commit 519b9c4)
What are you using to run the container: docker-compose
Extra information (optional)
DDNS updates CF with the correct IP (244.244.244.244) but for some reason, when it tries to find my IP, it reads the IP 2.2.2.2
Logs: this example on a loop

2023-04-17T09:23:49Z INFO IPv4 address of exemple.fr is 2.2.2.2 and your IPv4 address is 244.244.244.244
2023-04-17T09:23:49Z INFO Updating record [domain: exemple.fr | host: @ | provider: cloudflare | ip: ipv4] to use 244.244.244.244

Configuration file (remove your credentials!):

copy-paste from provided json

Host OS:
debian 11

Originally created by @Master-Robot on GitHub (Apr 17, 2023). Originally assigned to: @qdm12 on GitHub. **TLDR**: *public IP read wrong, constantly updating CF* 1. Is this urgent: No 2. DNS provider(s) you use: Cloudflare 3. Program version: `Running version latest built on 2023-04-13T17:47:03Z (commit 519b9c4)` 4. What are you using to run the container: docker-compose 5. Extra information (optional) DDNS updates CF with the correct IP (244.244.244.244) but for some reason, when it tries to find my IP, it reads the IP 2.2.2.2 Logs: this example on a loop ``` 2023-04-17T09:23:49Z INFO IPv4 address of exemple.fr is 2.2.2.2 and your IPv4 address is 244.244.244.244 2023-04-17T09:23:49Z INFO Updating record [domain: exemple.fr | host: @ | provider: cloudflare | ip: ipv4] to use 244.244.244.244 ``` Configuration file (**remove your credentials!**): ``` copy-paste from provided json ``` Host OS: debian 11

saavagebueno closed this issue

2025-11-20 04:22:11 -05:00

saavagebueno commented

2025-11-20 04:22:12 -05:00

@qdm12 commented on GitHub (Apr 17, 2023):

What does docker run -it --rm alpine:3.17 nslookup exemple.fr give you? 2.2.2.2 or 244.244.244.244??

@qdm12 commented on GitHub (Apr 17, 2023): What does `docker run -it --rm alpine:3.17 nslookup exemple.fr` give you? `2.2.2.2` or `244.244.244.244`??

saavagebueno commented

2025-11-20 04:22:12 -05:00

@Master-Robot commented on GitHub (Apr 17, 2023):

I get 244.244.244.244 but CF has 2.2.2.2 and all of my services resolve correctly...

@Master-Robot commented on GitHub (Apr 17, 2023): I get 244.244.244.244 but CF has 2.2.2.2 and all of my services resolve correctly...

saavagebueno commented

2025-11-20 04:22:12 -05:00

@Master-Robot commented on GitHub (Apr 17, 2023):

would it be because my CNAME is proxied to my A record?

@Master-Robot commented on GitHub (Apr 17, 2023): would it be because my CNAME is proxied to my A record?

saavagebueno commented

2025-11-20 04:22:13 -05:00

@Master-Robot commented on GitHub (Apr 17, 2023):

Just realised that my A record is proxied through CF, so resolving the IP will stop at CF servers. CF then forwards connections through to my server after that so my IP is not exposed...

@Master-Robot commented on GitHub (Apr 17, 2023): Just realised that my A record is proxied through CF, so resolving the IP will stop at CF servers. CF then forwards connections through to my server after that so my IP is not exposed...

saavagebueno commented

2025-11-20 04:22:13 -05:00

@qdm12 commented on GitHub (Jun 12, 2023):

You can use the "proxied": true option for Cloudflare 😉

@qdm12 commented on GitHub (Jun 12, 2023): You can use the `"proxied": true` option for Cloudflare 😉

saavagebueno referenced this issue

2025-11-20 04:25:39 -05:00

[PR #270] [CLOSED] Fix DDNSS provider specific IPv6 update flow #669

Sign in to join this conversation.