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
{{ message }}
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
The VPN connection is working.
I can ping IP Addresses in the remote network. e.g. 10.100.0.55
But when i thy to ping the hostname e.g. host1.domain.local the name is resolves to the ip address 127.0.0.1.
i've tested it on my machine and directly on the UDM-PRO.
Via DHCP i've set these DNS servers:
IP UDM-PRO
IP of remote DNS Server in the VPN remote network
Do i've forgot anything?
Thx.
The text was updated successfully, but these errors were encountered:
user@Users-MBP ~ % traceroute host1.domain.local
traceroute to host1.domain.local (127.0.0.1), 64 hops max, 52 byte packets
1 localhost (127.0.0.1) 0.485 ms 0.058 ms 0.046 ms
And now the traceroute to the IP of this host:
user@Users-MBP ~ % traceroute 10.100.0.55
traceroute to 10.100.0.55 (10.100.0.55), 64 hops max, 52 byte packets
1 unifi (192.168.1.1) 1.246 ms 0.845 ms 0.911 ms
2 172.172.33.15 (172.172.33.15) 17.696 ms 17.424 ms 20.025 ms
3 10.100.0.55 (10.100.0.55) 18.970 ms * 19.770 ms
So you're saying DNS isn't working, is that the problem? IDK what could be done about the DNS, I believe it's being pushed by my OpenVPN connection but I'm not utilizing it on the UDM directly.
yes.
but when i change the order of the DNS servers in the DHCP configuration, it works. In this case the remote DNS has to be the first DNS server. Otherwise UDM-PRO lookup the hostname with 127.0.0.1.
Hi
The VPN connection is working.
I can ping IP Addresses in the remote network. e.g. 10.100.0.55
But when i thy to ping the hostname e.g. host1.domain.local the name is resolves to the ip address 127.0.0.1.
i've tested it on my machine and directly on the UDM-PRO.
Via DHCP i've set these DNS servers:
Do i've forgot anything?
Thx.
The text was updated successfully, but these errors were encountered: