This feature will come AFTER the next release in the available snapshots…
For now have a look at pfsense.trendchiller.com and update manually…
Patches are already applied to cvs: ticket 19228 and 19229
so please be patient...

hi again

i have a problem now, msn messenger cant sing in on my client's pc's, how to fix this?

help is apreciated

simply create a php file and put it on public webserver (with php support) :

echo $_SERVER[REMOTE_ADDR]; ?>

And modify : /etc/inc/dyndns.class
Replace this :

$wan_ip = get_current_wan_address();

By this :

$filename = "HTTP://YOUR_WEBSERVER_URL/YOUR_FILE.PHP"; $handle = fopen ($filename, "r"); $wan_ip = fread ($handle, 20); fclose ($handle);

If you want, you can create a function with this code and call it (do not forget the  "return;" at the end of function).

It helps,
Thank you very mutch!  :)

It should automatically resolve hostnames if the DHCP server is enabled for an interface.  You can also add custom entries in Services -> DNS Forwarder.

http://osdir.com/ml/network.dns.dnsmasq.general/2006-10/msg00002.html

seems that it can be done with local

release version 2.39 is out as a side note

It sounds like in this case your modem has your public IP, and pfsense has a private IP on its WAN and its default gateway is the modem, is that correct?

I update by now to the new snapshot and everything works as expected: DHCP works also in bridged mode, and I get only a warning in the system logs, that DHCP is enable while in bridge mode. Hence, it works fine.

Thanks again!!

Best regards
Arno

PS: Better workarround for this would be to check if DHCP is enabled on both interfaces of an bridge; in such a case it woul be usefull to deactivate on instance - implementing this would accomplish also the wishes of the other thread through which this situation was introduced.

We cannot go back to ISC's client as we utilize multiple wans.

This thread is far too old.  Closing.

SOA records should point to a DNS name.  Then you need a A record with the DNS name of the dns server to resolve to.

Example:

domain.com  SOA    ns.domain.com 
domain.com SOA ns2.domain.comm
ns.domain.com      A    XXX.XXX.XXX.XXX
ns2.domain.com    A    XXX.XXX.XXX.XXX
www.domain.com  A            XXX.XXX.XXX.XXX

Hi Sunny,

I'll look into it when I get back to the office. Thanks for your advice and thanks to everyone for their input.

Keith

I have the DNS forwarder for the domain enabled as well with no luck.  This did work fine in previous snapshots btw.  No biggie for me, though.  Just wanted to help others out.

now these openvpn-options can be set up without using the custom parameters

duh, thanks.

I didn't have the opt enabled yet.

I'd suggest using the DC to provide DHCP and DNS to your clients. That way your DC always has current listings of your internal clients IPs. It will make your life easier and more secure.

I'd setup the internal network on a different domain then your public one. However if you've already setup the windows domain that is much easier said then done. At any rate, I'd register the domain you use internally just so no one else does, it could bite you in the butt in the future if you have road warriors, well worth $10/year

I'd setup the public DNS on a *nic system, either pfsense or other in a DMZ preferably.

You do NOT want your windows domain dns to be accessible from the outside world. But if they are the same domain name then just setup the *nix box and the Windows box both with the SOA. Your public one will be the one with real authority, but you DC must believe that it does as well. Your clients will believe your DC's DNS no matter what.

You can use DNS tricks on your DC to point to the internal IP of the webserver too, this will take the traffic off your internet connection, otherwise it may route out to the internet and then back to you.

Hope this helps.

Don't think i know what you mean with dmz pool limit. But you define all the rules.
this might help you out
http://doc.m0n0.ch/handbook/examples.html

Don't bother…..

Just use the pFSense for one DynDNS.....

And install the DynDns-client on one of your servers (you must be having at least one, that why you are using DynDNS) - and feed it all you other DynDNS IP's.... It will detect the WAN IP just fine, even when you consider that it's running on PC on your internal network.

For for me for month now.

TQ is work…. you are the best.... :D :D :D