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

[idn] Re: Optional & Additional Character Equivalence Preparations byZone

--On 2002-01-23 13.19 -0500 Edmon <edmon@neteka.com> wrote:

> But caching servers only cache the result of a query.
> for example a domain request
> <A><A'>.example
> the .example ns would internally match it with
> <a><a>.example
> and reply with a positive response.
> the caching server will therefore cache
> <A><A'>.example
> with the response.
> If you are asking what happens if another request comes:
> <a><A'>.example
> then the answer is simple, it will consult the .example server again,
> then it will cahce
> <a><A'>.example
> with the response.
> So, I dont see why all the servers in the world needs to be able to handle
> all additional matching rules.

It's not that easy. The result coming back is called an RR-Set, which means
all records which have the same owner. The responses are always treated in
groups of RR-Sets.

Now, given that we have one RR-Set which has different content on an
authoritative server from a caching server, read your favourite RFC's about
DNS Security.

Just don't go there.

     paf