TLD nameservers that also cache?
blk at skynet.be
Thu Jul 6 15:48:19 UTC 2000
At 8:07 AM -0700 2000/7/6, Rick H Wesson wrote:
> some one else could check me on this idea.... may i suggest you just
> ask the .be for their .be zone and run the .be for your self. if you don't
> need to talk to them your cash won't get poluted.
We could work with DNS.BE and try to become an official secondary
nameserver for this ccTLD, but that doesn't solve the cache pollution
problem represented by ns.belnet.be.
In the past, we have pulled zone transfers from the DNS.BE
nameservers to conduct some testing for the Belgian AltaVista server
we were setting up at the time, but they have since turned off the
ability for unknown servers to pull a zone transfer from those
> this would add the maintance of getting the zone as often as dns.be makes
> it available and you'll have to deal with the consequences if you miss a
> new copy of the zone.
That would speed up our access to the ".be" ccTLD, but it
wouldn't solve the cache pollution problem, because of the way BIND
periodically re-tests response time and makes sure that it
occasionally talks to each of the servers it knows about for each
These are my opinions -- not to be taken as official Skynet policy
Brad Knowles, <blk at skynet.be> || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium
More information about the bind-workers