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

    DNS resolution over OpenVPN

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 3 Posters 859 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.
    • M
      McMurphy
      last edited by

      I have an OpenVPN connection to a remote site.
      From my main site I can ping all IPs at the remote site.
      At my main site I have added the remote DNS server IP to the list of DNS servers under "General Setup" however am unable to resolve any of the remote site names.

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

        Cannot resolve any of the names from where?

        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
        • M
          McMurphy
          last edited by

          I cannot resolve name on the remote network from the main network.
          The local LAN is 192.168.1.0/24
          The remote LAN is 192.168.16.0/24

          user@domain:~$ ifconfig
          lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:7096 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7096 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:943073 (943.0 KB) TX bytes:943073 (943.0 KB)

          wlp1s0 Link encap:Ethernet HWaddr e4:02:9b:ce:2a:f2
          inet addr:192.168.1.175 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::e602:9bff:fece:2af2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:72921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47350 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:37537403 (37.5 MB) TX bytes:8700199 (8.7 MB)

          user@domain:~$ ping -c4 192.168.16.204
          PING 192.168.16.204 (192.168.16.204) 56(84) bytes of data.
          64 bytes from 192.168.16.204: icmp_seq=1 ttl=62 time=32.5 ms
          64 bytes from 192.168.16.204: icmp_seq=2 ttl=62 time=33.2 ms
          64 bytes from 192.168.16.204: icmp_seq=3 ttl=62 time=33.9 ms
          64 bytes from 192.168.16.204: icmp_seq=4 ttl=62 time=31.5 ms

          --- 192.168.16.204 ping statistics ---
          4 packets transmitted, 4 received, 0% packet loss, time 3005ms
          rtt min/avg/max/mdev = 31.590/32.826/33.916/0.870 ms

          user@domain:~$ nslookup 192.168.16.204
          Server: 127.0.1.1
          Address: 127.0.1.1#53

          Non-authoritative answer:
          *** Can't find 204.16.168.192.in-addr.arpa.: No answer

          Authoritative answers can be found from:

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

            Sorry. I wasn't clear enough. It doesn't really matter who can ping what from where in this case.

            Where are the workstations?

            What are the DNS servers those workstations are configured to use?

            Where are those name servers?

            How are those name servers configured?

            user@domain:~$ nslookup 192.168.16.204

            What is name server 127.0.1.1? It obviously does not have access to information to answer that in-addr query.

            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
            • M
              McMurphy
              last edited by

              The workstations are on a remote LAN (192.168.16.0/24) on the other end of an OpenVPN link

              The remote LAN is a Windows AD network.
              DC, DHCP & DNS is 192.168.16.2

              These remote workstations are configured to use the DNS server above.

              The name server is the Windows SBS server on the remote LAN.

              On the remote LAN I can enter:

              C:>nslookup 192.168.16.204
              Server: server.remotedomain.local
              Address: 192.168.16.2

              Name: tc204.remotedomain.local
              Address: 192.168.16.204

              I have no idea what 127.0.1.1 is. On the main pfSense home page it shows the DNS servers as:

              DNS server(s)
              127.0.0.1
              8.8.4.4
              8.8.8.8
              192.168.16.2

              I hope this answers what you were after...

              1 Reply Last reply Reply Quote 0
              • M
                mark.mcadam
                last edited by

                did you get this solved? im having a silimar issue

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