Re: clarification on AXFR

At Thu, 3 Jun 2010 11:39:30 +0530, rams wrote: > During AXFR of a zone, the zone.dbfile is not created till the AXFR > completes. Till AXFR completes, the file name will be some value as > 456eefwfc. Is it correct behavior? Yes, that's the intended behavior. --- JINMEI, Tatuya Internet Systems

Re: rndc flush(more-than-one)name

At Thu, 3 Jun 2010 15:21:08 +0200, Matus UHLAR - fantomas wrote: > > "rndc flushnamespace" / "rndc flushname -recurse" would have to > > walk the tree and remove each entry. This can be time consuming. > > is this planned feature or does it already work somewhere? This is a planned (or

Re: Choosing authoritative nameservers

Thanks for the reply sir! Just to share, I've finally figured out why my traces always seem to be hitting ens2.bursamalaysia.com no matter what I do. A packet dump actually shows requests being sent out to both ens1.bursamalaysia.com and ens2.bursamalaysia.com but somehow only ens2.bursamalaysi

RE: Multiple PTRs for an in-addr

Well said, Paul. I make my users choose between the various names for a server, and generally publish the name that the machine actually knows itself as, rather than any of the application names that reside there. In my opinion, the RFC is fairly clear. And my users don't know you have added thi

Re: rndc flush(more-than-one)name

> In message , Chris > Thom > pson writes: > > Arising out of today's little accident with the "de" TLD ... > > > > Am I right in thinking that "rndc flushname de" flushes only entries for > > that specific name, and not for names in the tree *under* "de"? It would > > be rather useful to have th