Project

General

Profile

Bug #3166

EC2 vpc subnets dont get dns smart-proxy

Added by Brian Galura about 8 years ago. Updated over 7 years ago.

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

Description

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

History

#1 Updated by Dominic Cleal about 8 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.

#2 Updated by Brian Galura almost 8 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/

Also available in: Atom PDF