It doesn't really matter whether the vendor claims that the data is
"also" cached data, since the RFC clearly states "if the desired data is
present in authoritative form [...] use the authoritative data in
preference to cached data". In other words, authoritative data trumps
cached data. This
By saying things like "We load the authoritative data into memory so
that is also cached data" and other nonsense the vendor is stating
that this behavior is in compliance with the RFCs and refusing to fix
their code. Very frustrating, as I believe this behavior is clearly
wrong and also se
The "resolver algorithm" in RFC 1034, Section 5.3.3, states
1. See if the answer is in local information, and if so return
it to the client.
and is further detailed as
Step 1 searches the cache for the desired data. If the data is in the
cache, it is assumed to be goo
My apologies if this is considered to be too off-topic.
I have a situation where my company uses a number of servers with a
commercial DNS implementation (in addition to our BIND servers). The
other implementation is Windows DNS, and there is some behavior that I
do not think is acceptable,
4 matches
Mail list logo
