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.

I figured out how to fix pfSense and I posted in your thread:

http://forum.pfsense.org/index.php/topic,19828.msg102564.html#msg102564

hi,

i was browsing thru the forums and stumbled upon this thread, which currently  the same situation im facing now… i have two internal network (LAN and LAN2) and would want to have a separate domain suffixes for the internal network e.g. LAN=mycompany.com, LAN2=myothercompany.com. i installed Fit123 package and tried the suggestions mentioned above, but no luck...

anyone have ideas about this? thanks in advance...

alli

@GruensFroeschli:

Then how should LAN1 users resolve names when WAN2 is down?

If that happens, Internet will go down anyway. Therefore I just have to change the rules of the firewall to route the packets through the last gateway available and then try to resolve the problem.

@GruensFroeschli:

IMO the "correct" way to do this is:
Set on the pfSense as primary and secondary DNS entry: 208.67.222.222 and 208.67.220.220
Like this all requests go to WAN1.
Then create a static route for 208.67.220.220 pointing to WAN2.
Like this all requests go to WAN1, and when WAN1 is down all requests go to WAN2.

That's pretty much like the loadbalancing. I was interested in this method. But i'm not supposed to do something like that.

@GruensFroeschli:

If you want that users resolve names over different WANs depending on in which LAN they are you have to stop using the DNS-forwarder and set the DNS entries on the clients direct (DHCP or static).

The fact is, I've opened access for LAN to WAN2 Network (Just for the local network, and not to access the Internet) which is why i used both WAN and WAN2 modem's addresses as global DNS. LAN Users have the IP address of pfsense as DNS, whereas LAN2 users have a static address: the address of the WAN2 modem.
This seems to do the trick.

same problem here DHCP enable on LAN and OPT1 DHCP not working…

@ZaInT:

The Fit123 package actually seemed like exactly what I need, but I just can't get it to write /usr/local/pkg/Fit123/ddns/ddns.php, no matter what I do to the file system.

Have you tried running: /etc/rc.conf_mount_rw
before setting up Fit123?
Just a guess that the file system you are trying to write to is still read-only… it's still embedded.

Yeah, you're right.  Editing /etc/resolv.conf is not the right way.

Nevermind this, i forgot the windows world..

I rebooted and it worked again >_<

@mgiammarco:

… or if I have to copy them by hand.

You could always backup the "DHCP Server" area on the "Diagnostics: Backup/restore" page, modify the "Failover peer IP", then restore that into the failover pfSense.