secondary name server not updating

[Barry Margolin]

   Date: Wed, 26 Apr 2000 19:58:36 -0400
   From: Frank Auciello <frank at torontowiredsolutions.com>

   these used to all be working fine. The only changes I made was installed 
   SSH and commented out everything in the inetd.conf file.

Those sound like they're part of an overall network security
implementation.  Could someone have also configured some packet filtering
that would affect connections from the slave to the master (although if the
two machines are ns1.torontowired.com and ns2.torontowired.com, they appear
to be on the same subnet, so this seems unlikely)?

What happens if you do:

dig canadianplaza.com axfr @209.47.165.5

on the slave?  I have no problem doing this from outside your network.

You could try running named on the slave with the -d option to see what
it's doing.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA