Project

General

Profile

Actions

Bug #6751

closed

Route53 DynDNS Problems / Replace Route53 DynDNS Module

Added by Jason McCormick over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Category:
Dynamic DNS
Target version:
Start date:
08/30/2016
Due date:
% Done:

100%

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

Description

With pfSense 2.3.2, the DynDNS system does not work with Amazon Route53 services. In looking through the logs and then the code to determine what my issue is, it appears that the pfSense support for Route53 was grafted in from a PHP module on Sourceforge that appears to be defunct. The r53.class module does not support most of the logging/checking system in dyndns.class which makes debugging very difficult. This issue being opened after discussions in 3973 and 6728. This issue aims to make available for discussion and hopeful inclusion new code that is written for pfSense to do basic DNS updates to Route53.

Actions #1

Updated by Jason McCormick over 7 years ago

Here is a diff against the current master for the change: https://github.com/pfsense/pfsense/compare/master...jxmx:6751_route53

I've tested this with creations and updates and so far everything appears to work.

Actions #2

Updated by Jim Pingle over 7 years ago

  • Target version changed from 2.3.2-p1 to 2.4.0
Actions #3

Updated by Jason McCormick over 7 years ago

Filed a pull request in Github

Actions #4

Updated by Jim Pingle over 7 years ago

Actions #5

Updated by Renato Botelho over 7 years ago

  • Assignee changed from Jason McCormick to Renato Botelho

PR has been merged, thanks!

Actions #6

Updated by Renato Botelho over 7 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #7

Updated by Jim Pingle about 7 years ago

  • Status changed from Feedback to Resolved

Tested Route53, it updates records properly now.

Actions #8

Updated by Jim Pingle about 7 years ago

  • Target version changed from 2.4.0 to 2.3.3
Actions #9

Updated by Jason McCormick about 7 years ago

If you are going to backport this to 2.3.3 Bug #7206 is also needed.

Actions

Also available in: Atom PDF