AXFR partially timed out

[Dave Sparro]

On 10/7/2010 4:55 AM, Beat Jucker wrote:
> Hello BIND users
>
> I have a very strange problem with AXFR. We are using a master and a
> secondary DNS Server with an internal and an external view. Depending
> on the source address the secondary server will get the internal or
> external view for zone transfer.
>
> Everything is working correct so far except only one specific zone file
> won't get transferred. In the external view there are about 70 zones
> defined. Every zone will get transferred except one and only one won't.
> Therefor there can't be a problem with the firewall.
>
> Then I scaled down the seconday DNS server to just about 2 zones and
> again: this specific zone file won't get transfered even the master
> said "AXFR started" and "AXFR ended" for this particular zone. On
> the secondary server I'll get "giving up: timed out".
>
> To test zone transfer by DIG I shut down the internal IP interface
> so the AXFR request used the external IP interface for the zone transfer
> and everything was ok (zone transfer succeeded).
>
> I also checkd the zonefile against nonASCII chars. Everything looks
> correct. I'm realy confused (by the way: we are still using BIND-0.9.5)
>
> Do you have any idea ... ?
>

Is the problem zone larger than the ones that are not a problem?  If so 
it may be a MTU problem, or even a firewall that does things differently 
based on packet sizes.

-- 
Dave