You need to stop and restart, not reload, dnsmasq to clear its cache.

And why would Lan have a gateway?  Do you have other lan networks that you need to get to?

The install does not even ask you for this - so why did you put it on?  What did you put in?  Pfsense own address?

It all worked! Just wanted to thank you.

I faced only one issue when DHCP did not update "reverse lookup zone" but it got fixed after specifying proper credentials for update account.

@mendilli:

does your access point act as a dhcp sever? if so it may deliver ip and you can not see it in pfsense. you must disable dhcp sever in access point.

Thanks for your reply; appreciated  ;D

No, it doesn't, I checked. More over, even if it would, it would be strange that it, by accident, would give it the next in line number (x.x.2.14) which happens to be the 'old' fixed ip-nummer that it had before (?)

if you give static ip to a network device there is nothing wrong when you can not see it in dhcp leases, dhcp sever shows only the ip's that it is delivering

This I didn't understand. If I tell Pfsense to give out a static IP I would see it in the DHCP/status, no?

because something got stuck and system thought it was running because of the pid file, when it really wasnt.  Did you have a power outage or something?

So you cleared up the old pid, now if you look there is a new pid file - if you view the contents of the file with cat it will show you a number – the pid..  As you stop and start the service this number will change.

If something wrong with the file, or it has a pid number of a running process that is not dhcpd - system can think dhcpd is already running, etc.

deleting it just allowed whatever the snafu was to get cleared up.

@jcyr:

In the current pfSense bind implementation the static dhcp mappings are only added the zone at the time the zone is saved.

Exactly!

I wonder if any dev is actually reading this forum …  :-\

"I have 4 rules added: tcp 25 outbound only by my mailserver disabled for all others. same for port 465. last rule is allow LAN to any rule."

Lets see these rules - because the way you describe them, they are not going to work if your last rule is an allow all.

So you have pointing to itself with the 127.0.0.1 entry - are you running the dns forwarder?  If not what is running on pfsense to resolve, so 127 is should not be there.

If your not running the forwarder, then you should put a check next to the box that says
Do not use the DNS Forwarder as a DNS server for the firewall

And that 127 entry should go away.

Thank you both for your helpful replies! I totally agree it seems like a rogue NAT-router has been set up somewhere, because the portal I'm taken too when I get an IP in the wrong range is equal to the login-page of one of the popular ISP residential NAT-routers.

The switches are manageable, so i should be able to track down the router, but "unfortunately" it seems it has been taken off the network again - I haven't been able to get connected to the wrong IP-range since i posted the message. Though it's good the problem has apparently been solved, it would have been nice to catch the router after months of annoyance :)

Anyway, now I know how to handle it the next time someone plugs in a NAT-router, so thank you both!

Rune

Im confused on this network setup..  So 192.168.5  and 192.168.1 are the same broadcast domain?  What mask are you using?  In a normal setup these 2 segments would be different, and should not be possible broadcast to the other network for dhcp.

How are your networks connected?

I now have this working. Here are the steps I took.

1. Install TinyDNS (System -> Packages -> Available Packages -> Install dns-server)

2. Added new domain to Tiny DNS (Services -> DNS Server -> New domain wizard)
During this step, I added my domain (foo.com) with a number of initial hosts

3. Configure Tiny DNS (Services -> DNS Server -> Settings)
I set the following:

Enable recursive DNS responder: Disabled
IP Address: 127.0.0.1
Interface to listen: loopback

I left all other settings as default

4. Configured DNS Forwarder (Services -> DNS Forwarder)
Enable DNS forwarder: selected
Interfaces: LAN

5. Added domain to overwride (Services -> DNS Forwarder -> add Domain Override near bottom of page)
Settings here are

Domain: foo.com
IP address: 127.0.0.1

6. Ensure that your ISP's DNS servers (or whichever servers you want to forward to) are configured under System -> General Setup

This is now working. All requests for my domain are handled by TinyDNS and everything outside my domain is handled by the forwarder.

Replace /etc/inc/services.inc and /usr/local/www/services_dhcp.php with the following. Not 100% sure that it works properly in practice, but it definitely leaves the routers option out of your DHCP config. To use, type "none" without quotes in the gateway field.

services.inc
services_dhcp.php

It was noticed a few times, we put a fix into the tree for it, 2.1.1 will find that and move it back where it belongs

General curious question for you - why don't you point your clients both vpn and local to pfsense.. This way you can resolve your local network hosts, etc.  pointing to outside dns seems counter productive if you want to resolve anything on your own network.

This is normally handled by DNS services on the network. If you are not using pfSense as your DNS server, then you will need to add pfsense DNS entry into this server to be able to ping my name. If you are using pfSense as your DNS server, then just set up hostname and domain name in general tab and it should resolve for you.

I'll try that but I think I may have found another issue.

I tried to edit see what the resolv.conf file was set to in shell and the file itself is a symbolic link pointing no where. If I try to edit it or remove it to create a new one, it tells me it's a read only file system.