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

    DNS Resolver has stopped working after 2.3.3

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 477 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 Offline
      mloiterman
      last edited by

      DNS resolution doesn't appear to be working for my iPhone, but only when I connect through my OpenVPN or IPSec tunnels.

      Basic network layout is as follows:
      192.168.1.0/24 LAN1
      192.168.2.0/24 IPSEC
      192.168.3.0/24 OPENVPN
      192.168.5.0/24 LAN3

      Relevant IP Addresses
      iPhone LAN1 IP - 192.168.1.67
      iPhone IPSEC IP - 192.168.2.1
      iPhone OPENVPN IP - 192.168.3.6
      MachineA LAN1 IP - 192.168.1.16

      Problem
      When I am connected to LAN1 via my WiFi, I can use the iPhone Prompt2 SSH client to connect to  "MachineA" and have it properly resolve it's IP, 192.168.1.16.

      If I disconnect from my WiFi and connect to the Internet via my cellular connection on my iPhone, then connect to my home network via either OpenVPN or IPSEC, the Prompt2 client can't resolve "MachineA" but it can connect to it with just the IP, 192.168.1.16.

      This seems to just have started after 2.3.3, but as far as I know, nothing in my configuration has changed.

      Additional Facts
      1.  It seems to impact ONLY my OpenVPN connection and IPSec connection because I can resolve "MachineA" from LAN2.
      2.  Since I can connect with the IP via from my OpenVPN or IPSEC connections, it doesn't appear to be a firewall issue at least as far as connectivity and not DNS.

      ![Screen Shot 2017-03-06 at 7.39.58 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.39.58 PM.png_thumb)
      ![Screen Shot 2017-03-06 at 7.39.58 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.39.58 PM.png)
      ![Screen Shot 2017-03-06 at 7.38.35 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.38.35 PM.png_thumb)
      ![Screen Shot 2017-03-06 at 7.38.35 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.38.35 PM.png)
      ![Screen Shot 2017-03-06 at 7.36.38 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.36.38 PM.png_thumb)
      ![Screen Shot 2017-03-06 at 7.36.38 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.36.38 PM.png)
      ![Screen Shot 2017-03-06 at 7.36.14 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.36.14 PM.png_thumb)
      ![Screen Shot 2017-03-06 at 7.36.14 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-06 at 7.36.14 PM.png)

      1 Reply Last reply Reply Quote 0
      • M Offline
        mloiterman
        last edited by

        Shortly after submitting this, I have checked the box "Provide a default domain name to clients" under Client Configuration in both my OpneVPN and IPSEC configuration settings and filled in my local domain and now everything appears to work.

        Is this expected behavior?

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