Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Wireguard

    Scheduled Pinned Locked Moved WireGuard
    14 Posts 2 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • neterminN
      netermin
      last edited by

      Hello forum friends I have configured a VPN with Wireguard, when I connect to it and I want to access any shared resource on the network by name I get an error, but by IP address if I let me, but if it is a computer on the LAN if I can connect by name, please could you help me solve this dilemma

      KOMK 1 Reply Last reply Reply Quote 0
      • KOMK
        KOM @netermin
        last edited by

        @netermin Your problem is that pfSense can't resolve those FQDNs. One solution is to add a domain override to DNS Resolver so that any lookups to anything from that domain will be resolved that the domain's DNS. I do this for my OpenVPN tunnel to work. Any reference to lan.mycompany.com is handled by my company's DNS.

        neterminN 1 Reply Last reply Reply Quote 0
        • neterminN
          netermin @KOM
          last edited by

          @kom Friend, how can I add a domain override to DNS Resolver?

          KOMK 1 Reply Last reply Reply Quote 0
          • KOMK
            KOM @netermin
            last edited by

            @netermin Services - DNS Resolver. Scroll down to the bottom. It's right there.

            neterminN 1 Reply Last reply Reply Quote 1
            • neterminN
              netermin @KOM
              last edited by

              @kom Friend I do not know if that serves me for what I need, the detail is when I'm in VPN and I do \192.168.1.20 takes me to the shared resource but when I do \Testing gives me error.

              KOMK 1 Reply Last reply Reply Quote 0
              • KOMK
                KOM @netermin
                last edited by

                @netermin Yes, because pfSense DNS has no idea who \Testing is. If you only need to connect to that one server then you could add a host override to set Testing to its LAN IP over the VPN. If you need to access many different hosts over the VPN then a domain override helps.

                neterminN 1 Reply Last reply Reply Quote 1
                • neterminN
                  netermin @KOM
                  last edited by

                  @kom good friend, sorry to bother you so much but could you tell me in this image how to configure it, I have tried several ways and nothing that can access the shared folder of the server by name. Thank you very much!

                  06.png

                  KOMK 1 Reply Last reply Reply Quote 0
                  • KOMK
                    KOM @netermin
                    last edited by

                    @netermin

                    Host: testing
                    Domain: Whatever domain you have pfSense configured for, found under System - General Setup - System - Domain
                    IP Address: the IP address of the testing server, 192.168.1.20
                    Description: whatever you want or leave it blank

                    Click Save

                    Now when you resolve testing, it will return 192.168.1.20

                    neterminN 1 Reply Last reply Reply Quote 1
                    • neterminN
                      netermin @KOM
                      last edited by

                      @kom Amigo, this is how I have configured it and it does not work.

                      7.png

                      8.png

                      KOMK 1 Reply Last reply Reply Quote 0
                      • KOMK
                        KOM @netermin
                        last edited by

                        @netermin What do you get for:

                        nslookup pruebas
                        

                        and

                        nslookup pruebas.pfsense.netermin.com
                        
                        neterminN 1 Reply Last reply Reply Quote 1
                        • neterminN
                          netermin @KOM
                          last edited by

                          @kom When I do nslookup tests, it resolves:

                          Server: dns.google
                          Address: 8.8.8.8.8

                          When I do nslookup tests.pfsense.netermin.com

                          Server: dns.google
                          Address: 8.8.8.8.8

                          KOMK 1 Reply Last reply Reply Quote 0
                          • KOMK
                            KOM @netermin
                            last edited by

                            @netermin Your client appears to be using Google for DNS. You can't override that way. Your clients must use pfSense for DNS for overrides to work.

                            neterminN 1 Reply Last reply Reply Quote 1
                            • neterminN
                              netermin @KOM
                              last edited by

                              @kom Would you place as primary DNS the pfsense ip on the network adapters?

                              KOMK 1 Reply Last reply Reply Quote 0
                              • KOMK
                                KOM @netermin
                                last edited by KOM

                                @netermin I don't understand what you mean.

                                pfSense has 2 DNS systems available, a forwarder and a resolver. Resolver is enabled by default. Your clients should be using pfSense as their DNS, either statically or set via DHCP.

                                Edit: If you don't want to make any changes to your DNS and you just need access to one or two servers from the one client, you could always edit its hosts file to add those names and point them to their IPs.

                                1 Reply Last reply Reply Quote 1
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.