request-nsid seems to not be working (Bind 9.11.3)

Bob McDonald bmcdonaldjr at gmail.com
Wed May 16 19:25:01 UTC 2018


from the Bv9ARM: (9.11.3)

request-nsid
If yes, then an empty EDNS(0) NSID (Name Server Identifier) option is sent
with all
queries to authoritative name servers during iterative resolution. If the
authoritative
server returns an NSID option in its response, then its contents are logged
in the resolver
category at level info. The default is no.

Seems to suggest that they get logged at the info level.

Regards,

Bob

On Wed, May 16, 2018 at 3:18 PM, Bob McDonald <bmcdonaldjr at gmail.com> wrote:

> Is that a functionality change from previous versions? I seem to remember
> it working at the info level.
>
> I could be wrong...
>
> On Wed, May 16, 2018 at 3:09 PM, Tony Finch <dot at dotat.at> wrote:
>
>> Bob McDonald <bmcdonaldjr at gmail.com> wrote:
>>
>> > I have a server that has request-nsid yes; specified in the options
>> block
>> > within named.conf. However, I don't see the NSID responses in the
>> resolver
>> > channel log file.
>>
>> It only appears at debug level 3 or greater.
>>
>> Tony.
>> --
>> f.anthony.n.finch  <dot at dotat.at>  http://dotat.at/
>> Malin, South Hebrides: Northerly 5 at first in east Malin, otherwise
>> variable
>> 3 or 4. Slight or moderate. Fair. Good.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180516/56001cdf/attachment.html>


More information about the bind-users mailing list