[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

``Secure name resolution'' [Re: ]


Hi,

> > For example, I would like to have www.example.com only be resolvable by
> > members of a specific group, and make it "invisible" to others.

[...]
> You could define those "special" names as zones by themselves, and then
> define separate "view"s for the "permitted" versus the
> "forbidden" clients. This would require BIND 9, which supports "view".

while all these implementation specific solutions (hacks, YMMV) exist, they
are applicable in limited scenarios only. There is no interoperable way
to communicate scopes or views between primary and secondary nameservers,
since the amount of metadata exchanged in a zone transfer is limited to
what the SOA RR can carry.

-Peter

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>