Closed 0xb33 closed 1 year ago
Any update on this? Looks good to me
Any idea how we can change this in a running environment ?
Apologies for the delayed reply. I tried it on my test instance and for me queries do no longer load after implementing this change. I think this is because in the adguard config, the WAN IP is used to connect to unbound; i.e. it will try to connect over 'internet' instead of internally to the unbound instance, which will not reply anymore since it's now only listening for connections on localhost. The only way to make this work is to use the hostname of the unbound docker container, as the internal IP address of the unbound container might change after recreation, but I don't know (yet) if adguard supports that.
An alternative approach would be to work with multiple (separate) networks that differentiate between internal en external (internet) traffic, for example like in this (unrelated) docker-compose file: https://github.com/HenryQW/Awesome-TTRSS/blob/main/docker-compose.yml
But yes, you are right. I agree this should be fixed.I will try to look into it in the near future, but I cannot commit to any dates at this time.
Howdy, did you get a chance to take a look?
Howdy, did you get a chance to take a look?
After shutting down Adhole.org, I haven't really looked at anything Adguard related anymore to be honest, so no. Doubting what to do with this repo as I'm not using it myself anymore...
I would not mind forking this repo and continu development where needed.
I would not mind forking this repo and continu development where needed.
Shall I add you as maintainer to this repo instead?
Thats fine too :)
Thats fine too :)
Great, I have invited you :)
I have started totally clean and redid everything. I created a terraform script that creates a free oracle cloud instance (https://github.com/bruvv/terraform-oracle-cloud-free-adguard) if you run that script it will create everything that is needed. In the instance.tf file you will find the command to run: "ansible-playbook --connection=local --inventory 127.0.0.1, /home/ubuntu/adguard/configure_adguard.yml -e "hostname=adguard.website.com emailaddress=here@email.com""
I am still testing this so I will not merge it but when I feel it is ready, @Freekers do you want me to merge it in your repo? (https://github.com/bruvv/ansible-adguard-unbound)
@Freekers I again made a big change to my ansible script, would you think it will be better to close this one and merge mine?
You mean archiving my repo?
no I meant merging my repo with yours.
Sounds good. I guess you need to open a new merge request for that? :)
Well you gave me permission to edit the repo so I can just merge but wanted to pass it by you first :)
Oh that's right, I forgot. Feel free to go ahead ;)
changed unbound container to listen only on locally, so then only adguard container after filtering, pass queries to this recursive DNS server, and block access to publicly accessing this recursive DNS server.
e.g
passes from Adguard, successfully blocks this domain as per OISD rules filter.
whereas, because of your recursive DNS server publically accessible on port 5353, you can simply bypass the filters, sending requests directly to your recursive DNS server. which i think should be blocked.
e.g