I have done this accidentally also. pfSense keeps thinking that whatever is in that cache file is the current IP address that the name translates to. I seems like it should actually translate the name out on the real internet and see what that value is, then if it is different from the interface's current public IP, make the change with the dynamic DNS provider. But, I guess, it takes time for a change at the dynamic DNS provider to propagate through the internet DNS and various caches. So the translated name might be a stale value, particularly if the customer has selected a long TTL for the name.
I wonder how this can be done better?
Delete the cache file from /conf, that will make it forget the last setting and it will have to do an update.

just a cosmetic reason but i managed it with the pfsense dhcp server, thanks anyway

If you have an Active Directory environment, there's probably some way to assign DNS servers via a user-based Group Policy.

Great to hear - and if you donated to pfsense, that is just icing on the cake!  Thanks!!

You need to create a NEW interface, vlan for example. And no there would be no network overlap.

As to how dhcp clients would know - you would have to setup a ip helper cisco calls it.  Dhcp relay on your switch.

Albra,
Wasn't that comfortable editing the xml but maybe I need to warm up to it on the test box.  Prefer your option "C" the best if it works.  I saw the paste window you describe and hoped it may be a method of bulk entry but the note below states that additional options are to be entered.  I thought "options' meant custom forwarder settings rather than hostname/ip entries similar to the paste window in the unbound package.  So is the syntax hostname/ip<space>hostname/ip<space>hostname/ip?

I'm doing many IP's because my network has 10 gateways with distributed DHCP on each subnet.  And I want Kiwi syslog server to resolve private IP's without relying on if the client device had a hostname entered into it's GUI.  If/when PfSense adds multiple DHCP pools such that leases can be served by PfSense to all gateway subnets then I can abandon this method.

I use the unbound package so the forwarder is disabled.</space></space>

Yes CopSoft it would be helpful a few more details.  Are you saying a down interface would be needed for each additional DHCP pool desired?  I have about 10 gateways setup on the LAN.  If I need 10 down interfaces this may not be a feasible or practical hack in my case.

Solved it by starting dhcpd with "-d". This showed an additional missing lib named "ld-elf.so.1". After copying this file also to the chroot-environment, everything was fine.

my WAN has directly public IP. about one day change once IP.  PFsense sometime can't normal update.

@gavit:

Is there a way to see how the watchdog checks if my ip changed?
I'd like to see which IP address he's checking. My PFsense is behind my ADSL modem so the ip address of my pfsense/WAN will always remain the same. The IP Address of my ADSLmodem/WAN will change.

The pfSense software uses http://checkip.dyndns.org/ to find the current public IP of the WAN. That will return the public IP that your front-end ADSL router/modem has, and then pfSense will update the dynamic DNS name to point to that public IP. I do this lots from pfSense with a private WAN IP behind an ADSL router, it works fine.
Of course, if you actually want to provide some service to outside users using that dynamic DNS name, then you will also have to port forward the relevant port(s) on the ADSL router through to your pfSense.

No it doesn't work that way, the only reason it lets you add that without an IP is for users who use the option to only assign IPs to known listed MACs.

my host machine is currently connected to a router. in this way the host machine will still get its internet connection.(am using teamviewer).

but prior to connecting the host machine to the router, i forgot to reconfig pfs WAN interface to dhcp. So that's where i think the conflict is, although I am able to run pfs as guest on vbox but i can't open the web GUI (based on my experience) if my internet source is dhcp yet my pfs WAN is static.

anyways, yeah i was able to use your advise, i didnt realize the "2" set interface can set the WAN into dhscp, and thanks alot!!!!

The VPN connection has an IP 192.168.10.0 and the network I am connecting to is also 192.168.10.0. The LAN IP on my home network is 192.168.5.0. Wouldn't it cause issues if my Home (192.168.5.0) and my VPN (192.168.10.0) are on the same segment?

I may have misunderstood and all you are asking is if the VPN has the same as the network I am connecting to. If that is the question , yes.

I only connected for a few minutes each time , I should let it sit for awhile and see if they show up.

The setup I am using now is different than before. Pfsense is still the firewall but I was using a virtual Windows server 2003 to control DNS and WINS , now I am just running a physical 2012 server . The reason I switched was because I previously was using a Samba fileserver on Ubuntu 12.04 and it was kind of pointless to have both. I could have setup the Ubuntu server as both DNS and WINS but really when I plan on running 50 or so machines in the virtual server I think server 2012 is better suited.

Thanks again

Happy Holidays from the Newby here.

I am having the same issue here. Use Cox Communications with Dynamic IP address. every Saturday night at midnight, the lease expires on the WAN IP and all I see are

"apinger: ALARM: WAN_DHCP(NN.N.NN.1) *** down ***" (where the n's = the ip address up the gateway to Cox).

The only solution for me is to reboot the PFSense Firewall.

I am now trying a script from the following post and will keep you up to date on my progress.

http://forum.pfsense.org/index.php/topic,17243.msg89348.html#msg89348  (or look up message # 89348 in the forum search)

My setup is:
2.1-RELEASE (i386)
built on Wed Sep 11 18:16:22 EDT 2013
FreeBSD 8.3-RELEASE-p11

You are on the latest version.
Platform pfSense
CPU Type Intel(R) Atom(TM) CPU D510 @ 1.66GHz
Current: 1257 MHz, Max: 1676 MHz
4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads
Using onboard adapter as wan (re0)
Using Asus Gigabit PCI NIC as lan (re1)

Also, I want to confirm that this is only happening on PFSENSE (version 2.1), NOT my standby $50 Asus consumer gateway, WiFi routers, nor Clear0s, m0n0wall, SmoothWall.

I hope this helps.

JonnyB
SunnySD, Ca

In System->General Setup, make sure you specify a DNS server for each WAN. Then when 1 WAN is down, there will still be a DNS server reachable on the other WAN.
e.g. 8.8.8.8 on WAn1, 8.8.4.4 on WAN2
If you have a reasonable "ordinary" configuration (e.g. 1 LAN with 2 real WANs to the internet) then you can also enable default gateway switching (in System->Advanced Miscellaneous tab) and then the default route will switch over and pfSense itself will get to the internet from the shell.

@ptt:

Your "Block" rule is wrong….

The Source port should be "Any"  not 53...  Only the "Dest" port should be 53  :)

Also, the "total bandwith up/down" Rule, allows traffic from "Any" to "Any".... get rid of that rule  ;)

thanks for the response.  I did change the source port to any and removed the bandwith up down rule. the up/down rule was to provide a rule for a limiter ( which I guess I do not have configured correctly). Once I removed the bandwith up/down rule dns responses were blocked correctly on the wan interface and I don't need the port 53 rule this was a total meatware problem.  :o

Right, lets continue there :)

Thanks for your replies so far.