Comment on Need help getting domain to resolve over LAN
Zwuzelmaus@feddit.org 5 days ago
I tell it to point docmost.example.com to 192.168.1.80, […] but actually nothing happens. I get a connection timed out error.
I suggest to collect more info about this “nothing”.
ping from your PC on the inside to the name docmost.example.com
ping from your PC on the inside to the number 192.168.1.80
traceroute from your PC on the inside to the name docmost.example.com
traceroute from your PC on the inside to the number 192.168.1.80
Then do the same in the reverse direction: from that docker container to your PC.
Maybe traceroute shows you some stations on the route. Then do the same from this station.
Write down the results thoroughly.
iAmTheTot@sh.itjust.works 5 days ago
Thanks for the suggestions.
Ping from PC to
docmost.example.com: Pings fine, packet loss.Ping from PC to
192.168.1.80: Pings fine, no packet loss.Traceroute from PC to
docmost.example.com: 1 hop, all <1 ms, to192.168.1.80Traceroute from PC to
192.168.1.80: 1 hop, all <1 msPing from Nginx container to PC: Pings fine, no packet loss.
Traceroute from Nginx container to PC: Hops to
172.18.0.1in <1ms, and then it times out on subsequent hops.I decided to try to traceroute from my PC to
172.18.0.1and172.18.0.9which is the actual IP of the Nginx container according to UNRAID, and in both cases they hop to192.168.1.254which is my router, and then all subsequent hops time out.Do you know why pings would go through without any loss but traceroutes would fail? Any idea what’s going on here?
Zwuzelmaus@feddit.org 5 days ago
Now you know that the problem is not your DNS.
It is either your routing or firewalling.