[prev in list] [next in list] [prev in thread] [next in thread]
List: pfsense-dev
Subject: [pfS-Dev] DynDNS issues
From: erik () erikkristensen ! com (Erik Kristensen)
Date: 2011-11-30 14:56:14
Message-ID: 937D97E8-5953-480E-A091-8B8083B13AD1 () erikkristensen ! com
[Download RAW message or body]
The problem is that isn't a good and normal error ? that error mean something went \
wrong on the server side (i.e. dyn's side) and their API docs specifically say to \
contact them.
If it were any of the other errors that they list out in the api docs then it would \
be easier to handle.
-Erik
On Nov 30, 2011, at 9:50 AM, Fuchs, Martin wrote:
> Then we should perhaps wait 30 minutes ;-)
>
> Thanks, holger ;-)
>
> Regards,
>
> martin
>
> -----Urspr?ngliche Nachricht-----
> Von: dev-bounces at lists.pfsense.org [mailto:dev-bounces at lists.pfsense.org] Im \
> Auftrag von Holger Bauer
> Gesendet: Mittwoch, 30. November 2011 15:40
> An: pfSense development mailing list
> Betreff: Re: [pfS-Dev] DynDNS issues
>
> > From their API:
>
> http://dyn.com/support/developers/api/return-codes/
> The client ***must*** not resume updating until 30 minutes have passed or user \
> confirms that the problem has been resolved.
> I don't know if they start blocking your account if you retry it all over in 30 \
> second delays for abuse.
> Holger
>
>
> 2011/11/30 Fuchs, Martin <martin.fuchs at trendchiller.com>:
> > ;-)
> > Is it very complex to implement a function to retry the actualization after 30 \
> > seconds of the account if the previous was not successful (marked as red) ?
> > Regards,
> >
> > martin
> >
> > -----Urspr?ngliche Nachricht-----
> > Von: dev-bounces at lists.pfsense.org
> > [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Erik Kristensen
> > Gesendet: Mittwoch, 30. November 2011 12:27
> > An: pfSense development mailing list
> > Betreff: Re: [pfS-Dev] DynDNS issues
> >
> > Hrm . I'll take a look at the the code again.
> >
> > -Erik
> >
> >
> > On Nov 30, 2011, at 6:20 AM, Fuchs, Martin wrote:
> >
> > > There's no way to contact dyn for rhat until you have a pro account
> > > > -(
> > >
> > > After this error was gone for a while on multiple systems it seems as
> > > if it returns on most of them :-( Manual "saving" in dyndns-updater
> > > on pfsense solves the error until the next time :-(
> > >
> > > Regards,
> > >
> > > martin
> > >
> > > -----Urspr?ngliche Nachricht-----
> > > Von: dev-bounces at lists.pfsense.org
> > > [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Erik Kristensen
> > > Gesendet: Sonntag, 27. November 2011 01:26
> > > An: pfSense development mailing list
> > > Betreff: Re: [pfS-Dev] DynDNS issues
> > >
> > > Martin,
> > >
> > > Are you still getting the error dnserr as the response?
> > >
> > > You'll need to contact dyndns.org regarding your account and hostnames to find \
> > > out what is wrong. Thats what their api says to do, its the dyndns server side \
> > > that is throwing the error.
> > > -Erik
> > >
> > > On Nov 26, 2011, at 4:48 PM, Fuchs, Martin wrote:
> > >
> > > > So what can we do... ?
> > > > When this error occurs the current ip is printed in red and not green, so \
> > > > pfsense seems to know about the fact that the update was not successful... \
> > > > Can we build in a delay for 15 minutes or else to retry "until ip is printed \
> > > > in green" ;-)
> > > > -----Urspr?ngliche Nachricht-----
> > > > Von: dev-bounces at lists.pfsense.org
> > > > [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Erik
> > > > Kristensen
> > > > Gesendet: Montag, 21. November 2011 16:02
> > > > An: pfSense development mailing list
> > > > Betreff: Re: [pfS-Dev] DynDNS issues
> > > >
> > > > Hey guys,
> > > >
> > > > Martin, interesting error . according to the dyndns api return codes \
> > > > (http://dyn.com/support/developers/api/return-codes/) an DNS error was \
> > > > encountered. Unfortunately that isn't very clear. However they do recommend \
> > > > the following if that error occurs ...
> > > > The codes below indicate server errors that will have to be investigated. The \
> > > > client must stop updating and ask the user to contact Dyn support. The client \
> > > > must not resume updating until 30 minutes have passed or user confirms that \
> > > > the problem has been resolved.
> > > > -Erik
> > > >
> > > > On Nov 21, 2011, at 8:40 AM, Holger Bauer wrote:
> > > >
> > > > > I have a bunch of systems, that show that as well. Most of them are
> > > > > still 1.2.3 so it's not a 2.0 specific issues. Those systems were
> > > > > running fine for years and all started to show the same in the logs
> > > > > several weeks/months ago. As we have ISP forced 24h disconnects
> > > > > here in germany you usually notice such an error rather quick. I
> > > > > think something has changed on the DynDNS-Provider end. I also have
> > > > > some reports from colleagues that see the same failures in updating
> > > > > the IP on completely different routers. Maybe someone could get in
> > > > > contact and ask if something has changed and what to do to handle
> > > > > that failure in a proper way so they don't take down the account
> > > > > for abuse when retrying updates all over again?
> > > > >
> > > > > Holger
> > > > >
> > > > > 2011/11/21 Fuchs, Martin <martin.fuchs at trendchiller.com>:
> > > > > > Hi !
> > > > > > Here's another one again...
> > > > > > Dyndns again, too...
> > > > > > I am really wondering what this payload error means...
> > > > > >
> > > > > > Nov 21 03:00:19 php: : phpDynDNS: (Unknown Response) Nov 21
> > > > > > 03:00:19
> > > > > > php: : phpDynDNS: PAYLOAD: dnserr Nov 21 03:00:19 php: : DynDns:
> > > > > > Current Service: dyndns Nov 21 03:00:19 php: : DynDns: DynDns
> > > > > > _checkStatus() starting.
> > > > > > Nov 21 03:00:18 php: : DynDns: DynDns _update() starting.
> > > > > > Nov 21 03:00:18 php: : DynDns debug information: DynDns: cacheIP
> > > > > > != wan_ip. Updating. Cached IP: 46.142.32.24 WAN IP: 46.142.47.241
> > > > > > Nov
> > > > > > 21 03:00:18 php: : DynDns: Current WAN IP: 46.142.47.241 Cached IP: \
> > > > > > 46.142.32.24 Nov 21 03:00:18 php: : DynDns debug information: \
> > > > > > 46.142.47.241 extracted from local system. Nov 21 03:00:18 php: : DynDns: \
> > > > > > updatedns() starting
> > > > > > Regards,
> > > > > > Martin
> > > > > >
> > > > > > -----Urspr?ngliche Nachricht-----
> > > > > > Von: dev-bounces at lists.pfsense.org
> > > > > > [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Fuchs,
> > > > > > Martin
> > > > > > Gesendet: Mittwoch, 5. Oktober 2011 16:40
> > > > > > An: pfSense development mailing list
> > > > > > Betreff: Re: [pfS-Dev] DynDNS issues
> > > > > >
> > > > > > You're lucky ;-)
> > > > > >
> > > > > > Am 05.10.2011 um 15:22 schrieb "Jim Pingle" <lists at pingle.org>:
> > > > > >
> > > > > > > On 10/5/2011 8:40 AM, Erik Kristensen wrote:
> > > > > > > > I wonder if DynDns change their API.
> > > > > > > >
> > > > > > > > Are you using DynDNS? I am.
> > > > > > > >
> > > > > > > > Maybe that is the common denominator.
> > > > > > > >
> > > > > > > > Anyone else doing Dynamic DNS? Is it working for you? What provider?
> > > > > > >
> > > > > > > I have two entries with DynDNS, one with Namecheap, and two
> > > > > > > he.net tunnelbroker DynDNS entries (on 2.1). They all work every
> > > > > > > time without issue. Everything comes up green every time my IP changes.
> > > > > > > (Which is unfortunately often these days)
> > > > > > >
> > > > > > > Jim
> > > > > > > _______________________________________________
> > > > > > > Dev mailing list
> > > > > > > Dev at lists.pfsense.org
> > > > > > > http://lists.pfsense.org/mailman/listinfo/dev
> > > > > > >
> > > > > > _______________________________________________
> > > > > > Dev mailing list
> > > > > > Dev at lists.pfsense.org
> > > > > > http://lists.pfsense.org/mailman/listinfo/dev
> > > > > >
> > > > > > _______________________________________________
> > > > > > Dev mailing list
> > > > > > Dev at lists.pfsense.org
> > > > > > http://lists.pfsense.org/mailman/listinfo/dev
> > > > > >
> > > > > _______________________________________________
> > > > > Dev mailing list
> > > > > Dev at lists.pfsense.org
> > > > > http://lists.pfsense.org/mailman/listinfo/dev
> > > >
> > > > _______________________________________________
> > > > Dev mailing list
> > > > Dev at lists.pfsense.org
> > > > http://lists.pfsense.org/mailman/listinfo/dev
> > > >
> > > > _______________________________________________
> > > > Dev mailing list
> > > > Dev at lists.pfsense.org
> > > > http://lists.pfsense.org/mailman/listinfo/dev
> > >
> > > _______________________________________________
> > > Dev mailing list
> > > Dev at lists.pfsense.org
> > > http://lists.pfsense.org/mailman/listinfo/dev
> > >
> > > _______________________________________________
> > > Dev mailing list
> > > Dev at lists.pfsense.org
> > > http://lists.pfsense.org/mailman/listinfo/dev
> >
> > _______________________________________________
> > Dev mailing list
> > Dev at lists.pfsense.org
> > http://lists.pfsense.org/mailman/listinfo/dev
> >
> > _______________________________________________
> > Dev mailing list
> > Dev at lists.pfsense.org
> > http://lists.pfsense.org/mailman/listinfo/dev
> >
> _______________________________________________
> Dev mailing list
> Dev at lists.pfsense.org
> http://lists.pfsense.org/mailman/listinfo/dev
>
> _______________________________________________
> Dev mailing list
> Dev at lists.pfsense.org
> http://lists.pfsense.org/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic