I'm not sure I get your point. You always need to provide your IP address to the Dynamic DNS provider. If you don't, it will cease to be dynamic. The ways to do that vary. You can for example simply do a http request to some special page of your Dynamic DNS provider passing along your credentials and the page will automatically know your IP address, compare it with the stored one and eventually update it if there has been any change.
DynDNS does indeed provide with a mechanism to manually introduce an IP, but the problem here is the ability of pfSense to update this entry if the public IP address changes. Regarding the routing, I'm not sure what you mean. Holger has clearly stated that indeed the dynamic DNS service of pfSense only checks and updates the public IP address on the WAN interface and that in the future pfSense will get the functionality to choose the interface you want to update with this service. (Multiple dyndns clients updating different interfaces would be nice...) On the other hand, policy based routing of some traffic through one or the other interface can be controlled by adding a simple rule to the firewall. Regards, Stefan -----Mensaje original----- De: Bill Marquette [mailto:[EMAIL PROTECTED] Enviado el: lunes, 16 de octubre de 2006 21:27 Para: discussion@pfsense.com Asunto: Re: [pfSense-discussion] Dynamic DNS Some dyndns providers require us to supply an IP, some don't. I think DynDNS isn't one of those, but it does allow us to enter an IP, which we do - the only one we know. FWIW, traffic sourced from pfSense will always (for now) go out your primary WAN interface (the one with the default route), regardless of what policy routing says. --Bill On 10/16/06, Stefan Tunsch <[EMAIL PROTECTED]> wrote: > I'm talking about the integrated dyndns client. > > Luckily I installed the ADSL with the dynamic ip address on the WAN > interface... > > How can I report an IP other than the WAN IP? I understand that in > many situations my configuration is the one most people will use, > where there is a router between pfSense and the Internet. In this > scenario, reporting the WAN interface IP makes absolutely no sense. I > should be reporting the router's public IP. > > Of course, a solution might be to install the client software provided > by DynDNS on some other machine and route this traffic via an > appropriate firewall rule through my WAN interface. But doing it with > pfSense would be much cleaner. > > > Regards, Stefan > > > > -----Mensaje original----- > De: Holger Bauer [mailto:[EMAIL PROTECTED] Enviado el: lunes, > 16 de octubre de 2006 16:58 > Para: discussion@pfsense.com > Asunto: RE: [pfSense-discussion] Dynamic DNS > > The dyndns client only works at WAN interface and is always reporting > the WAN interface IP. We have code in the next version do dyndns per interface. > > Are you talking about the integrated dyndns client or a client that > is running inside your LAN on a workstation or server? > > Holger > -----Original Message----- > From: Stefan Tunsch [mailto:[EMAIL PROTECTED] > Sent: Monday, October 16, 2006 4:26 PM > To: discussion@pfsense.com > Subject: [pfSense-discussion] Dynamic DNS > > > Hi there! > > I recently set up my first pfSense firewall into production. > > I am using the load balancing feature. One of the two ADSL connections > I'm using has a dynamic IP address. The loadbalancing itself is > working fine, but I'm having trouble with the Dynamic DNS client set up. > > I have created an account with DynDNS and set up pfSense accordingly. > > The problem is that pfSense reports the IP address of the WAN > interface instead of providing the public IP of my router. > > The second issue is that I don't want to "balance" this url from one > interface to the other. I want to use just one of the WAN interfaces > I've set up. Curiously, pfSense always checks the same interface, > which is the one where I have dhcp set up between WAN and the router. > > > Any comments on this would be appreciated. > > regards. > > > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.408 / Virus Database: 268.13.4/476 - Release Date: > 14/10/2006 > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.408 / Virus Database: 268.13.4/476 - Release Date: > 14/10/2006 > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.408 / Virus Database: 268.13.4/476 - Release Date: > 14/10/2006 > > > -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.4/477 - Release Date: 16/10/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.4/477 - Release Date: 16/10/2006
