Re: BIND zone transfers
> On Wed, Feb 08, 2006 at 12:45:02PM -, [EMAIL PROTECTED] wrote: >> Under FreeBSD 4.8 BIND was making zone transfers normally. In my >> network, >> Windows 2000 is the master and bind is the salve. Recently, the server >> was upgraded to FreeBSD 6.0, and suddenly BIND stopped making zone >> transfers, except for the first zone, which is transferred just as it >> should be. Zone transfers are taking place from a W2K server. I am >> seeing this problem with BIND 9.3.2 and BIND 9.3.1 > > Saw this in the BIND FAQ, maybe it applies to your situation: > > > Q: Zone transfers from my BIND 9 master to my Windows 2000 slave fail. >Why? > > A: This may be caused by a bug in the Windows 2000 DNS server where DNS >messages larger than 16K are not handled properly. This can be worked >around by setting the option "transfer-format one-answer;". Also >check whether your zone contains domain names with embedded spaces or >other special characters, like "John\032Doe\213s\032Computer", since >such names have been known to cause Windows 2000 slaves to >incorrectly reject the zone. > > > -- >- Tim Utschig <[EMAIL PROTECTED]> > I did not properly explain the situation. The Windows 2000 server is functioning as a secondary server for the parent organization's DNS, and I am using BIND to download the zones to the local offices, from the W2K server, to help reduce network traffic. Sorry this was not clear the first time. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BIND zone transfers
On Wed, Feb 08, 2006 at 12:45:02PM -, [EMAIL PROTECTED] wrote: > Under FreeBSD 4.8 BIND was making zone transfers normally. In my network, > Windows 2000 is the master and bind is the salve. Recently, the server > was upgraded to FreeBSD 6.0, and suddenly BIND stopped making zone > transfers, except for the first zone, which is transferred just as it > should be. Zone transfers are taking place from a W2K server. I am > seeing this problem with BIND 9.3.2 and BIND 9.3.1 Saw this in the BIND FAQ, maybe it applies to your situation: Q: Zone transfers from my BIND 9 master to my Windows 2000 slave fail. Why? A: This may be caused by a bug in the Windows 2000 DNS server where DNS messages larger than 16K are not handled properly. This can be worked around by setting the option "transfer-format one-answer;". Also check whether your zone contains domain names with embedded spaces or other special characters, like "John\032Doe\213s\032Computer", since such names have been known to cause Windows 2000 slaves to incorrectly reject the zone. -- - Tim Utschig <[EMAIL PROTECTED]> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BIND zone transfers
- Original Message - From: <[EMAIL PROTECTED]> To: Sent: Wednesday, February 08, 2006 2:45 PM Subject: BIND zone transfers Any suggestions as to how to proceed would be greatly appreciated. Thanks in advance for your assistance. Do you have the Win2k IP address defined as a NS to which zone transfer is allowed? (Can't get the BIND documentation atm so cannot tell the exact setting name... -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BIND zone transfers
I have been running BIND for several years in the Regional Offices I maintain and the problem in one office has me confused and I'm not sure where to look. Under FreeBSD 4.8 BIND was making zone transfers normally. In my network, Windows 2000 is the master and bind is the salve. Recently, the server was upgraded to FreeBSD 6.0, and suddenly BIND stopped making zone transfers, except for the first zone, which is transferred just as it should be. Zone transfers are taking place from a W2K server. I am seeing this problem with BIND 9.3.2 and BIND 9.3.1 I am using the same configuration file in two other offices without any problems and the offices are configured identically (hardware, software, etc.). Traceroutes to, and from, the Windows 2000 Server show the proper routes being taken both directions and response times from the servers range between 36ms and 40ms. Event Viewer on the Windows 2000 server shows Event 6002 and the text indicates the remote computer aborted the transfer and the transfer should be restarted at the secondary. When restarting the transfer the same results are achieved. The Windows 2000 Server's DNS is configured to allow BIND secondaries. The FreeBSD server has two interfaces which are controlled by mpd (DSL and VPN). When running named -g, I see the transfers start (zone .XXX/IN: Transfer started), but receive a message later, 30-45 minutes, stating the transfer timed out. The zones I am transferring contain less than 100 entries each. Any suggestions as to how to proceed would be greatly appreciated. Thanks in advance for your assistance. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
