• DNS Domain Override Not Working

    6
    0 Votes
    6 Posts
    1k Views
    M
    @msswift I've made too many edits to last post so I'm being blocked as a spammer. Please cross out "The near end of the tunnel does NAT." It's neither true nor relevant.
  • DNS Forwarder works but DNS Resolver do not work with docker container.

    2
    0 Votes
    2 Posts
    874 Views
    V
    @fandangos said in DNS Forwarder works but DNS Resolver do not work with docker container.: So I've found that I can fix it if I disable the DNS Resolver service and instead use the DNS Forwarder. My question is basically, why? Why DNS Resolver might be blocking the requests from docker containers? The Resolver uses an access control list. By default all local networks assigned to pfSense interfaces are allowed to access it. If you want other devices to access the Resolver you have to add the IPs or networks to the ACL on the Access Lists tab. So check how the docker requests the DNS server and if it either does at all. I understand DNS Resolver is great because there's no need for external servers providing the IP for an address, it can resolve it somehow (I have no idea how it's done). The DNS Resolver uses root DNS servers by default. You cannot configure them by yourself. However, in forwarder mode it uses the servers you've entered in System > General or even the ones configured by DHCP if applicable and you allow to override your settings. is DNS Resolver faster compared to DNS Forwarder? The Resolver caches host name IP pairs. So when you resolve a cached host name it would be faster naturally. Otherwise it won't really be.
  • Unbound DNS Resolver through Wireguard Tunnel (Mullvad VPN)

    18
    1 Votes
    18 Posts
    10k Views
    E
    @packetpirate Glad you figured this out! :)
  • Does DHCP Relay require firewall rule?

    18
    0 Votes
    18 Posts
    6k Views
    GertjanG
    @johnpoz I knew (something) about 'quick'. The FreeBSD pf documentation says : look here PF FAQ and there I find a lot of info. The quick Keyword As indicated earlier, each packet is evaluated against the filter ruleset from top to bottom. By default, the packet is marked for passage, which can be changed by any rule, and could be changed back and forth several times before the end of the filter rules. The last matching rule wins, but there is one exception to this: The quick option on a filtering rule has the effect of canceling any further rule processing and causes the specified action to be taken. Let's look at a couple examples: I stand corrected
  • AVAHI issues after upgrading to 2.6.0

    2
    0 Votes
    2 Posts
    537 Views
    johnpozJ
    @beefer said in AVAHI issues after upgrading to 2.6.0: mDNS broadcast is replicated accross vlans, So sniff on the interface the printer is connected too - does the printer answer? When you see the discovery go out..
  • DNS Forwarder not sending logs after appliance restart

    1
    0 Votes
    1 Posts
    268 Views
    No one has replied
  • 0 Votes
    1 Posts
    192 Views
    No one has replied
  • DNS Resolver Not responding

    11
    0 Votes
    11 Posts
    1k Views
    R
    First, @bmeeks, I appreciate your advice to back off and deal with the DNS Resolver issue without the complications of pfBlocker. Plus I did not know that the DNS Resolver worked out of the box. @steveits said in DNS Resolver Not responding: Why is your WAN going down? This turned out to be a pivotal question. I started looking at my cable modem's settings. The modem's DHCPv6 Prefix is hard coded to 56, instead of 64 which is the WAN interface default, so I changed that. I also could not find anything in my modem that looked like a DHCPv6 configuration settings, just the prefix. The modem's not exactly young. So I checked Request Only IPv6 Prefix on the pfSense WAN interface... ...and... ...drum roll... I think it works! The DNS Resolver has been responding to requests for about 20min, and either logging is broken, or unbound isn't starting and stopping anymore. I keep staring at it and waiting for something to break, but so far, so good. Thanks to everyone for your help!!! And please stick around to help when I try to set up pfBlocker.
  • Trying to use PfSense DDNS with Dreamhost

    ddns dreamhost dns vpn
    1
    1 Votes
    1 Posts
    814 Views
    No one has replied
  • DHCP Service will no longer start

    4
    0 Votes
    4 Posts
    743 Views
    G
    OK. I believe it's something to do with ntopng. Removing that package appears to have resolved the issue.
  • DHCP Reservation massive update script

    1
    0 Votes
    1 Posts
    193 Views
    No one has replied
  • Unbound stops listening on Interface

    12
    0 Votes
    12 Posts
    2k Views
    T
    Why is there still no proper fix for this issue? It is still completely broken in 2.6.0 and both patches that are supposed to "fix" this in 2.7.0 are nothing but a mere workaround: https://redmine.pfsense.org/issues/12612 https://redmine.pfsense.org/issues/12613 With these patches applied every restart of a device connected to one of the in/out interface of the DNS Resolver causes a restart of the unbound service (including complete loss of cache and temporary loss of DNS resolution for all devices). This bug is going to force me to downgrade back to 2.4.5-p1 and will eventually make me chose another firewall solution in the near future. Sorry if I sound frustrated, but major bugs like this should not be ignored like this for almost a year.
  • DynDNS for Private IP

    15
    0 Votes
    15 Posts
    6k Views
    S
    @Gertjan Appreciate the test and useful information. You should be promoted to the highest level Moderator. It's helpful to warn users away from RFC1918 on public DNS, provided it's not obstructive or failing to imagine non-standard use cases. BTW been doing DNS for 20 years and it's only "BROKEN!!" if interferes with interoperability. My fringe use case: embedded Linux devices in QA networks, which for "reasons" can't use a private DNS server. Probably some homelabs also. Having to run nmap across a bunch of network blocks gets really old, fast. Anyways: thanks for the tip. https://freedns.afraid.org/
  • DNS resolver for use in China

    7
    0 Votes
    7 Posts
    2k Views
    1amt0ny1
    @johnpoz got it thanks!
  • UEFI HTTP booting w/ 2.6.0

    3
    1
    0 Votes
    3 Posts
    860 Views
    P
    @jimp Done! https://redmine.pfsense.org/issues/12892 Thanks for the help on this one! Cheers, Ben
  • Split DNS Isn't Working?

    4
    5
    0 Votes
    4 Posts
    756 Views
    NollipfSenseN
    @gertjan said in Split DNS Isn't Working?: @nollipfsense said in Split DNS Isn't Working?: NIC A NIC doing DNS ? A NIC is a bunch of electronics like capacitors and inductors for creating a good line impedance, a clock detctor (using a PLL), a big shift registers, some CRC bit test functionality. Some front end 'PCI' logic to make the NIC accessible for the CPU and DMA for the actual data transfer. A NIC might be able do take some useful decisions based on the MAC parts in the packet headers. Check the CRC for you. The on board ROM should be seen as a BIOS extension, so the NIC could be used by the BIOS to remote boot on OS or something like that. These are my words, but I'm pretty sure a NIC doesn't know what "DNS" is. It knowledge stops at the "TCP/IP" border, which is far lower on the OSI ladder. Yeah, I know it sounds funny and the way I said it with emotional twist at the time looking at the Freepbx interface and seeing DNS 10.8.27.1 grayed out, knowing it was the right opportunity to do a clean 2.6 install. While in the bios, I did thought about that, but it was too late, I already committed to a clean install long over due. The sad part is I swore that my latest configuration change was backed up, and it turned out to be a lie. The more one does it; the more one learns, I guess. I rebuilt both pfSense and FreePBX last night.
  • DNS Overides

    dns override dns forwarder dns custom
    15
    0 Votes
    15 Posts
    3k Views
    S
    @gertjan said in DNS Overides: deep in the past Using my "Internet years" theory (like dog years) that's 7 Internet years ago.
  • Am I getting "Static ARP" wrong?

    12
    1
    0 Votes
    12 Posts
    2k Views
    JKnottJ
    @scilek said in Am I getting "Static ARP" wrong?: since they don't have manageable switched WTF? What sort of business doesn't have a managed switch? Even home users can have them, as they're so cheap. Avoid TP-Link though.
  • Host Overrides are Not Resolving (used to)

    15
    0 Votes
    15 Posts
    5k Views
    W
    For visiting readers, the solution is above — this is just follow up. And additional thanks. @johnpoz -- Yup, you called it. ;) So, in a post-mortem, one should ask how that got missed by me. John's answer, "your "browser" or what your using to try and resolve these fqdn isn't using your dns - browsers like to use doh now.. which would point to some dns outside of your control" mentioned it, but my brain didn't pick up on it. When I read the phrase "fdqn isn't using your dns", I immediately turned to my client's operating system's DNS resolvers – and that pointed to pfSense. It simply did not dawn on me that something else might be transporting, what I thought was strictly local, DNS resolution outside my network. And, as so, I wasn't in a mindset to go looking for that. And, if I'm honest with myself, when I read "browsers like to use doh now" I completely misinterpreted that part of the sentence entirely. As the abbreviation doh all lowercase did not trigger anything to me as, at the time I read it, it was an unknown acronym that I didn't look up because was thinking he was saying this about 'browsers not using fully qualified domain names' (which he was not): [image: 1646178036143-doh.png] And, given that I had just – in err – having proved to myself I was pointing at pfSense, which it was, missed the subtly of what was actually being said. 'doh' didn't catch my attention, 'DoH' might have, but I was well down a different rabbit hole. Having never have encountered this kind of problem before, and aware DoH (DNS over HTTPS) was in use just fine in other environments I've messed with, I didn't give it the second thought that it so rightly deserved. Instead, I got hyper-focused on the 'forwarding' and 'DNSSEC' part, which were two things I went off to read about (and now in hindsight may not fully grok in the context of pfSense's unbound DNS Resolver). The security device is a Firewalla Gold. The way the hardware lab is set up is akin to this at the moment (it changes often): [image: 1646179800517-the-lab.png] At any given time either (or both) Firewalla devices may be removed; they tend to sit in bridge mode and send live notifications to my phone of devices being on the network that shouldn't be there (and give good insight to device details that are), further limit traffic by region, and provide alerts for certain kinds of activity or data usage patterns. It has identified a number of devices sleeping in the closet I'd forgotten about and my DHCP pool was happily assigning addresses to, but I was having a hard time tracking down. It has also alerted me to rogue behaviors certain applications and devices do at off hours; stuff I would not have thought to dig through logs to find. While I know they can act as firewalls themselves, I am extremely fond of pfSense and enjoy the low-level bit-twiddling granularity it provides. But there are high-level features pfSense simply does not provide (or I am ignorant of), and this fills those gaps when I'm not using the devices at external locations. I'm not interested in having Firewalla be "the" firewall, as this configuration isn't for a home (rather a personal lab for education purposes), and I have no minors requiring content restrictions or scheduled access times. I am acutely aware that it is possible to forego the need for two Firewalla devices (or even one) by integrating VLAN rules. Each Firewalla device has its own profiles, which I can compare behaviors. The current set of experiments are around keeping devices on various networks from seeing each other at level 2 and/or level 3 layers or only allowing certain kinds of access, such as from one network but not the other. I'm with you on not forwarding DNS, your arguments are sound, and I've been reading a number of security articles that say the same thing – much of the "protection" you think you're getting isn't real, as it can easily be determined by other ways. I'll have to look into DNS Over TLS (DoT), as that was entirely new to me as well. Part of the adventure has been stepping into the deeper part of the networking pool to improve my own understanding, and I hit that point where the gentle tapering swimming pool bottom suddenly drops to well beyond my height. Thank you again for all your help, insight, and advise.
  • Undbound enabled DNSSEC plus IPSEC Peers with dynamic IPs

    2
    0 Votes
    2 Posts
    305 Views
    A
    No one is facing similar effects? Anyone an idea where this may come from?
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.