Project

General

Profile

Actions

Bug #3156

closed

Foreman allows underscores in hostnames

Added by Petter Hassberg over 10 years ago. Updated almost 10 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

If I enter a hostname with an underscore in it while creating a new host,

eg "ore1-func_2", then foreman won't complain although the smart-proxy won't be able to update the dns record.


Related issues 1 (0 open1 closed)

Is duplicate of Foreman - Bug #3697: Field Validations Should be more ComprehensiveClosedStephen Benjamin11/20/2013Actions
Actions #1

Updated by Petter Hassberg over 10 years ago

reproduced in foreman-1.2.1-1.el6.noarch

Actions #2

Updated by Dominic Cleal over 10 years ago

  • Category set to Host creation

We'll have to be careful implementing this, as underscores are valid in domains. Perhaps we can prohibit it in the hostname and permit it only in the domain portion.

Actions #3

Updated by Greg Sutcliffe over 10 years ago

If you go down that road, watch out for unmanaged Hosts, we specify the FQDN in the name field there...

Actions #4

Updated by Ewoud Kohl van Wijngaarden over 10 years ago

Since those host names are not allowed by the DNS RFC, it should be discouraged. (In practice it may or may not work since most software does accept it.) From http://domainkeys.sourceforge.net/underscore.html: Host names are not allowed to have underscores in them. In DNS, host names are the name fields of A or MX records or the data fields of the SOA and NS records. Thus, there are many DNS entries that are not hostnames.

Actions #5

Updated by Dominic Cleal almost 10 years ago

  • Is duplicate of Bug #3697: Field Validations Should be more Comprehensive added
Actions #6

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Duplicate

Shipped in 1.4 via #3697.

Actions

Also available in: Atom PDF