problem with a zone transfer and secondary transfer of zone files

[Barry Margolin]

In article <cjcfpp$1pu2$1 at sf1.isc.org>,
 Lance Miller <lance at blackfoot.net> wrote:

> When I try to do a manual zone transfer with dig I get the following
> answer
> 
> # dig school.k12.state.us  axfr
> 
> ; <<>> DiG 9.2.2 <<>> domain.com axfr
> ;; global options:  printcmd
> ; Transfer failed.

Does the master server allow you to perform zone transfers?

> 
> Logs from a transaction;
> 
> messages:Sep 28 12:28:34 ns1 named[195]: lame server resolving
> 'domain.com' (in 'messages:Sep 28 12:28:34 ns1 resolving
> 'Hellgate.k12.mt.us' (in 'hellgate.k12.mt.us'?): 12.32.34.32#53
> messages:Sep 28 12:28:34 ns1 named[196]: lame server resolving
> 'domain.com' (in 'domain.com''?): 1.2.3.4#53

Those messages don't come from zone transfer attempts, those occur when 
your server is recursing.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***