Also see thread starting at: http://darkwing.uoregon.edu/~llynch/dnsop/msg03465.html
In a discussion between Olaf and Ed, Ed was the last to reply: > > > >> It might be good to note that > >> the time from master to slave is negligible when using NOTIFY and IXFR, > >> increasing by reliance on AXFR, and more if you rely on the SOA timing > >> parameters for zone refresh. (Non-standard means of zone transfers have > >> other timing concerns.) When it comes to freshness of data within caches, > >> the TTL is the only pertinent parameter, with a shorter setting increasing > >> freshness at the cost of fewer cache "hits." > > > >I propose to modify the 3rd paragraph of section 2 by appending your > >text: > > > > Administrators of secured zones will have to keep in mind that data > > published on an authoritative primary server will not be > > immediately seen by verifying clients; it may take some time for > > the data to be transfered to other secondary authoritative > > nameservers and clients may be fetching data from caching > > non-authoritative servers. In this light ist is good to note that > > the time from master to slave is negligible when using NOTIFY and > > IXFR, increasing by reliance on AXFR, and more if you rely on the > > SOA timing parameters for zone refresh. > > s/ist/it/ - in there somewhere. Any other comments? > Not me, if nobody else replies this will be the text. . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
