Project

General

Profile

Actions

Bug #106

closed

1.2.3-RC2 - NanoBSD - Dynamic DNS Updates (DynDNS.org)

Added by Christian Bendl over 14 years ago. Updated almost 14 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
10/02/2009
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
1.2.3
Affected Architecture:

Description

Updates with a cached ip seem not to work properly after
a line hard reset (by ISP or manually).
My ISP deconnects PPPoE connections every 24 h,
the dyndns update script logs a positive update
after the connection is established again.
After that no VPN connection are working, because
the IP was never "really" updated.

Resolve attemp #1:
Get to the DynDNS config pane and click
the save button to clear my cached ip and get the update
working again.

Could it be some problem with DNS name resolution after this
kind of "hard" reset?!

Probably i take a look into it myself, if i got any free time this week..

Actions #1

Updated by Scott Ullrich over 14 years ago

Please try 1.2.3-RC3. A linkup bug was fixed where the various processes would not invoke after unplugging or plugging in a NIC.

Actions #2

Updated by Scott Ullrich over 14 years ago

  • Status changed from New to Feedback
Actions #3

Updated by Aarno Aukia about 14 years ago

The OP didn't mention whether he was using dyndns or rfc2136 updates.
On 1.2.3 the update of rfc2136 dyndns is missing from /etc/rc.dyndns.update, where services_dnsupdate_process() should be called in addition to services_dyndns_configure().
sullrich: can you add this ?

Actions #4

Updated by Chris Buechler almost 14 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF