Option to force DNS resolution using external DNS provider #195

New Issue

saavagebueno · 2025-11-20T04:21:23-05:00

saavagebueno commented

2025-11-20 04:21:23 -05:00

Originally created by @g3rmanaviator on GitHub (Jun 9, 2022).

Originally assigned to: @qdm12 on GitHub.

What's the feature?
Toggle to select between native OS DNS resolution (i.e. DNS server configured by the operating system) or
external provider or external IPs.
Extra information?
When using split DNS a host or domain will typically resolve to a private RFC1918 address because the internal DNS server resolves
to the private IP of 10.x.x.x or 192.168.x.x instead of the public NAT IP.
To overcome this it would be ideal to be able to tell the updater which DNS server to use to verify what the host or domain
currently resolves to. For example:

-Resolve current IP using host DNS
-Resolve current IP using (Google (8.8.8.8), Cloudflare (1.1.1.1), or Quad9 (9.9.9.9))

Originally created by @g3rmanaviator on GitHub (Jun 9, 2022). Originally assigned to: @qdm12 on GitHub. 1. What's the feature? Toggle to select between native OS DNS resolution (i.e. DNS server configured by the operating system) or external provider or external IPs. 2. Extra information? When using split DNS a host or domain will typically resolve to a private RFC1918 address because the internal DNS server resolves to the private IP of 10.x.x.x or 192.168.x.x instead of the public NAT IP. To overcome this it would be ideal to be able to tell the updater which DNS server to use to verify what the host or domain currently resolves to. For example: -Resolve current IP using host DNS -Resolve current IP using (Google (8.8.8.8), Cloudflare (1.1.1.1), or Quad9 (9.9.9.9))

saavagebueno closed this issue

2025-11-20 04:21:23 -05:00

saavagebueno commented

2025-11-20 04:21:24 -05:00

@g3rmanaviator commented on GitHub (Jun 9, 2022):

Can be accomplished by passing "--dns" option to container.

@g3rmanaviator commented on GitHub (Jun 9, 2022): Can be accomplished by passing "--dns" option to container.

saavagebueno commented

2025-11-20 04:21:24 -05:00

@qdm12 commented on GitHub (Jun 9, 2022):

Indeed!

Or

  dns: 1.1.1.1

for docker-compose.yml files.

@qdm12 commented on GitHub (Jun 9, 2022): Indeed! Or ```yml dns: 1.1.1.1 ``` for docker-compose.yml files.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#195