propagation for .com tld

[Jim Reid]

>>>>> "Barry" == Barry Margolin <barmar at genuity.net> writes:

    Barry> Do the GTLD servers really use normal zone transfer for the
    Barry> COM domain?

Who cares what they do as long as the process is reliable and works
quickly enough? This is an implementation detail that only matters to
the operator of the gTLD servers provided they do that job properly.
Does anyone outside Genuity care how the genuity.net zone gets
propagated between its servers?

    Barry> Given the size of the domain and the DNS
    Barry> protocol's feeble "compression" scheme, this seems like an
    Barry> incredibly inefficient way to do it, probably taking the
    Barry> better part of a day.  My guess is that gzip can reduce its
    Barry> size to around 10%, so it would be better for them to
    Barry> configure all the GTLD servers as masters and perform
    Barry> periodic FTP's of the compressed zone file.

Have you been talking to DJB recently? :-) Another possible approach
Verisign/NSI might use for .com is to have each server independently
build the zone file from the back-end registry database.