Thanks for the pointer to dns-server.  Perhaps that will do the job.

tested it out, it works thanks alot

Any news on this?

@jahonix: Have those machines been assigned a DHCP lease dynamically from the pool before the MAC got a static mapping (with a different IP? I have the exact same messages in my log, and I think that I also assigned a dynamic address to the device before it got a static one. I've tried to remove it from the lease file, restarting the DHCP server, but nothing seems to work. How do you solve this? [edit] I should've looked a bit more carefully on the forum, the solution is in this thread: [/edit]

5 days since I upgraded to 1.2RC4 …  All of sudden today, my pfsense box stop responding. At the console, I see this message repeated: xl0:  connection watch dog time-out Tried to switch to another virtual console but nothing.  I hit the power button, pfsense started the shutdown process and power off. I boot the box again.  I did not setup remote syslog before therefore I couldn't see what had happen.  Remote syslog is now setup & I'll monitor the box... I found several threads regarding timeout issue under heavy load but that was a while back.  Not sure if that is the case here. note: xl0 is the LAN interface. edit: caught this in syslog Jan 23 14:22:16 kernel: xl0: tx underrun, increasing tx start threshold to 120 bytes Jan 23 14:22:16 kernel: xl0: transmission error: 90 edit2:  sorry, I shouldn't put this here. I will start a new post in hardware section.

if you edit /usr/local/www/diag_dhcp_leases.php there is a function in the middle that removes duplicates from the array. Try commenting that function out and see if the lease shows up then.

Click save on the settings tab.  I should have checked this out prior but it creates the user account any time you make changes to the settings or other areas of the DNS Server package.

http://devwiki.pfsense.org/SubmittingPatches

Setup remote syslogging.

hello nylan I've the same problem, when I connect my PC directly to the soekris box. The dhcp server gives me no new lease when I am connected to LAN port. After several times restarting my PC it worked. hope someone can help on this one. wfg     thorolf

Set a DNS server on the config page. Create a static route for the IP of the DNS server to the gateway you want it routed to.

In the Web GUI: System/General Setup In the DNS Servers section, check the "Allow DNS server list to be overridden by DHCP/PPP on WAN" Services/DNS Forwarder check the "Enable DNS Forwarder" checkbox The Note towards the bottom of the DNS Forwarder section explains it all Note: If the DNS forwarder is enabled, the DHCP service (if enabled) will automatically serve the LAN IP address as a DNS server to DHCP clients so they will use the forwarder. The DNS forwarder will use the DNS servers entered in System: General setup or those obtained via DHCP or PPP on WAN if the "Allow DNS server list to be overridden by DHCP/PPP on WAN" is checked. If you don't use that option (or if you use a static IP address on WAN), you must manually specify at least one DNS server on the System: General setup page.

OK, that is not problem.

@wallacebw: That was a bad attempt at comedy, not a solution. oh crap :D

Good suggestion! I've discovered that trying to describe network topography in text is a bit tricky Does this help? Basically, I have a separate DNS/DHCP server on one side and using PFsense for DHCP/DNS on the other, I'd like lookups to work across the two subnets. [image: 2125918920_c4700916df.jpg] In looking at this, it might be more confusing that I had planned. The text that is floating over the "LAN" machines on each side is meant to be a general description and has nothing to do with the machines it is floating over… I'm not so good at this

@hot_rene: ok, but how should resolve than the requests from outside to the inside hosts. I will have soom a server running 2003 in my DMZ serving as DNS. somehow the requests should go through it. any idea? 10x Its been a while, so I'm guessing this is resolved. I'm not sure about your specific setup, by typically I've seen 2 DNS servers. One for internal resolution and one for external. Personally, I let my registrar host my external stuff, but I dont have a lot going on. If you are going to host your external DNS using W2k3 in the DMZ, then its fairly simple. Put that box in the DMZ, forward UDP and TCP ports 53 through the NAT. Then configure the DNS with the external names and IPs… You'll have to notify your registrar of the static IP that you are natting to that DNS server as well.