Re: Cant resolve .orgs
From: William Stacey [MVP] (staceywREMOVE_at_mvps.org)
Date: 08/17/04
- Next message: Tweezer: "Re: DNS issues for machines with DHCP reservations."
- Previous message: Jonathan de Boyne Pollard: "Re: Cant resolve .orgs"
- In reply to: Lanwench [MVP - Exchange]: "Re: Cant resolve .orgs"
- Next in thread: Jonathan de Boyne Pollard: "Re: Cant resolve .orgs"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Aug 2004 11:49:52 -0400
> OK, but it's always been my experience that it's faster.
Very well could be. However, to really know for sure, would need to do
specific testing in your environment and name usage patterns and cache
loading, forwarder loading, etc. If you have, for example, a domain name NS
that is already cached, then the resolver will find that NS as the closest
NS and query it directly with one query and one reply. In most cases, com,
net, org will already be cached so unknown second level domain will require
2 queries. For the most part, either method or both seems to work well in
most cases. Cheers.
-- William Stacey, MVP
- Next message: Tweezer: "Re: DNS issues for machines with DHCP reservations."
- Previous message: Jonathan de Boyne Pollard: "Re: Cant resolve .orgs"
- In reply to: Lanwench [MVP - Exchange]: "Re: Cant resolve .orgs"
- Next in thread: Jonathan de Boyne Pollard: "Re: Cant resolve .orgs"
- Messages sorted by: [ date ] [ thread ]