AXFR refused?

[Michael Quan]

From: Mark.Andrews at nominum.com

>	You should have *both* 110.103.216.IN-ADDR.ARPA and 
>	240.110.103.216.IN-ADDR.ARPA as zones on your server.

>	110.103.216.IN-ADDR.ARPA should be being transfered from your
>	ISP's servers.  This zone contains CNAME records that point into
>	240.110.103.216.IN-ADDR.ARPA for final resolution.

>	240.110.103.216.IN-ADDR.ARPA should contain the PTR records for
>	the machines in your subnet.  Your ISP will normally secondary
>	this zone to reduce the number of queries required to resolve
>	a reverse lookup.

>	Your ISP has setup 110.103.216.IN-ADDR.ARPA correctly.  What you
>	currently have as 110.103.216.IN-ADDR.ARPA should be in
>	240.110.103.216.IN-ADDR.ARPA.

	I moved what I have in my 110.103.216.IN-ADDR.ARPA into
240.110.103.216.IN-ADDR.ARPA but now named says
"242.110.103.216.IN-ADDR.ARPA is outside zone (ignored)" and reverse
lookups no longer work within my network.

>   e.g.
>	/*
>	 * 110.103.216.IN-ADDR.ARPA is required so that local reverse
>	 * lookups work when the external link is down.
>	 */
>	zone "110.103.216.IN-ADDR.ARPA" {
>		type slave;
>		file "216.103.110.rev";
>		masters { 206.13.28.11; 206.13.29.11; };
>	};

	So if I understand this correctly, I become a slave to
206.13.28.11 and 206.13.29.11 for the file 216.103.110.rev.
	Now the new file 216.103.110.rev what should go into there?

>	zone "240.110.103.216.IN-ADDR.ARPA" {
>		type master;
>		file "216.103.110.240.rev";
>	};

	As I said previously named now reports
"242.110.103.216.IN-ADDR.ARPA is outside zone (ignored)" and no
reverse works inside or out.
	I still get AXFR refused from ns1.pbi.net.

	What about this entry in my named.conf.

	zone "pbi.net"{
	     type slave;
	     ....
	     ....

        That tells named that pbi.net is my secondary.  Do I still
need this?

Thanks,
Michael