This has been a very interesting problem that we are continually trying to fix. Since there isn't anyone on the development team that has PPPoE it has been a slow process. I use DynDNS personally (however I am not using a PPPoE connection) and DynDNS is working very well for me. My pfSense install just did a successful update to my DynDNS yesterday, I even checked my account to make sure.
I made a change to the dyndns.class that resides in the /etc/inc directory yesterday or the day before. Make sure you have the lastest of that file on your system and try seeing if you can get it to update. If it does not work please get the contents of /var/etc/dyndns.debug AND /var/etc/dyndns.cache and paste them in a response to this message. I have added some extra debugging to help figure this problem out. Regards. -Erik On Mon, 12 Sep 2005 16:56:57 +0200, Frimmel, Ivan \(ISS South Africa\) wrote > Running 0.84 Dyndns(dynamic) seems to still be flaky .. last week I > registered a custom dns with dnydns .. and it works 100% of the > time. I have one router setup with one PPPoE dialout and another set > with a different one. > > > > I "load balanance" incoming traffic by giving half of the people I meet > one dyndns address which the one machine registers, and the other > half the other dnydns ( custom ). > > > > SO : The custom dyndns is always upto date.. the dynamic one is a > problem. But only recently .. I think from around 0.82 Its been > unreliable. My IP gets changed every 24-48 hours and the problem is > because I have multiple outbounds so I can't use a update client > cause it won't know which gateway to use. > > > > Updating the dyndns (dynamic) setting manually gives me: > > Sep 12 16:26:01 > > php: /services_dyndns.php: phpDynDNS: No Change In My IP Address and/or > 28 Days Has Not Past. Not Updating Dynamic DNS Entry. > > > > Dynamic DNS client > > Enable > > Service type > > DynDNS (dynamic) DynDNS (static) DynDNS (custom) DHS DyNS HN.ORG > ZoneEdit easyDNS No-IP ODS.org > > Hostname > > MX > > Set this option only if you need a special MX record. Not all > services support this. > > Wildcards > > Enable Wildcard > > Username > > Password > > > > > > > > Doing a reboot doesn't help either - only way is to do it manually by > going to the dyndns page and putting in WAN IP. > > > > Which I did on Friday .. played a bit now and this is the date I get > of my last update: > > IP in Database/DNS: 165.165.217.60 Last Updated: Fri Sep 9 11:17:28 2005 > > > > Looking at my DynDns account I notice that my wildcard is set to ON > on PF and OFF on dynDns .. I wonder if this can be the cause ? Need > to do some more testing locally... > > > > > > Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
