I'm also seeing this problem.
I have to disable DNS forwarding to get tinydns to correctly bind to the interface and start. With DNS forwarder disabled I get no external resolution. Re-enable DNS forwarder, and disable tinydns and external resolution comes back.
Try to add an afterfilterchangesshellcommand-tag (see http://blog.pfsense.org/?p=31) to automatically restart the dhcp server on interface linkup. You'll have to download the config.xml and manually add a section to it and reupload it again.
Update on DNS issues. After removing my real DNS server entries from my SBS 2003 and adding the pfSense as the only entry, and following the previous instructions of adding the internal Web Servers local names and addresses in the DNS Forwarder area of the pfSense, all is well.
Thanks again very much.
Here is what I found out…
Yesterday night and I am 100% sure of that, DHCP server was pointing to the CARP BOX2.
This morning I ran ipconfig /all and it was pointing to CARP BOX1, then I disabled and enabled network connection to renew DHCP and it was pointing to BOX2 again. After reading your post I disabled all rules except the one with LOAD BALANCER and changed it to default gateway.
I renewed connection and got routed to BOX1 DHCP server. Then I connected another PC to the network and got routed to DHCP BOX1.
I thought that your solution worked out. I went back to my PC renewed connection and got back on DHCP BOX2. I guess it was not enough for me, so I used another nic in my pc. I unplagued the cable from old nic into the new one and got DHCP BOX1 right away. Renewed connection and still DHCP BOX1, reverted rules to original ones and still DHCP BOX1. It does not matter now how many times I renew connection I still get BOX1.
For the moment I thought that it should work now. I went back to PC that I just connected to network. It was sitting on DHCP BOX1. I renewed connections and it went to DHCP BOX2.
I am guessing that this is not the firewall problem!
Indeed, your way is better (using Backup/Restore).
(afaik just adding the static mac entries would not force it to reboot)
It doesnt, it's just that using the "Edit File", new macs won't display until I reboot.
Thanks again.
Hi Perry
Hmm, I had those set, well, I removed them, saved, and set them again, and later the pfSense was rebooted for a unrelated reason, and now it works…
Hi,
It seems that nobody has responded to this problem in quite a while. I ran into the same problem. First I thought it has to do with installation problem or missing some library, but I tried reinstalling the DNS Server module and still got the same problem. All of my other features are working OK. Can anyone at least suggest the nature of this problem?
I have read on other thread about some other issues with DNS server so obviously the module is working for some people.
Thanks.
@hoba:
Is it only the DNS-forwarder that is not synced over or other settings as well?
Other settings are synced flawlessly. (the only thing I have to manually sync are the PPTP server/user settings as there is no option to sync that piece of information)
I had another post that seems to have disappeared… odd...
Anyway, found that if we use a non-existent address (as others have mentioned) such as 192.168.1.0 (I'm using 192.168.1.x network) then domain-level blocking works.
So, 0.0.0.0 works for host-level blocking only, even though it used to work for both.