At 02:06 04/06/2009, Sabahattin Gucukoglu wrote:
On 4 Jun 2009, at 04:06, Mark Andrews wrote:
In message
aaab52ef-ad0a-4d3c-9b28-b864f342d...@sabahattin-gucukoglu.com ,
Sabahattin Gucukoglu writes:
The problem is this: the authoritative servers for a domain can
easily
never be consulted for
On 4 Jun 2009, at 04:06, Mark Andrews wrote:
In message aaab52ef-ad0a-4d3c-9b28-b864f342d...@sabahattin-gucukoglu.com
, Sabahattin Gucukoglu writes:
The problem is this: the authoritative servers for a domain can
easily
never be consulted for DNS data if the resource being looked up
happens
Sabahattin Gucukoglu wrote:
Glue data, additional and non-authoritative by design, intent and
specification, aren't what I want caches to keep.
You had better cache glue As, as long as they are tagged as glue
As with a domain name of query.
Then, the cached information may be used as glue
... it's that, or my reading of RFC 2181 has gone horribly wrong.
The problem is this: the authoritative servers for a domain can easily
never be consulted for DNS data if the resource being looked up
happens to be available at the parent zone. That is,
bigbox.example.net's address and
In message aaab52ef-ad0a-4d3c-9b28-b864f342d...@sabahattin-gucukoglu.com, Sab
ahattin Gucukoglu writes:
... it's that, or my reading of RFC 2181 has gone horribly wrong.
The problem is this: the authoritative servers for a domain can easily
never be consulted for DNS data if the resource
