Project

General

Profile

Actions
Copy link

Bug #3166

open

EC2 vpc subnets dont get dns smart-proxy

Added by Brian Galura about 11 years ago. Updated almost 11 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Network
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

This means my EC2 instances dont get the expected reverse DNS.

Actions
Copy link
 #1

Updated by Dominic Cleal about 11 years ago

  • Category set to Network
  • Target version deleted (1.3.0)

We could perhaps do this by matching network addresses between VPC subnets and preconfigured subnets during host creation on the fly, but better would be a proper association between EC2 / compute resource subnets and our subnets.

Actions
Copy link
 #2

Updated by Brian Galura about 11 years ago

With Dominic's suggestion I have a workaround using foreman_hooks. Ive posted a blog about it here http://digital-ducttape.com/2013/10/23/aws-vpc-buildout-with-foreman_hooks-for-rdns-creation/

Actions
Copy link

Also available in: Atom PDF