You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My home server provides a few docker containerized services such as traefik (for reverse proxy), Adguard Home, and other web tools.
One of them stopped working since AdGuard is now my official LAN DNS server.
It's a monitoring tool which crawl (real external) websites every 5mn in order to verify uptime and tls certification expiration.
From my ISP router, I've set this home server and its adguard runing (192.168.1.90) as DNS router. It seems my monitoring stopped working since then.
Of course, this monitoring service is hosted on the same machine, but has not the same ip since docker gives it a 172.18.0.9 which is even not in the same mask as my real local network.
I think this is the reason why it stopped working, but I can't figure out how I can fix this issue…
From adguard, everything seems ok:
From the monitoring docker container, i tried this:
~# ping 192.168.1.90
PING 192.168.1.90 (192.168.1.90): 56 data bytes
64 bytes from 192.168.1.90: seq=0 ttl=64 time=0.149 ms
64 bytes from 192.168.1.90: seq=1 ttl=64 time=0.151 ms
64 bytes from 192.168.1.90: seq=2 ttl=64 time=0.145 ms
64 bytes from 192.168.1.90: seq=3 ttl=64 time=0.178 ms
64 bytes from 192.168.1.90: seq=4 ttl=64 time=0.118 ms
^C
--- 192.168.1.90 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.118/0.148/0.178 ms
~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
900: eth0@if901: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
link/ether 02:42:ac:12:00:09 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.9/16 brd 172.18.255.255 scope global eth0
valid_lft forever preferred_lft forever
I also tried a nslookup, and I can see the query in AdGuard
But the container seems to never receive the response…
~# nslookup www.google.com;; connection timed out; no servers could be reached
What did I miss ? Can someone help and explain me please ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
My home server provides a few docker containerized services such as traefik (for reverse proxy), Adguard Home, and other web tools.
One of them stopped working since AdGuard is now my official LAN DNS server.
It's a monitoring tool which crawl (real external) websites every 5mn in order to verify uptime and tls certification expiration.
From my ISP router, I've set this home server and its adguard runing (
192.168.1.90
) as DNS router. It seems my monitoring stopped working since then.Of course, this monitoring service is hosted on the same machine, but has not the same ip since docker gives it a
172.18.0.9
which is even not in the same mask as my real local network.I think this is the reason why it stopped working, but I can't figure out how I can fix this issue…
From adguard, everything seems ok:
From the monitoring docker container, i tried this:
I also tried a nslookup, and I can see the query in AdGuard
But the container seems to never receive the response…
What did I miss ? Can someone help and explain me please ?
Beta Was this translation helpful? Give feedback.
All reactions