Project

General

Profile

Actions

Feature #17879

closed

Add DNS CNAME entry for nsupdate

Added by Guilherme Maluf Balzana over 7 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Category:
DNS
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

DNS managed by Foreman should be able to assign aliases for hosts.

Smart-proxy API currently support DNS CNAME entries for DNSCMD only.

This feature should able CNAME support on dnsupdate DNS provider and make it possible to assign more then one CNAME to a host1.

Issues related with this subject
#14091 #9388 #1581 #15244

1 https://github.com/theforeman/smart-proxy/blob/develop/modules/dns_common/dns_common.rb#L108


Related issues 3 (0 open3 closed)

Related to Smart Proxy - Refactor #17906: Move create_*_record remove_*_record functions into dns_commonClosedEwoud Kohl van Wijngaarden01/03/2017Actions
Blocks Smart Proxy - Refactor #17880: DNS CNAME parameters methods are swappedRejectedGuilherme Maluf Balzana12/29/2016Actions
Copied from Foreman - Feature #17878: Add DNS CNAME entry for nsupdateRejectedGuilherme Maluf Balzana12/29/2016Actions
Actions #1

Updated by Guilherme Maluf Balzana over 7 years ago

Actions #2

Updated by The Foreman Bot over 7 years ago

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

Updated by Guilherme Maluf Balzana over 7 years ago

  • Related to Refactor #17880: DNS CNAME parameters methods are swapped added
Actions #4

Updated by Guilherme Maluf Balzana over 7 years ago

  • Related to deleted (Refactor #17880: DNS CNAME parameters methods are swapped)
Actions #5

Updated by Guilherme Maluf Balzana over 7 years ago

Actions #6

Updated by Anonymous over 7 years ago

  • Related to Refactor #17906: Move create_*_record remove_*_record functions into dns_common added
Actions #7

Updated by Anonymous over 7 years ago

  • Status changed from Ready For Testing to Rejected

Closing this in favour of http://projects.theforeman.org/issues/17906 which provides default implementations for all create and delete record methods for all providers.

Actions #8

Updated by Ewoud Kohl van Wijngaarden over 7 years ago

  • Status changed from Rejected to Resolved
  • translation missing: en.field_release set to 209

I think closing it as resolved makes it clearer this is now supported. The other issue kind of sneaks it in.

Actions

Also available in: Atom PDF