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

    Finally adguard local server working)))

    Scheduled Pinned Locked Moved General pfSense Questions
    1 Posts 1 Posters 147 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.
    • A
      Antibiotic
      last edited by Antibiotic

      Hello my friends,
      This is instruction for home users, whom to want a baby "Adguard DNS Server" filtering DNS for whole your Home network but still use pfSense Unbound resolver as main, this is my settings! I did fight with this almost one week. I'm not a guru of IT and step by step with some wrong steps in the beginning set up this dream)))

      INTERFACE1 192.168.10.1
      INTERFACE2 192.168.20.1
      ADGUARD SERVER INTERFACE 192.168.30.1
      ADGUARD LOCAL IP 192.168.30.5
      ADGUARD DNS listening port 3053

      I have set in Adguard DNS settings everywhere pfSense 192.168.30.1
      Screenshot_6-6-2024_19144_192.168.30.5.jpeg

      pfSense Unbound as resolver mode NOT forward mode

      Screenshot_6-6-2024_191526_192.168.20.1.jpeg

      Screenshot_6-6-2024_194427_192.168.20.1.jpeg

      Screenshot_6-6-2024_19468_192.168.20.1.jpeg

      Screenshot_6-6-2024_194759_192.168.20.1.jpeg

      pfSense NAT port forward rules:

      Screenshot_6-6-2024_19178_192.168.20.1.jpeg

      Finally all my DNS from whole Home networks are filtering and still use pfSense Unbound resolver as main for outbound .

      Screenshot_6-6-2024_192155_192.168.30.5.jpeg
      I think did correct and happy now)))

      Only Average processing time on Adguard dashboard still big in ms ( I think calculated average from set up and later on will get down during permanently use), if anybody have experience please give a tip how to avoid this. Query log is fast:
      Screenshot_6-6-2024_192547_192.168.30.5.jpeg

      Ports opened on WAN of my Adguard Server:

      Screenshot_6-6-2024_192951_192.168.30.5.jpeg

      Port forwarding on Adguard server, but in doubt is this requiring or not, but I did:

      Screenshot_6-6-2024_193856_192.168.30.5.jpeg

      INTERFACES rules:

      Screenshot_6-6-2024_195049_192.168.20.1.jpeg

      Adguard server interface rules:

      Screenshot_6-6-2024_195117_192.168.20.1.jpeg

      I still use pfBlockerNG with IP filtering lists for firewalling but disable DNSBL filtering)))

      pfSense plus 24.11 on Topton mini PC
      CPU: Intel N100
      NIC: Intel i-226v 4 pcs
      RAM : 16 GB DDR5
      Disk: 128 GB NVMe
      Brgds, Archi

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