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

    Dual WAN DMZ subnet DNS quits after 12 hours

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 1.6k 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.
    • S
      sgebhard
      last edited by

      Hello everyone, I am fairly new to Pfsense (1 year) and am having problems with my DMZ subnet.  Setup is as follows:
      2 WAN connections (both from same ISP, same DNS servers) with load balancing and fail over

      1 LAN subnet with nothing forwarded to it (192.168.0.0)
      1 DMZ subnet with all the devices that need ports on it (192.168.3.0), DMZ interface bridged with main WAN (WAN1)
      Runnng Squid with HAVP
      DNS forwarder enabled

      After reboot everything works great for about 12 hours, then the DMZ stops resolving DNS, LAN subnet is fine, not affected.  When it stops, I looked in the logs and cannot see any anomolies in DNS forwarder, Squid, or HAVP, after DNS stops a reboot fixes it immediately again for 12 hours.  I don't think it is a configuration issue, as if it were it would not work at all.  What am I missing?  The packet capture attached is on the DMZ subnet, you can see the resolve fails.  Any assistance on this would be great, I am tearing my hair out!  Thanks

      [dmz packat capture.txt](/public/imported_attachments/1/dmz packat capture.txt)

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