push the routes via dhcp like ip route add 10.0.0.0/24 via 192.168.0.1 set Additional BOOTP/DHCP Options in DHCP Server number 121 type string value 18:0a:00:00:c0:a8:00:01 Tested with Tumbleweed dhclient https://forum.pfsense.org/index.php?topic=94570.0

Roger, thanks for your help…

Domain override would be used to point a domain to a different NS.. If you want cnn.com to resolve to a specific IP - then you would use a HOST override.. That is fantastically helpful and my exact problem. Thank you.

@simplei: It seems it's a openwrt configuration problem.  ;) Solved the issue. Thanks. Hi, can you share your OpenWRT configuration?. I have a similar setup and I'm stucked with the problem that my clients do not get addresses through DHCP. :-(

There should be little to no overhead imho, its not like its going to send traffic out the wan interface to the isp and back when you connect to the wan-ip from the lan-net.. It still a ip local to the system which is routed to lo0 both the same for wan-ip and lan-ip.

The dhcp bleed out problem started when I accidentally connected untagged vlan 100 port to untagged vlan 200 port. Maybe I should try tagged ports to prevent dhcp requests going to a foreign subnet.

that is not a ping that is a dig.. Do a ping - and can you ping any other devices on that network?  Can you ping  the pfsense IP on that network?

hmmm I have not gotten back to this - and do not recall if I ever filed any sort of bug report.  I am currently running 2.4 beta - I will try and reproduce again in 2.4 and if clean there will fire up a copy of 2.3.4 and try it there.

Hi and thanks for the immediate response Just before the comment i did an ipconfig /all to make sure of the DNS configuration and for some reason, maybe forgotten from previous troubleshooting, indeed i had static configuration in the IPV4 DNS section, i changed it automatically use the DHCP settings and i can now get the correct response :-) Thank you so much, you were right and my problem is solved

It seems like upgrading to 2.3.4 fixed my issue.  It has been 2 days.  Keeping my finger crossed.

Your welcome ;) hehehe

Avahi would be completely pointless with only 1 segment.

@ypanier: Hi, I have exactly the same issue with 2.3.4 and previously with the 2.3.3 The lease than the client retrieve is shown in DHCP Leases on master/slave but the hostname is only shown on the server who gave the lease To resolve the behavior i tried : disable dns forward / resolver disable dhcp server run pfSsh.php playback disabledhcpd rm /var/dhcpd/var/db/dhcpd.leases* reboot both slave and master reconfigure the dhcpd service It seems that the problem is well known : https://lists.isc.org/pipermail/dhcp-users/2016-October/020331.html It seems that these bug was resolved in 4.3.5 (version installed on pfsense) but continue to encounter it Anyone have an idea or patch ? best regards, temp. i disabled dhcp sync in CARP and also disabled second DHCP server to get arround this.  :(

I have this same problem, thanks for the tip… I'll try it out today.

"1) I don't use FQDN, I just use hostnames" While jimp answer is correct for short hand only wanting to put in a shortname and letting the system add the suffix for you.  It is pure bad practice to not use a FQDN.. Does does not work via host name, but a fqdn.  So you can get lazy and let the system add the domain part for you.  You should always use fqdn when doing any sort of dns query and not rely on a suffix search to do it for you. Vs adding them via xml - you can always just load a file in unbound that has your entries in there for you.  In the custom/advanced box.. example server: include: /etc/unbound_ad_servers include: /etc/unbound_mystuff Here are 2 files that I load into unbound that have stuff in them, one is ad_servers I redirect and another is my stuff I load. Another option which is normally the case with stuff you want to put in dns for your hosts is just setup a dhcp reservation for them, ie a static and register your static in the resolver.  Then all you have to do is create the static host entries and you kill 2 birds with 1 stone.

I captured the DHCP-Packet, so its no problem with pfsense  :)

fixed! restart didnt help i had to stop it and then start