Project

General

Profile

Actions
Copy link

Bug #6153

closed
KB JP

RFC 2136 Client fails to update more than 1 record

Bug #6153: RFC 2136 Client fails to update more than 1 record

Added by Ken Bass over 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Dynamic DNS
Target version:
2.3.3
Start date:
04/14/2016
Due date:
% Done:

100%

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

Description

I added a single RFC 2186 Client (name1.mydomain.com) and verified it worked. DNS was updated and 'cached IP' was green.
I then added an additional entry (name2.mydomain.com), all other parameters the same. It did not work - client page showed N/A.

System log shows 'Not updating name1.mydomain.com A record because the IP address has not changed'
System log shows 'Not updating name2.mydomain.com A record because the IP address has not changed'

Edited entry and presses 'Force and Save update' - same problem.
Manually ran rc.dyndns.update - same problem and log message.

There was only a single /conf/dyndns_wan_rfc2136_'name1.mydomain.com'_ns.mydomain.com.cache
I had to delete that file (note: there was no name2 file). Then it worked.

JT Updated by Jim Thompson over 10 years ago Actions
Copy link
 #1

  • Assignee set to Chris Buechler

CB Updated by Chris Buechler about 10 years ago Actions
Copy link
 #2

  • Category set to Dynamic DNS
  • Status changed from New to Confirmed
  • Assignee deleted (Chris Buechler)
  • Target version set to 2.4.0
  • Affected Version changed from 2.3 to All

RB Updated by Renato Botelho over 9 years ago Actions
Copy link
 #3

  • Subject changed from RFC 2186 Client fails to update more than 1 record to RFC 2136 Client fails to update more than 1 record

RB Updated by Renato Botelho over 9 years ago Actions
Copy link
 #4

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:ed680fda05f2d2d17a59d2893a6ae45e0cbef164.

RB Updated by Renato Botelho over 9 years ago Actions
Copy link
 #5

  • Assignee set to Jim Pingle

Pingle has a way to validate the changes

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #6

  • Status changed from Feedback to Resolved

Works for me. Two RFC2136 entries on WAN both get updated now. I wiped the cache files and tested using /etc/rc.dyndns.update and both entries are processed.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #7

  • Target version changed from 2.4.0 to 2.3.3
Actions
Copy link

Also available in: Atom