Bug 31798 – Host names with underscore should be forbidden

Bug 31798 - Host names with underscore should be forbidden


Summary:	Host names with underscore should be forbidden

Status:	RESOLVED DUPLICATE of bug 20482

Product:	UCS
Classification:	Unclassified
Component:	UMC - Computers
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-06-24 13:41 CEST by Jan Christoph Ebersbach
Modified:	2018-04-13 13:30 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Christoph Ebersbach

2013-06-24 13:41:09 CEST

It is possible to create host objects containing an underscore.  These names can't be resolved through Samba 4 and should therefore be forbidden.

Comment 1 Jan Christoph Ebersbach

2013-11-18 09:46:47 CET

Actually, this a a DNS issue.  Hostnames must not include underscores!

A customer reported this problem, today.

Comment 2 Philipp Hahn

2013-11-18 10:08:33 CET

(In reply to Jan Christoph Ebersbach from comment #1)
> Actually, this is a DNS issue.  Hostnames must not include underscores!

Yes and no: DNS allows underscores: RFC 1034, section 3.5 "Preferred name syntax", but host-names are letters-digits-hyphen only: RFC 1123, section 2.1 "Host Names and Numbers.

See <http://www.c3.hu/docs/oreilly/tcpip/dnsbind/ch04_05.htm> and <http://stackoverflow.com/questions/2180465/can-someone-have-a-subdomain-with-an-underscore-in-it> for more details.

Comment 3 Florian Best

2016-03-03 13:07:21 CET


*** This bug has been marked as a duplicate of bug 20482 ***