Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(readme): add configuration notice split-dns #389 #417

Closed
wants to merge 1 commit into from
Closed

docs(readme): add configuration notice split-dns #389 #417

wants to merge 1 commit into from

Conversation

affeldt28
Copy link

Adds a configuration notice to the readme.

If you configured your internal dns to point to an internal ip, to also use your services within your network. Ddns-updater will check against this ip and triggers an update to your configured provider. Due to the fact that this record will never be your public ip, this update will be done every time it checks if your ip is up to date.
Adding a public dns to your container will prevent this behavior, because then ddns-updater will not check against your internal dns.

@qdm12
Copy link
Owner

qdm12 commented Apr 13, 2023

First, thank you for the PR 👍
Second sorry for the massive delay!!
Third, in 464a557 I added documentation in the Readme for the variable RESOLVER_ADDRESS - here since January but undocumented weirdly - and linked to your issue #389 and that should work such that only the domain name lookup mechanism uses the DNS specified instead of the whole container, which is a bit better.
By default it still uses the Docker network DNS server, but it can be changed for example to 1.1.1.1:53.

@qdm12 qdm12 closed this Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants