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…

Thanks for your help hoba!

Yes, I changed a intel NIC, as well as a new cable. Guess the problem was because of the physical problem!

Aldo

Yes.

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.

Maybe I should rename myself to wiki?  ;D

I'm afraid not just because the notebook owner said that at home he uses his adsl modem via ethernet adapter; he said that at his or his girlfriend home the network adapter works fine; I would say the same if he didnt said that for me, just because I did a lot of tests, with more than one operational system (I did with linux because I trust in its results, cant say the same about win) and could not work.

@jan:

@hoba:

Time to sniff to find out where the traffic goes.

I replicated the same issue on another machine with a different set of NIC's , is this a bug? Anyways I went back to /24 and to serve the other machines I installed a router.

I reinstalled for the nth time and did some test regarding network addresses, if network address is 10.10.10.x/24 it works but if 10.10.10.x/23, bottom half of the subnet cannot connect to the internet. If network address is 192.168.x.x series whether it's /24 or /23 , all clients can connect to the net. I wonder why, it's just simple routing.

I wouldn't think so unless ipcop supports CARP (which it doesn't afaik).

Turn off tinyDNS – you don't need it's functionality just for local name resolution. In the DNS forwarded select "Register DHCP leases in DNS forwarder" and "Register DHCP static mappings in DNS forwarder," then set your DHCP server to assign your routers IP for a dns server.

My installation was bad, new install fixed this one right up! ;D

If you have set a large enough DHCP range you could set the lease to something like 1-2 to months. Or you could use the Status->DHCP leases and use the '+' button to add static reservations so that they do not expire.

I've been having a similar problem recently that seems to be getting worse. Sometimes DNS resolution for a domain will simply stop working. I have to cycle dnsmasq and it works again. I'm going to try and hardcode the dns servers as nianderson suggested and see if that works.

@nianderson:

I recently installed a pfsense box with the intention of doing dual wan. Unfortunatly I had so many issues I had to back down to single wan for the time being. Even after going down to single wan and ensuring my upstream dns is set correctly I am experiencing many timeouts. All of the sudden all the pcs will start timing out on their requests. Cycling dnsmasq seems to temporarily resolve the issue. Has anyone else experienced these issues? Any idea where I should be looking for a resolution?

Thanks

Ok, thank you very much

:)