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

    Trialling CloudConnexa with a single site

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 215 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 McMurphy

      I am testing CloudConnexa and have my LAN behind pfSense which is connected to CloudConnexa as a "connector".
      OpenVPN Networks (1).png

      I wish to run all LAN DNS queries through the CloudConnexa DNS filter.

      The CloudConnexa DNS server is 100.96.1.1 and this is only accessible from pfSense, so workstations on the LAN cannot access the CloudConnexa DNS server directly

      My initial through was to setup the pfSense Resolver in forwarding mode and list the CloudConnexa DNS server in System => General Setup

      My concern here is that when the connection to CloudConnexa is down I need DNS resolution in order to be able to establish the connection to CloudConnexa so only using the CloudConnexa DNS server will not work.
      22.03.2024_08.27.27_REC.png

      Presently I have pfSense operating as a forwarder and checking the DNS servers sequentially.
      22.03.2024_08.35.27_REC.png

      Additionally (out of my depth here) It appears that traffic to CloudConnexa is routed via the OpenVPN interface.
      22.03.2024_08.29.05_REC.png

      Does this mean that any DNS queries to 100.96.1.1 will automatically be routed via CloudConnexa as opposed to be having the specify CloudConnexa as the GW for this DNS server?
      22.03.2024_08.33.35_REC.png

      Thanks in advance

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