Project

General

Profile

Actions
Copy link

Feature #7321

closed

DynDNS - Add DreamHost DNS support

Added by Frank Gruman over 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Dynamic DNS
Target version:
2.4.0
Start date:
02/26/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

I have been a customer of DreamHost (https://www.dreamhost.com/) for many years with several domains and subdomains. I have always used a PC with a custom script to maintain DNS domains that pointed back to the customer sites. I have finally gotten fed up with that solution and have extended the Dynamic DNS solution to support DreamHost DNS.

Please consider accepting Pull Request 3579 (https://github.com/pfsense/pfsense/pull/3579) to support the addition of DreamHost Dynamic DNS.

In implementing this I did add some additional methods to the dyndns.class file to support lookup and remove operations. This is because DreamHost does not perform a direct DNS record update but rather a remove and an add. The remove must be done with data that matches an existing record and thus the lookup was necessary since the dyndns module does not seem to have access to the old interface address.

Actions
Copy link
 #1

Updated by Jim Thompson over 7 years ago

  • Assignee set to Renato Botelho
Actions
Copy link
 #2

Updated by Jim Thompson over 7 years ago

will need a signed CLA prior to integration.

Actions
Copy link
 #3

Updated by Frank Gruman over 7 years ago

The Pull Request should show that I have already completed the CLA. Is there a separate one that I need to complete?

Actions
Copy link
 #4

Updated by Jim Thompson over 7 years ago

Whoops... I completely missed that the second red flag "CLA Missing" was a reversal.

Actions
Copy link
 #5

Updated by Corey Boyle over 7 years ago

Any progress on this? I'd love to use it. Looking at the possibility of combining this with the acme and haproxy packages.

Actions
Copy link
 #6

Updated by Frank Gruman about 7 years ago

I'm pretty interested in finally seeing this delivered. The pull request was accepted into master 5 months ago. Is there any specific reason it has still not been delivered or tagged for inclusion in a release?

Actions
Copy link
 #7

Updated by Kill Bill about 7 years ago

Frank Gruman wrote:

I'm pretty interested in finally seeing this delivered. The pull request was accepted into master 5 months ago. Is there any specific reason it has still not been delivered or tagged for inclusion in a release?

It's already included in 2.4.x, not really sure what else are you requesting.

Actions
Copy link
 #8

Updated by Frank Gruman about 7 years ago

OK - I do see that it made it into the 2.4.0 Git branch. I didn't see it listed at https://redmine.pfsense.org/versions/25 or https://redmine.pfsense.org/versions/34 and this ticket was never updated to include a target version. I was waiting to see it added somewhere as a sign that it had made it out.

So - I guess it's just a matter of either jumping into the RC stream or waiting for the final release of 2.4.0.

Actions
Copy link
 #9

Updated by Renato Botelho about 7 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #10

Updated by Jim Pingle about 7 years ago

  • Project changed from pfSense Packages to pfSense
  • Category set to Dynamic DNS
  • Target version set to 2.4.0
  • % Done changed from 0 to 100
Actions
Copy link
 #11

Updated by Corey Boyle almost 7 years ago

I tried to set this up today, but did not have any luck. I selected "Verbose" logging, but I'm not sure where to find the logs. Is this working for anyone else?

Actions
Copy link
 #12

Updated by Frank Gruman almost 7 years ago

The logs should appear under Status > System Logs under the "General" section. Most of the log entries will start with "rc.dyndns". I've got this running on 4 separate routers without any hitches so hopefully the log will give you the detail you need.

Actions
Copy link
 #13

Updated by Corey Boyle almost 7 years ago

Thanks so much! The logs helped me figure it out. I didn't realize I needed to create the record manually first. Seems obvious to me in retrospect. Is this able to set the TTL?

Actions
Copy link
 #15

Updated by Joshua Kugler almost 7 years ago

Corey Wicklund I saw your note about adding this to the ACME package. Were you able to do this? I did not see Dreamhost in the list of options of DNS providers. I would love to have it in the ACME package. Anything I can do to help on that front?

Actions
Copy link
 #16

Updated by Corey Boyle almost 7 years ago

Dreamhost is not an option in the ACME package. However, I was able to get around this by using the "standalone HTTP server" method and HAProxy. You can see the way I did it here...

https://forum.pfsense.org/index.php?topic=130598.msg727189#msg727189

Actions
Copy link

Also available in: Atom PDF