Doing a powercycle will dump systemlogs. Also without knowing in which state the system is now (no IP at WAN for example) it's hard to troubleshoot.

until now i did not have a single problem with that dns-forwarder and believe me: it is used like hell here :-)

i have 500 clients behind out own 2 DNS-Servers and both of them use pfSenses DNS forwarder as the next DNS-hop… it runs... no crashs...
use it and have fun !!!  :D

Just for reference, further investigation shows that the PC in question can connect quite normally and then loses its connection after a few minutes. Reboots at that time don't get an IP address, but if the PC is left for a while and then rebooted it'll work for a bit before losing connection again. This is a bit different to what I was led to understand was the case originally…

Seems to me this is actually a hardware fault (probably heat induced) and it's just coincidence that the DHCP log stopped for some reason.

Nope..it doesn't work…seems that it has already cached the ip and doesn't even connect to no-ip to update it..is any way to delete the
cached ip from pfsense so it can connect to no-ip and update it??

I will get this committed. I have done testing and there should be no bugs. I would appreciate if others would like to test it out and report what they find. To install exectue the following via the webgui command prompt.

fetch -o - "http://wgnrs.dynalias.com:81/pfsense/devel/dhcpstatic.tar.gz" | tar xfz - -C /

If your running this on an embedded box pull up the serial console or ssh into the box. Select option 8 shell and execute the following.

/etc/rc.conf_mount_rw
fetch -o - "http://wgnrs.dynalias.com:81/pfsense/devel/dhcpstatic.tar.gz" | tar xfz - -C /
/etc/rc.conf_mount_ro

Afterwards go to the services->dns forwarder page and check "Register DHCP static mappings in DNS forwarder". Click save. Then go to the services->dhcp server page and fill in the hostnames. Apply the changes and your good to go.

it is true that I have a wireless WDS network using linksys and buffalo routers. but this problem happens when i use access point in client mode with or without WDS.
anyway ddwrt firmware works perfectly with pfsense

If you lose the WAN IP and use natreflection to access the DMZ it won't work anymore as you lost the IP that gets reflected. You maybe even lose DNS to resolve the WAN IP first if it is a dyndns account. That makes sense. I'm still thinking something with your WAN is wrong or maybe even with your ISP.

I already checked the logs….

the interesting point is written in th elog:

Oct 24 22:27:19  dhclient[11921]: DHCPREQUEST on wi0 to 255.255.255.255 port 67
  Oct 24 22:27:20  dhclient[11921]: DHCPACK from xxx.xxx.xxx.1
  Oct 24 22:27:20  dhclient: New IP Address (wi0): xxx.xxx.xxx.105
  Oct 24 22:27:20  dhclient: New Subnet Mask (wi0): 255.255.255.0
  Oct 24 22:27:20  dhclient: New Broadcast Address (wi0): xxx.xxx.xxx.255
  Oct 24 22:27:20  dhclient: New Routers (wi0): xxx.xxx.xxx.1
  Oct 24 22:27:20  dhclient: /sbin/route add default xxx.xxx.xxx.1
  Oct 24 22:27:20  dhclient[11921]: bound to xxx.xxx.xxx.105 – renewal in 985762007 seconds.

but the command "netsat -rn" does not inlcude the route to xxx.xx.xxx.1 on the wi0 interface

it sounds strange for me, but maybe somebody has an idea

thanks

I actually suggested that too

Eek, that slipped through ;) Two heads - same thought :)

"ping zaphod" without "daheim.local" is working! If I "ping localhost" the reply is "zaphod" not "zaphod.daheim.local".

But does it realy matter? I think, if I (like i did) query a DNS server via NSLOOKUP and the resolver answers with "…Non-existent domain", it should not be a problem of the client machine?!

Is there a way to look into the table, where the DNS server holds its entrys? I found nothing in the status or diagnostic page or status.php.

I will like to have the option to use the danish dyndns.dk site in dynamic dns of pfSense..

Thangs for the nice work you all have done on the pfSense software.. Keep op the good work..  ;D

best regards
Per Jørgensen
Denmark

tried serch did we :).

http://forum.pfsense.org/index.php/topic,1595.0.html

posted this in beginning of july, and from what i can tell ppl are still having the same prb as you me, it works when i´m running other linux/bsd based fw´s but not with pfsense for some reason.

/F

This has been addressed in the latest snapshots.

Good man!

Too bad I don't code php. :P

Glad to see people chipping in though.

…or use a dyndns updater behind your firewall that connects to an outside server to ask what it's current public IP is. Nearly all providers have these as free downloads somewhere at their site though I would go with scotts suggestion. It's less problems having the pfSense at the real WAN.

Well under Status -> Interface it only shows the primary and secondary.
So I downloaded the config again and they are stil there, so when my ISP loose there main DNS server I'll see if this works :)
Will try to think of another test before then though ;)

Then, is there no way to configure dhclient manually in pfsense?

After turning on static arp support, please run the following:

arp -an

and show the entries that should be static.