Resolving names over wireguard subnet

[kss]

I apologize if this is an already answered question --

I have connected my two sites using wireguard VPN site to site setup. How do you resolve names across the VPN? I am able to ping the far-end machines by their IP addresses, from either site, but not by name.

Both sites run similarly configured opnsense firewalls; both sites use unbound. I tried adding the DNS server name of the far end site to the DNS server list but that didn't work. I even tried running WINS (gasp!) at both sites on a raspberry pi that is running pi-hole, again, no luck. I seem to be missing something fundamental here, for which I seek help.

[Patrick M. Hausen]

Use different domains for both sites. Add a domain override pointing to the remote unbound for the remote domain at both sites.

There is to my knowledge no solution to "merge" all hosts on both sides into one domain with OPNsense only. If you run Active Directory or similar infrastructure it's rather trivial, because you normally have a DC at each site.

[kss]

I will try that, thanks!

[kss]

 Thanks for your insight -- that I should have different domain names at the two sites connected via VPN, I have a more functional site-to-site VPN.

• I have name to IP resolution when I ping computers at the other site, although the ping itself times out
• I added both domains to the LAN DHCP4 search list, now I can use the hostname or the FQDN for name resolution
• RDP and VNC work across the VPN from any computer to any other computer by just using the name, IP address, or FQDN

Only thing that is still blocked is being able to browse directories using file manager -- both styles of addressing -- \\PC-2 and \\192.168.2.2 -- time out.

Pretty sure these are being blocked by the firewall rules, but am nervous about experimenting with them.