Replies: 7 comments 7 replies
-
127.0.0.1 is the address for localhost. If you are entering this address as the DNS server for clients, you are telling them to use their own host as the DNS which is highly unlikely to work. 172.17.0.2 looks like the IP address of the container, which will not be accessible to hosts on your LAN. Find the IP address of the DS220+ and set this as the DNS server for clients (e.g. 192.168.1.1). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for taking the time to reply. I can see how the DNS settings I applied do not make sense but the AdGuard Home Setup Guide says (copied and pasted): Configure your devices I was simply doing what the guide says. Anyway, I tried using the IP address of my Synology DS220+ which is fixed at 192.168.1.220 but that did not work either. I copied and pasted the full IP address of my Synology DS220+ including the port: http://192.168.1.220:5000 and at leat that allowed traffic but when I switched off my Browser (Brave) Shields and uBlock Origin and opened a web page which I thought would have ads (dailymail.co.uk), it was full of ads. In the AdGuard Home Dashboard, it reports: DNS Queries 0 In DNS Blocklists, I have the Adguard DNS filter (updated) with 57,633 rules enabled. I tried blocking Amazon in Blocked services but the main Amazon site (amazon.com) still loaded, So, something is now right but something else is clearly wrong. Incidentally, I can only input 4 integers in my router's DNS settings so I cannot use the full IP address of my Synology DS220+ and with therefore have to apply the settings on a per device basis. |
Beta Was this translation helpful? Give feedback.
-
|
A few things to clarify from your reply...I don't have a Synology, but this guide looks OK. Which guide are you following? Regardless of the guide, you will need to have chosen a network type (host, bridge, or macvlan). I use host network in my docker because then setup is much easier (no port mapping required) and I can see the IP addresses of all the DNS clients. What network type are you using?
I think that's what the browser wizard says when you run it for the first time? Agreed, it's a bit confusing. If you are using host or bridge network then you just use the IP address of the Synology. This is called out in the guide I linked to above (Step 2).
To clarify, a server runs services on 'well known ports' - e.g. DNS is published on port 53, http is on port 80, and so on. Port 5000 is the port that the Synology web UI runs on - that won't work for DNS. In your router set the primary DNS to the IP address of your Synology (provided you are using host or bridge network) - forget about the port. Leave the secondary DNS blank. Remove any DNS configuration from your clients (set to auto DNS). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for taking the time to help me. I'm away from my Mac where I feel more comfortable doing this (replying on an iPad) - more windows on two screens and it's getting late here in the UK. I should also say that I am a little out of my comfort zone but I am usually pretty good at carrying out technical instructions thanks to military training several decades ago - so I thought I would be able to do this without sending distress signals. I don't have links to the guides I had followed (they are on my Mac) - there were three or four all of which seemed to have gaps which may or may not be due to their age and software version. I'm using the Host mode. I could try Macvlan but Bridge is out of the question as almost all, if not all, the devices on my network have fixed IPs - most are not necessary but some are. I'll have a good read of the guide you kindly linked to. I think it might come down to starting again from scratch. |
Beta Was this translation helpful? Give feedback.
-
|
Having read the guide you linked to along with all the comments, my eyes are watering. As I said previously, there is obviously something right about my installation - if I put my Synology IP address in my Mac's DNS settings, I get no traffic but if I add a port (any port) I get traffic but the ads are not blocked. I hadn't thought to reboot the Synology but have now done so and according to Dr F, it could take 24 hours and I think I need that time to prepare myself because I think I am going to have to start again from scratch. |
Beta Was this translation helpful? Give feedback.
-
|
I think starting with a fresh install following a guide is your best bet. Then you can call out if/when you get stuck on a specific step. The guide I linked to might look overwhelming at first glance, but it's spelling out in great detail everything you need to do - the steps themselves are quite simple and line up with the official AGH docker guide. If you're not quite ready to blow away your current install, I would have a look at what you have entered in upstream DNS servers (Settings > DNS Settings). Try entering the Cloudflare addresses, 1 per line like this:
Under that, select 'Parallel requests' then click on 'Apply'. Once you've done that, click on 'Test upstreams'. Do you get a box telling you that the specified servers are working correctly? If so, set your client DNS as advised in an earlier post and try again. |
Beta Was this translation helpful? Give feedback.
-
|
If you have been expecting an earlier reply, thank you for your patience. I have been sick for a week and then had other things to catch up on. I decided to really start from scratch and reinstall Container Manager as well as I had tried installing AdGuard a couple of times previously and maybe I had not deleted the containers correctly - when I uninstalled Container Manager, I opted to remove everything as apart from AdGuard, I have no other containers. I had felt a bit daunted before I started the installation of AdGuard but I really needn't have as it took just a few minutes and is now up and running when the DNS is applied on my Mac - I just need to test it on my router. When I previously tested the DNS on my router, it somehow ended up blocking my access to the router interface - however, after a lengthy panic, I managed to get in by reconfiguring my Mac's DNS settings. Anyway, things are looking good - I'm just waiting to be able to test it on my girlfriend's iPad. Thank you very much for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I don't need it on my Mac, I was only trying to get this working to block ads on my girlfriend's iPad. I looked into iCloud Private Relay but it is a part of iCloud+ which neither my girlfriend or I have and is therefore inactive on our iPads. It seems a bit strange that the AdGuard Home configuration guide for iOS devices makes it seem a simple case of changing the DNS settings. I've found other suggestions of how to get AdGuard Home working with iOS but haven't really got very far. One suggests enabling encryption but when I have tried that, I got the following error: Error: control/tls/validate | port 443 is not available, cannot enable HTTPS on it | 400 Another suggests adding /dns-query part to calls (on a iPhone) but to be honest, I'm not sure what that actually means. I tried adding it to the iPad's DNS settings; i.e. 192.168.1.220/dns-query but that didn't make a difference. I don't know of any other place that this could be applied on a device but they were quite clear that these were device settings: https://www.reddit.com/r/Adguard/comments/1c78mye/ios_device_not_working_with_adguard_home/ I found a small number of posts on here about the problem but there were no replies. I'm still looking for other ideas but I suppose I may have to give up at some point. |
Beta Was this translation helpful? Give feedback.
-
|
In Settings > Encryption Settings, untick the first box (Enable Encryption HTTPS etc), tick the second box (Enable Plain DNS), then click 'Save Configuration'. Now, head to Settings > DNS Settings and clear everything in the first box (Upstream DNS Servers) and enter the plain Cloudflare servers like this: 1.1.1.1 Select 'Parallel Requests' to speed up your DNS resolving, then click 'Apply'. I am quietly confident this will fix your problems. If it does, then you can play around with DNS over HTTPS/TLS/QUIC or whatever protocol you like. I suspect you have ticked 'Enable Encryption' under Settings > Encryption settings. This is not required unless you want DNS over HTTPS etc from your clients to Adguard Home. 99.9% of the time this is not what users want/need. You can untick this option and still use DNS over HTTPS from Adguard Home to the upstream DNS (e.g. Cloudflare). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I tried that and on my iPad - it seems to work, although there are ad placeholders which I don't get on my Mac. I'll test it on my girlfriend's iPad when she gets home - she has to use Safari(!!!) which, from what I have been reading, may behave differently. |
Beta Was this translation helpful? Give feedback.
-
|
Well, everything seems to be working on my girlfriends iPad as well - except that ads on Facebook and Twitter/X are not being blocked. I have the latest AdGuard DNS filter installed which seems to include Facebook and the old Twitter/X URL but at least the general AdGuard Home mechanism is working. Thank you very much for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Great stuff! Not sure about Facebook, I don't use that. Ads on Twitter aren't blocked by my AGH install either - this is a known limitation - https://github.com/AdguardTeam/AdGuardHome#comparison-limitations Ad placeholders will still remain with a DNS-based ad blocker too. Try some different upstream servers now that you know it's working...Personally I use DNS over TLS and have three upstreams - Adguard, Cloudflare and NextDNS operating in parallel. Make sure your upstream DNS is non-filtering though - you don't want to filtering to occur upstream, you want it to occur on your Adguard Home install |
Beta Was this translation helpful? Give feedback.
-
I have AdGuard installed on my Synology DS220+ via Container Manager but when I input the DNS 127.0.0.1 and 172.17.0.2 into any device (router or Mac), I get a no internet error on my browser.
Unfortunately, one guide I tried to follow seemed to be a bit disjointed, the images and instructions didn't always match up but it was the most recent guide I could find but I think I have done everything correctly - at least I can access the AdGuard home screen and see the settings as well as the Setup Guide (which provided the DNS I tried inputing to my devices).
I don't see any settings there or in the AdGuard container which don't look right - it isn't as if there were many settings to configure - so I don't know what is going wrong.
Do the DNS settings need more than a short time to propagate? When I tried to configure the router, I could see the new DNS settings on my Mac after switching the WiFi off and back on again and I also tried configuring the DNS settings on my Mac manually but each time I got a browser error saying that the web page I was trying to find could not be found with a generic DNS error.
I'd be very grateful for any advice as I am trying to help block ads on my girlfriends iPad but the version of Brave now on the app store is not compatible with it.
Beta Was this translation helpful? Give feedback.
All reactions