Bug 45701 – .intranet Domain

Bug 45701 - .intranet Domain


Summary:	.intranet Domain

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UCS Installer
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-10 16:25 CET by Kevin Dominik Korte
Modified:	2020-07-03 20:54 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	4: Will affect most installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.091
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018021521001252
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 Kevin Dominik Korte

2017-11-10 16:25:24 CET

We are currently recommending to use a Domain Ending in .intranet. While that currently works there are applications to use .intranet as a publicly available Top-level domain, among others by Liveray. The only reason that hasn't happened is, that there are multiple registrars looking to sell it.

I think we should change the recommendation to follow the recent recommendation of Microsoft, Novel, and RedHat which all recommend a subdomain of a public domain for the internal network.

Comment 1 Stefan Gohmann

2018-02-16 06:22:37 CET

I move this bug from the manual to the installer since we should adjust it directly in our installer.

Comment 2 Ingo Steuwer

2020-07-03 20:54:02 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.