-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
DNS bind multiple host #1401
Comments
Commenting to see if this is something that is possible? I am looking to install this on a system that already runs a DNS server (for local network lookups/overrides) so I need to be able to specify another IP (both IPv4 and IPv6) to use for the AdGuardHome configuration. |
Being able to set multiple addresses as dns bind_host would be really beneficial, especially given that Ubuntu by default binds to 127.0.0.1:53 and thus Adguard cannot build to 0.0.0.0:53. Even if you only want to bind to one interface, e.g. eth0, it is absolutely needed to bind to multiple addresses to provide both ipv4 and ipv6 coverage. |
this would be really nice to have, i want to bind it to one ipv4 and one ipv6 ip, and not use 0.0.0.0:53 witch makes it bind to all ips on the computer (docker ips, bridged ips, ips on other interfaces) |
This is need to get the full usage with ipv4 + ipv6. |
I'm surely missing something... Running Adguard on Docker, Ubuntu 20.04 which has two NICs, one wired one wlan. Adguard binds to wlan, which is not what I want as the DNS set on DHCP server is the wired nic interface... And of course this behaviour is messing all my lan. |
This would be very useful since I'm currently forced to allow AGH to bind to everything just so that IPv4 and IPv6 DNS will both work, not to mention this does not work in a container (as far as I can tell). Additionally, it doesn't seem possible to bind to both v4 and v6 on one specific interface (but not touch the others). IPv6 is only a thing if I configure AGH to bind to everything. |
+1. This needs resolved, please. Are there any workarounds at the moment? |
Worry not, it's planned on the closest release. |
Updates #1401. Squashed commit of the following: commit a18c3f0 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 21:55:26 2021 +0300 home: imp code commit 2b4a28c Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 20:55:08 2021 +0300 all: rm unused field commit 5766a97 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 16:40:14 2021 +0300 all: support multiple dns hosts
As of snapshot 5d0d32b on the I will now close this issue. If you find any bugs with the new feature, please file them as separate bugs. Thanks! |
@ainar-g I see this from the wiki - My limited knowledge believes the ipv4 and ipv6 addresses are on the same interface. Are you saying by this comment that we would NOT be able to bind both an ipv6 and ipv4 address if they are on the same interface? One of the requirements (for me/my use-case) is to have AGH listen on both ipv4 and ipv6... With the change in place, how would I listen to both my ipv4 and ipv6 addresses on ens192? |
@cjustinhall, you are correct! I've improved that section of our Wiki and also added examples as well as a note about |
Had a look at the wiki. Good modifications. Very clear now. Thanks. Will give this a try. |
Updates AdguardTeam#1401. Squashed commit of the following: commit a18c3f0 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 21:55:26 2021 +0300 home: imp code commit 2b4a28c Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 20:55:08 2021 +0300 all: rm unused field commit 5766a97 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Mar 22 16:40:14 2021 +0300 all: support multiple dns hosts
Updates AdguardTeam#1401. Updates AdguardTeam#2646. Squashed commit of the following: commit 93b025a Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Wed Mar 24 16:41:07 2021 +0300 home: fix migration, imp code
Prerequisites
Problem Description
I want to bind the DNS host to
127.0.0.1
and::1
.But the configuration only can set one address.
Work:
Not work
Proposed Solution
Alternatives Considered
Additional Information
The text was updated successfully, but these errors were encountered: