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

    DNS leaks using OpenVPN client tunnel

    OpenVPN
    7
    69
    23.3k
    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.
    • G
      gschmidt
      last edited by

      you mean like this?

      snip.JPG
      snip.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • L
        lovan6
        last edited by

        I use the 2 ExpressVPn DNS on 1st and 2nd tab and Google DNS on 3rd and 4th = None

        1 Reply Last reply Reply Quote 0
        • G
          gschmidt
          last edited by

          Also when I switch them I get a DNS leak (which shows the ip address of my ISP)

          I have read your thread also…having the same kind of problem
          Only I am routing not all my network traffic trough the vpn tunnel, but only 2 devices.
          Which works, however I have DNS leaks.

          I cant figure out how to solve this.

          Also tried the DNS Resolver, but if I set the outgoing network interfaces to only EXPRESVPN, i have no internet at all hosts including the 2 running through the vpn tunnel.

          1 Reply Last reply Reply Quote 0
          • L
            lovan6
            last edited by

            On Dns resolver I used Network Interface = Lan, Expressvpn, Localhost.

            Outgoing Network = Wan, Lan, Expressvpn, Local host.

            1 Reply Last reply Reply Quote 0
            • G
              gcu_greyarea
              last edited by

              Hi,

              you could try the following:

              Disable DNS Resolver and Forwarder on pfSense.

              Create an Alias for the two hosts you want to use the VPN Tunnel. (Tunnel_Hosts)

              Create a Port Forward Rule:
              Source: Tunnel_Hosts , Dest Port:53
              Redirect Target IP:  Your VPN Providers DNS Server
              Redirect Port:53

              Create a Firewall Rule on your LAN IF:
              Source: Tunnel_Hosts
              Destination: Any
              Gateway: Tunnel_GW
              Tag: No_WAN_Egress

              Create Floating Rule:
              Interface: WAN
              Source: Tunnel_Hosts
              Quick (Apply immediately on Match)
              Direction: Any
              Tagged: No_WAN_Egress

              1 Reply Last reply Reply Quote 0
              • NeoDudeN
                NeoDude
                last edited by

                Setup an alias for Google DNS servers (8.8.8.8 & 8.8.4.4), or your VPN providers DNS servers, or any ones you want.

                Add a port forward on your LAN…

                Source Address = Your VPN Hosts Alias
                Dest Port = 53 (DNS)
                Redirect Target IP = Your DNS Alias created above
                Redirect Target Port = DNS

                On the corresponding automatically created LAN rule make sure your VPN Gateway is selected in advanced.

                Using this method you can add or remove VPN hosts by simply editing your VPN Hosts Alias, without having to mess about with static DNS addresses. Anything in your VPN Hosts alias will use the DNS servers in your alias created above through the VPN tunnel. Everything else will use the DNS resolver or whatever your default is.

                Home Server "Gandalf":  unRAID Pro 6 | MB**:**  ASUS Z9PE-D8 WS | CPU:  Dual Xeon E5-2670 | RAM:  64GB Crucial PC-1600 ECC

                1 Reply Last reply Reply Quote 0
                • G
                  gschmidt
                  last edited by

                  @NeoDude:

                  Setup an alias for Google DNS servers (8.8.8.8 & 8.8.4.4), or your VPN providers DNS servers, or any ones you want.

                  Add a port forward on your LAN…

                  Source Address = Your VPN Hosts Alias
                  Dest Port = 53 (DNS)
                  Redirect Target IP = Your DNS Alias created above
                  Redirect Target Port = DNS

                  On the corresponding automatically created LAN rule make sure your VPN Gateway is selected in advanced.

                  Using this method you can add or remove VPN hosts by simply editing your VPN Hosts Alias, without having to mess about with static DNS addresses. Anything in your VPN Hosts alias will use the DNS servers in your alias created above through the VPN tunnel. Everything else will use the DNS resolver or whatever your default is.

                  And keep the settings in the DNS Resolver (2.4.3) default, or do you have a specific selection of interfaces?

                  1 Reply Last reply Reply Quote 0
                  • S
                    strangegopher
                    last edited by

                    to fix dns leaks, i didn't do anything fancy, just set the dns servers under dhcp settings to be google dns. simple and it works.

                    I am also blocking any access to dns server on the firewall

                    https://www.dnsleaktest.com/

                    1 Reply Last reply Reply Quote 0
                    • G
                      gschmidt
                      last edited by

                      @strangegopher:

                      to fix dns leaks, i didn't do anything fancy, just set the dns servers under dhcp settings to be google dns. simple and it works.

                      I am also blocking any access to dns server on the firewall

                      https://www.dnsleaktest.com/

                      I made the port forward NAT rule…this does not leak my IPS provider, but all Google and OpenDNS servers...and I didn't even specify OpenDNS in pfsense

                      So if you perform a dnsleaktest, you only see the dns server of your VPN provider?

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by

                        @strangegopher:

                        to fix dns leaks, i didn't do anything fancy, just set the dns servers under dhcp settings to be google dns. simple and it works.

                        I am also blocking any access to dns server on the firewall

                        https://www.dnsleaktest.com/

                        This is all you need to do. DNS queries will be policy routed out the VPN just like all the other traffic.

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • S
                          strangegopher
                          last edited by

                          @gschmidt:

                          @strangegopher:

                          to fix dns leaks, i didn't do anything fancy, just set the dns servers under dhcp settings to be google dns. simple and it works.

                          I am also blocking any access to dns server on the firewall

                          https://www.dnsleaktest.com/

                          I made the port forward NAT rule…this does not leak my IPS provider, but all Google and OpenDNS servers...and I didn't even specify OpenDNS in pfsense

                          So if you perform a dnsleaktest, you only see the dns server of your VPN provider?

                          Purpose of dns leak test is to find out your real ip address even if your are behind a vpn. If there is no dns leak then you should see ip address of your vpn provider instead of your real ip address.

                          1 Reply Last reply Reply Quote 0
                          • G
                            gschmidt
                            last edited by

                            Thanx for helping, this a struggle for me for 2 weeks now.

                            I understand the leak testing. I already used the test site you linked me, this is why i noticed the leaks.
                            The problem is with my current settings the dnsleaktest site returns all Google and OpenDNS servers.
                            Not my ISP ip-address and also not my VPN provider DNS server.

                            There are many threads and tutorials about "route network clients policy based through a OpenVPN Client tunnel"
                            For my current setup I used (a combination of) the tutorials:
                            https://www.techhelpguides.com/2017/06/12/ultimate-pfsense-openvpn-guide/
                            https://www.infotechwerx.com/blog/Creating-pfSense-Connection-VPNBook

                            Now the first tutorial describes DNS leak prevention at "Step 11", which are 2 methods.
                            Method 1 (my current setup), but this leaks what I describe at the beginning of this reply
                            Method 2 is working correctly, however all other network clients (which are not meant to go through the openvpn client gateway), also use the DNS server of my VPN provider  because in the DNS resolver only the EXPRESSVPN gateway is selected for outgoing interfaces. As soon as i multi select EXPRESSVPN, LAN or WAN my ISP ip-address is leaking.

                            Now your answer looks so simple:

                            I have specified the Google servers at System/General Setup/DNS Server Settings
                            I have made static DHCP mappings for the network clients that need to go through the OpenVPN Gateway i have created.
                            I have made a firewall alias for those static mappings
                            I get the idea of Derelict to fill the vpn provider DNS servers on the static DHCP mappings

                            Now this one "I am also blocking any access to dns server on the firewall", the picture you attached shows that (selected) rule I guess?
                            A firewall rule on the LAN i guess?
                            what I see is an alias of all RFC 1918 ipv4 private networks, but I can't see the Destination port and gateway…is this any?

                            Besides that...I have a firewall rule on the LAN, which sends the static DHCP mappings (as an alias) through the VPN Client Gateway (EXPRESSVPN)
                            The other one is the NAT redirection to the DNS servers of my VPN provider (DNS leak prevention method 1)
                            The rest of the rules are default from pfSense 2.4.2 installation

                            above or under which rule should your "I am also blocking any access to dns server on the firewall" rule be located?

                            ![LAN Firewall Rules .JPG](/public/imported_attachments/1/LAN Firewall Rules .JPG)
                            ![LAN Firewall Rules .JPG_thumb](/public/imported_attachments/1/LAN Firewall Rules .JPG_thumb)

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              That second rule will never match because the traffic will be matched by the any rule above it and policy routed out the VPN.

                              Note the 0/0 counters there.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

                              1 Reply Last reply Reply Quote 0
                              • G
                                gschmidt
                                last edited by

                                Right!…I changed the order...but still...leaking Google and OpenDNS (which i did not specify anywhere in pfsense)

                                NAT-02.jpg = NAT Redirection of ExpressVPN DNS servers

                                Result= dnsleaktest.jpg

                                NAT-rule-01.JPG
                                NAT-rule-01.JPG_thumb
                                NAT-rule-02.JPG
                                NAT-rule-02.JPG_thumb
                                dnsleaktest.JPG
                                dnsleaktest.JPG_thumb

                                1 Reply Last reply Reply Quote 0
                                • DerelictD
                                  Derelict LAYER 8 Netgate
                                  last edited by

                                  WHAT DNS SERVERS ARE YOUR CLIENTS SET TO USE?

                                  DNS is NOT this hard, people.

                                  With your rules like that, the express_vpn_dns servers will be queried using the default gateway, NOT the VPN, unless you have redirect gateway for the VPN itself.

                                  Chattanooga, Tennessee, USA
                                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    strangegopher
                                    last edited by

                                    @gschmidt:

                                    I have specified the Google servers at System/General Setup/DNS Server Settings

                                    No need to do this as unbound by default uses root servers for dns, so no need for dns forwarding.
                                    If you want you can remove all the dns servers from this section and dns will still work.

                                    above or under which rule should your "I am also blocking any access to dns server on the firewall" rule be located?

                                    Sorry I posted the wrong image.
                                    This is what the dns rule should look like:
                                    (above all other rules in your case [except anti-lockout])
                                    Action: Block
                                    Protocol: IPv4 TCP/UDP
                                    Source: ExpressVPN_Hosts
                                    Src Port: Any
                                    Destination: This Firewall
                                    Dst Port: 53 (DNS)

                                    That will block access to firewall's dns server.

                                    Now you will have to to do to is go to:
                                    Services/DHCP Server/LAN
                                    and Under DNS Servers add dns server of your choice (like google dns).

                                    Also like Derelict mentioned you can remove the 2nd rule of NAT redirection to expressvpn.
                                    And any other port forwarding rules u created under Firewall -> Nat.

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      gschmidt
                                      last edited by

                                      On the static DHCP mappings in pfSense (which is my main router): Empty
                                      On client 1 (Window 10 PC): automatically (which is the gateway 192.168.1.1)
                                      On client 2 (linux device): 192.168.1.1

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        strangegopher
                                        last edited by

                                        Do you not see this under Services/DHCP Server/LAN?

                                        Capture.PNG
                                        Capture.PNG_thumb

                                        1 Reply Last reply Reply Quote 0
                                        • DerelictD
                                          Derelict LAYER 8 Netgate
                                          last edited by

                                          That DOES NOT MEAN that you do not have static DNS servers on the client you are testing, bro.

                                          This really is. not. that. hard.

                                          Chattanooga, Tennessee, USA
                                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                          1 Reply Last reply Reply Quote 0
                                          • G
                                            gschmidt
                                            last edited by

                                            Ok….I have created the rule =Block rule.jpg
                                            Added the google dns servers = "DHCP Server DNS Server.jpg"
                                            and the ExpressVPN DNS servers = Static DHCP Mapping.jpg"

                                            dnsleaktest result= dnsleaktest.jpg

                                            :o

                                            ![Block Rule.JPG](/public/imported_attachments/1/Block Rule.JPG)
                                            ![Block Rule.JPG_thumb](/public/imported_attachments/1/Block Rule.JPG_thumb)
                                            ![DHCP Server DNS Server.JPG](/public/imported_attachments/1/DHCP Server DNS Server.JPG)
                                            ![DHCP Server DNS Server.JPG_thumb](/public/imported_attachments/1/DHCP Server DNS Server.JPG_thumb)
                                            ![Static DHCP Mapping.JPG](/public/imported_attachments/1/Static DHCP Mapping.JPG)
                                            ![Static DHCP Mapping.JPG_thumb](/public/imported_attachments/1/Static DHCP Mapping.JPG_thumb)
                                            dnsleaktest.JPG
                                            dnsleaktest.JPG_thumb

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