on 7/30/2002 4:56 PM John C Klensin wrote: > is one. How often the user/ server queries for COM during that > TTL interval doesn't count, the only thing that is important is > whether or not one such query occurs. I'm perfectly aware, thankyouverymuch. > And what happens to ".re" relative to ".com" has nothing to do > with the story. .edu versus .com then, or .au versus .com, or anything you want. There are millions of organizations that don't issue queries for those zones either. Perhaps somebody will be kind enough to post some actual per-TLD statistics for those zones. If something like .pr0n (being sensitive to mail filters) starts taking out a massive number of .com sites, there will be fewer queries for .com. No question about it. Saying that there will be no more queries for .com is fairly ludicrous, but it can be sustainably argued that some networks will timeout their internal caches for longer periods, resulting in a slight lowering of .com lookups. Meanwhile, there will be lots of networks that NEVER lookup any domain in the .pr0n TLD. Furthermore, domains which had been operating under .kr, .ru, .uk and so forth will also move, resulting in those tertiary zones getting fewer root queries. So even though there may be an equal number of domains under the .com and .pr0n titan TLDs, the overall load will likely have only gone up by a few percentage points. This is especially true if the overall number of resolver-side queries is consistent. -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/