If you can show the changes from your config history, I can see how that might have been possible. Diag>Backup/restore, Config history tab. Choose the left radio button from the last config revision that didn't work, the right radio button on the first config revision where it was fixed, and hit "diff". Paste that output. Can PM it to me if there's something there you're not comfortable posting publicly.

This is an old post, but in case anyone else is looking for how to import a custom dhcp.conf file, see this workaround: https://happy-coder.com/2014/06/27/pfsense-custom-dhcpd-configuration/

@cohomology: I am running a pi-hole(BTW, very nice piece of software to block ads) You can do this and more with the pfBlockerNG package: https://forum.pfsense.org/index.php?topic=102470.0

Expired leases will be reused if/when they're needed. dhcpd's behavior is to not hand out an expired lease again until all the leases that haven't yet been assigned are exhausted.

Are they there if you hit "show all configured leases"? Do they exist in /var/dhcpd/var/db/dhcpd.leases?

Your going to want to localise responses -y, –localise-queries     Return answers to DNS queries from /etc/hosts which depend on the interface over which the query was received. If a name in /etc/hosts has more than one address associated with it, and at least one of those addresses is on the same subnet as the interface to which the query was sent, then return only the address(es) on that subnet. This allows for a server to have multiple addresses in /etc/hosts corresponding to each of its interfaces, and hosts will get the correct address based on which network they are attached to. Currently this facility is limited to IPv4. You will then need to create entries in each vlan Here is a thread were this was discussed before https://forum.pfsense.org/index.php?topic=106872.0 I even put some examples in there on how to use..

Your LAN hosts need to be pointed at pfSense for DNS.

Well then run an authoritative name server if you want to use cnames.

It works just like the standard Unbound would in non-forwarding mode (in fact all non-forwarding resolution works the same). As an example a query for "www.example.tld" would first consult the root servers for NS records of top level domain ".tld", then query those nameservers for NS records of "example.tld" and finally query those nameservers for "www.example.tld". If any of the records are still in unbound's cache they will be used, otherwise the standard queries will be used to fetch them again.

I managed to solve this issue by destroying my VM and rebuilding it a 3rd time and all is well. matter is closed.

Thanks! this did solve the problem @AllGamer: for reference (working for me) after upgrading from 2.2.6 to 2.3 I had to enable DNS resolver to bring names from DHCP assigned dynamically, and DHCP reserved (sorry forgot the actual names used by pfsense) it was two separate check boxes. –- Edit --- Found the correct names I had to enable: Register DHCP leases in the DNS Resolver Register DHCP static mappings in the DNS Resolver both inside DNS Resolver / General Settings

I know that this is an old topic, but I recently just ran into this problem after setting up pfsense and a bridged Actiontec T2200 and did resolve it, so I figured I would post here in case someone stumbles across this thread like I did. After running a network capture between the Actiontec modem and my pfsense system, I found that pfsense was holding onto the last IP address that it had received while NATed behind the Actiontec in non-bridged mode. So what was happening was pfsense was sending a DHCP REQUEST packet with the private IP address and Telus DHCP was coming back with a DHCP NAK because private addresses are not allowed at customer endpoints. Makes sense. Pfsense was not giving this private address lease up though, so I had to wait until the lease had timed out on pfsense before forcing an IP renewal. At that point, it made a DHCP request with 0.0.0.0, which Telus's DHCP servers then responded to with a public IP. I think this may highlight a bug in pfsense 2.3 though, that Status -> Interfaces -> WAN release button does not appear to properly release the IP address.

Yea, and uncheck "Allow DNS server list to be overridden by DHCP/PPP on WAN" (2.2.6 calls it this way).

I run DHCP from my Cisco layer 3 switch and not pfsense.  I guess this might be another option.

Just wanted to chime in…happened again today. Could not reach any sites. Checked and unchecked "Do not use the DNS Forwarder or Resolver as a DNS server for the firewall", and its working fine again. Strange.  :P Edit: Looks like I have the same problems as the people in this thread: https://forum.pfsense.org/index.php?topic=103714.0 I get the message "kernel: pid 40874 (dnsmasq), uid 65534: exited on signal 11" in system log when the internet goes down. Seems like an update to 2.3.0 will fix the issue :)

dear i have the same problem mostly with Samsung mobile device still unable to figure out the problem My post https://forum.pfsense.org/index.php?topic=110153.0