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

    DNS resolver setup questions – caching from upstream DNS failing

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 499 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
      MakOwner
      last edited by

      The "DNS Resolver" service is the equivalent to a caching DNS server with locally defined hosts injected via the Host Overrrides table.

      Is this not the case?

      The DNS Forwarding creates a lot of confusion on my part - near as i can tell they are mutually exclusive, however, if the caching of requests for information held upstream is not working for me with only the DNS Resolver enabled.

      pfSense is sitting inside a private 10.x.x.x IPV4 network, and we want NAT for a 192.168.x.x class B behind pfSense.
      DHCP offered inside the Class B with all of the static and DHCP assigned ip addresses pointing to the pfSense as DNS, NTP and default gateway.

      This would duplicate an existing IPCop configuration i just shut down.

      Routing seems to be working fine, locally defined static and DHCP hosts properly resolve inside the class B network, however, nothing outside the private network resolves.

      What section of the backup XML file would be needed to troubleshoot the settings that I have probably hosed up that's causing this?
      that seems more efficient than trying to post screen captures.

      Resolved, I think.

      <facepalm>:o

      The DNS Forwarder option of the DNS Resolver service.

      Well, maybe not.  Every time I save any sort of change to anything DNS related I can see a text overlay in the header of the web page saying "Warning in array() blah blah blah null in line 239 in /etc/…/unbound.inc I think it was.  Can't find this in the logs anywhere yet.

      :(

      Wonderful.  IPV6 DHCP no longer injects to the local resolver.
      Any way to get this working?
      I wouldn't think this would that odd of a configuration.

      This error that you can barely see here pops up three or four times as the DNS resolver starts during reboot.

      Arrgghh... Double posted the same image!

      pfSense_Error.png
      pfSense_Error.png_thumb
      pfSense_Error.png
      pfSense_Error.png_thumb</facepalm>

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