@Referee2000: Again - thanks!  Where do you want the gift card sent to?  :-) I give my time to the pfSense forums as way of expressing my gratitude for this great project. If you would like to make a gift of a more material kind how about a donation to the pfSense project (http://www.pfsense.org/index.php?option=com_content&task=view&id=47&Itemid=77 ) or a micro loan to a project in Thailand or a Pacific Islands country (see http://www.kiva.org)?

i have no idea - i don't have your modem or ISP info.  just try DHCP on the pfsense WAN and see if it works.

What version of pfSense is this on? 1.2.2? 1.2.3-RC3? 2.0?

Services –> DHCP Server

Hello! I just installed pfsense and I have the same problem, almost.. I only get a lease ack if/when the dhcprequest is sent to 255.255.255.255: boot: Nov 28 09:17:31 dhclient[5711]: DHCPREQUEST on em0 to 255.255.255.255 port 67 Nov 28 09:17:32 dhclient[5711]: bound to 85.24.. – renewal in 450 seconds. then, 450 secs later: Nov 28 09:25:04 dhclient[5711]: DHCPREQUEST on em0 to 85.24.202.1 port 67 Nov 28 09:25:04 dhclient[5711]: SENDING DIRECT Nov 28 09:25:07 dhclient[5711]: DHCPREQUEST on em0 to 85.24.202.1 port 67 Nov 28 09:25:07 dhclient[5711]: SENDING DIRECT this goes on until: Nov 28 09:45:23 dhclient[5711]: DHCPREQUEST on em0 to 255.255.255.255 port 67 Nov 28 09:45:24 dhclient[5711]: DHCPACK from 85.24.202.1 Nov 28 09:45:24 dhclient[5711]: bound to 85.24.. – renewal in 450 seconds. What I have found so far: On my windows machine, I get a new lease directly after 450 secs, when the DHCPREQUEST is sent directly to the dhcp-server. So I ran wireshark, and the Windows request has lots of more stuff (OPTION, and different stuff in some of the OPTION) than what the PFSENSE-request has... So, any idés of how to solve this? The problem is that sometimes the 255.255.255.255 request after 2x450 secs gives me a new IP, or, does not work at all, so that I manually has to go into the pfsense webinterface and renew the ip :( this is what pfsense looks like: ( i tried to add as much as I could to the dhcpd-conf file, but it´s still not enough) http://basse.host22.com/junk/greenshot_2009-11-28_09-53-02.png and windows: http://basse.host22.com/junk/greenshot_2009-11-28_09-52-46.png Any help would be really appreciated! update: I tried the 2.0 alpha, and it worked great! Any ETA on a stable 2.0? :P I will try to capture these updates also, and see how they differ from the current stable pfsense updates...

The question is simple: how does dynamic dns (RFC2136) work in pfsense? Thanks!

@Perry: http://doc.pfsense.org/index.php/File:SplitDNS-forwarder-example.png exactly thats what i wanted. i have solved it now. thanks a lot :)

@DWAyotte: I was wondering if anyone has been able to setup their own dyndns server and what exactly are you using? I had to write my own. There are a few open source implementations that are either broken or do not support the dyndns protocol. I was wanting to add an updater option in pfSense that would allow dyndns protocol updates to any custom server. I'm not sure if there would be any demand for something like this.

I see. But giving a name to the LAN2 interface doesn't do the trick. I think that this comes from the interface of pfsense not being recognized as a DNS, or maybe the DNS configured in the general setup aren't being forwarded on LAN2… Otherwise, whether or not i am able to access the interface through a hostname, I should be able to access the Internet from LAN2 when using the interface IP as DNS.

Funny thing is this has never happened on my linksys WRT54GL with dd-wrt that I was using prior installing pfSense/Alix. Anyway, [SOLVED].

post 'em and maybe we will?

@covex: […]or maybe a pfSense book?  ;D It's coming. Should be available for ordering within the next week or two. :)

I suppose I could have edited the config.xml file directly, but because PFSense does not seem to handle MX records correctly (I need my web server to send e-mail to my e-mail server!), I was forced to override the entire domain, and setup a new DNS server. I was able to delete all the overridden DNS records, including the ones with underscores, and now I can revert util.inc back to normal.

jimp - I have opened a bug. I still may not be able to get this working after all.  I can use "dig" to do a test zone transfer, but BIND 9.3 can't slave the zone.  I think I read something about a bug in BIND that axfrdns can't/won't cope with that causes the zone transfers to fail. At this point I'm thinking of giving up on tinydns and installing BIND using pkg_add.

sounds like a bug in the netgear firmware.

ok, it would be nice if the indication was corect so one could use that page to actually see on which interface the host is active, but maybe this was something of a 'special case' where the host had been active on different nets. But still, not something unique I think.