BIND 10 #1994: RFC 5001 (NSID) support, configuration
BIND 10 Development
do-not-reply at isc.org
Thu May 24 22:03:29 UTC 2012
#1994: RFC 5001 (NSID) support, configuration
-------------------------------------+-------------------------------------
Reporter: shane | Owner:
Type: | Status: new
enhancement | Milestone: Next-Sprint-
Priority: | Proposed
medium | Resolution:
Component: | Sensitive: 0
Unclassified | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: NSID |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Description changed by shane:
Old description:
> This ticket covers part of implementing RFC 5001.
>
> http://tools.ietf.org/html/rfc5001
>
> The RFC identifies a lot of information that could be returned.
>
> I propose that we provide configuration that supports:
>
> 1. Disabling NSID completely
> 2. Specifying a fixed string to be returned
> 3. Returning gethostname()
>
> BIND 9's default is #3 (or rather, it is for hostname.bind), so probably
> this should be what BIND 10 defaults to.
New description:
This ticket covers part of implementing RFC 5001.
http://tools.ietf.org/html/rfc5001
The RFC identifies a lot of information that could be returned.
I propose that we provide configuration that supports:
1. Disabling NSID completely
2. Specifying a fixed string to be returned
3. Returning gethostname()
BIND 9's default is disabled, so possibly this is what BIND 10 should
default to. Although I tend to think that option 3 is the best.
--
--
Ticket URL: <http://bind10.isc.org/ticket/1994#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list