Project

General

Profile

Actions
Copy link

Feature #1225

closed

AWS-Route53/Foreman/SmartProxy DNS integration

Added by Brian Gupta almost 13 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/smart-proxy/pull/262
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Now that Amazon has a DNS service we should integrate. http://aws.amazon.com/documentation/route53/

Files

route53.patch route53.patch 3.74 KB Daniel Maraio, 12/30/2011 06:02 PM

Related issues 2 (1 open — 1 closed)

Related to Foreman - Tracker #5409: DNS Proxy ImprovementsNew

Actions
Blocked by Smart Proxy - Feature #7008: Add providers to existing proxy modules from a plugin/moduleClosed08/09/2014Actions
Actions
Copy link
 #1

Updated by Brian Gupta almost 13 years ago

Please switch to Feature not bug.

Actions
Copy link
 #2

Updated by Daniel Maraio almost 13 years ago

Hey Guys,

I hamfisted route53 support in here by glueing together dns_api and the Route53 gem from https://github.com/pcorliss/ruby_route_53.

Its very basic but will do your forward and reverse dns with AWS. Should probably be an option to skip reverse DNS for a subnet, or use an alternate nameserver, as some organizations might not have their reverse delegated to them, especially if they have less than a /24.

To use, have your forward and reverse hosted zones already created. Then add the following to smart-proxy settings.yml, then point your domain to the smart-proxy.

:dns_backend: AWS
  :dns_aws_accesskey: yourkey
  :dns_aws_secretkey: yourkey

Use at your own risk, probably some bugs, its also ugly.

Actions
Copy link
 #3

Updated by Ohad Levy almost 13 years ago

awesome! thanks, one comment and another question:

  1. do you want to use a git patch (or a github pull) so you get the credit for it?
  2. would you mind adding a rescue LoadError, so it wont fail if you dont have the gem installed?

thanks!

Actions
Copy link
 #4

Updated by yziningyz yziningyz over 12 years ago

Spam removed by admin

Actions
Copy link
 #5

Updated by apoeleh apoeleh over 12 years ago

Spam removed by admin

Actions
Copy link
 #6

Updated by apoeleh apoeleh over 12 years ago

Spam removed by admin

Actions
Copy link
 #7

Updated by Benjamin Papillon almost 12 years ago

  • Tracker changed from Bug to Feature
  • Category set to DNS

Hello,

I switched the Tracker to Feature as user request.

Regards

Actions
Copy link
 #8

Updated by Stephen Benjamin over 10 years ago

Actions
Copy link
 #9

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/262 added
Actions
Copy link
 #10

Updated by Sol Cates over 9 years ago

I took the good starting point that Daniel Maraio had, and used the DNS Proxy Improvements framework from #5409 to create the feature in smart-proxy PR https://github.com/theforeman/smart-proxy/pull/262 . Thanks Daniel and the rest of the Foreman team for the hard work.

Actions
Copy link
 #11

Updated by Dominic Cleal about 9 years ago

  • Blocked by Feature #7008: Add providers to existing proxy modules from a plugin/module added
Actions
Copy link
 #12

Updated by Dominic Cleal about 9 years ago

  • Status changed from Ready For Testing to Resolved

Thanks to Daniel and Sol for their efforts and code. I've uploaded this into a new Smart Proxy plugin over at https://github.com/theforeman/smart_proxy_dns_route53, which is based on the brand new work in #7008.

It isn't released as a gem or package yet as there's a bit of work on the dependencies to sort out, but I hope to do that soon.

Actions
Copy link

Also available in: Atom PDF