Hostname Naming Compliance
jlightner at water.com
Mon Feb 23 19:35:26 UTC 2009
And of course you can legitimately say it is a "Standard" even if it
isn't enforced by the software. Your argument would be that people
implementing new servers or attempting to access the systems wouldn't be
able to do so because they wouldn't have added the "exception to
Standard" that your PHBs are requiring.
From: bind-users-bounces at lists.isc.org
[mailto:bind-users-bounces at lists.isc.org] On Behalf Of Chris Thompson
Sent: Monday, February 23, 2009 2:31 PM
To: Bind Users Mailing List
Subject: Re: Hostname Naming Compliance
On Feb 23 2009, Evan Hunt wrote:
>On Mon, Feb 23, 2009 at 01:54:46PM -0500, Eric C. Davis wrote:
>> I know the option to use this compliance checker is present, but I'm
>> curious to know if there are plans to make it mandatory to comply.
>> aren't using this feature now, but I would like to. My problem is
>> politicking my way around the issue of breaking something that works.
>> If Bind were to say they were going to start forcing compliance with
>> this naming standard, then I simply have to say it's a standard that
>> being enforced. Shouldn't enforcement be applied across the board
>> anyway instead of at the operator's discretion?
>I haven't heard anyone at ISC suggest this, but if I did, I'd argue
>against it. I don't think we have any wish to be the "enforcers". :)
>And anyway, if we put "mandatory" compliance into BIND, people who
>wanted to break the rule would just hack it back out again.
Or switch to different nameserver software that wasn't so proscriptive.
There's a strong argument that it isn't the job of BIND to be enforcing
restrictions that are not strictly DNS-related (vide RFC 2181 section
The current uneasy compromise, in which there are restrictions that are
meant to be helpful, but which can be turned off, is probably the best
that can be achieved.
Email: cet1 at cam.ac.uk
bind-users mailing list
bind-users at lists.isc.org
Please consider our environment before printing this e-mail or attachments.
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
More information about the bind-users