Direct access to AGH not possible, but through my router #7587
Unanswered
karlranseierausrom
asked this question in
Q&A
Replies: 1 comment
-
You need to set the DNS on the LAN/Client settings not the WAN/internet DNS. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a AVM fritzbox 7530AX, where I have set the DNS server to my HomeAssistant with AdGuard Add-On.
192.168.178.108 is the IP of my Hass/AdGuard.
With this setting all queries go through the router and everything is listed in AGH as if it comes from my router:
In AGH I have set three clients with their IP adresses. Only the router has some counts.
So far everything is correct, because DNS server for every client is my router, as I gathered by using nslookup. The router than uses AGH as DNS-server, if I understand correctly.
The disadvantage is, that I cannot directly apply rules to certain clients (like for my fridge, printer and so on). I want every client connect directly to AGH.
To make every client directly connect to AGH, I have set the local DNS in avm fritzbox firmware:
When I than disconnect and connect any client (android, wind10) it gets no connection to the internet. Using nslookup I found out, that the IP address is correct: 192.168.178.108, so that the client tries to use that as DNS server. Looking up example.org gives an time out for dns resolving.
The same happens when I manually switch to the AGH-IP by nslookup:
In some dicussions I found out, that cients should be created. I did that, but have not created any rules.
Someone noted, that I have to add
to the yaml. It did not work, therefore I removed it again.
I have the feeling that I am doing a very stupid mistake. Does someone have an idea what I could do to solve the problem?
Best regards
karl.ranseier
edit: homeassistant OS on Rpi5. Home assistant is the version of today. AGH version 5.2.2
Beta Was this translation helpful? Give feedback.
All reactions