Problem with DDNS and Bind 8.1.2

[Mark_Andrews at isc.org]

> Running into a problem running Bind 8.1.2, DHCP 2.0b1pl6 (yes, I know
> it's old, but there's no update without moving to a 2.2.x kernel+other
> work) and the DHCP-DNS perl scripts.  I have two DNS servers (a master @
> .14 and a slave @ .15) also acting as DHCP servers on a private class c
> network.  They both serve a range of 100 ip addresses (from .51 to .150
> and from .151 to .250, so there is no overlap).  The following messages
> are appearing in the logs on the master DNS server, and the files on the
> slave server are not getting updated as the master files are changed.
> 
> Any help would be *greatly* appreciated.
> 
> TIA,
> 
> Ken McCord

	Firstly I would change bind versions, BIND 8.1.2 reported this
	under non error conditions.

	Mark
> 
> 
> 
> 24-Sep-1999 21:19:59.784 update: error: error processing update packet
> id 37110 from [192.168.1.15].1098
> 24-Sep-1999 21:19:59.809 update: error: error processing update packet
> id 37878 from [192.168.1.15].1101
> 24-Sep-1999 21:19:59.945 update: error: error processing update packet
> id 40182 from [192.168.1.15].1110
> 24-Sep-1999 21:19:59.968 update: error: error processing update packet
> id 40950 from [192.168.1.15].1113
> 24-Sep-1999 21:20:00.099 update: error: error processing update packet
> id 43254 from [192.168.1.15].1122
> 24-Sep-1999 21:20:00.124 update: error: error processing update packet
> id 44022 from [192.168.1.15].1125
> 24-Sep-1999 21:20:00.872 update: error: error processing update packet
> id 46326 from [192.168.1.15].1134
> 24-Sep-1999 21:20:01.012 update: error: error processing update packet
> id 47094 from [192.168.1.15].1138
> 
> 
> Here is a copy of the master's /etc/named.conf file:
> 
> 
> // generated by named-bootconf.pl
> 
> options {
> 	directory "/var/named";
> 	/*
> 	 * If there is a firewall between you and nameservers you want
> 	 * to talk to, you might need to uncomment the query-source
> 	 * directive below.  Previous versions of BIND always asked
> 	 * questions using port 53, but BIND 8.1 uses an unprivileged
> 	 * port by default.
> 	 */
> 	// query-source address * port 53;
> };
> 
> // 
> // a caching only nameserver config
> // 
> logging {
> 	channel update_debug {
> 		file "/var/log/named/update.debug";
> 		severity debug 3;
> 		print-category yes;
> 		print-severity yes;
> 		print-time yes;
> 	};
> 	category update {update_debug;};
> };
> 
> zone "ac-coin.com" {
> 	type master;
> 	file "/etc/zone/ac-coin.com";
> 	notify yes;
> 	also-notify { 192.168.1.15; };
> 	allow-update { 192.168.1.14;192.168.1.15; };
> };
> 
> zone "0.0.127.in-addr.arpa" {
> 	type master;
> 	file "/etc/zone/127.0.0";
> };
> 
> zone "1.168.192.in-addr.arpa" {
> 	type master;
> 	file "/etc/zone/192.168.1";
> 	notify yes;
> 	also-notify { 192.168.1.15; };
> 	allow-update { 192.168.1.14;192.168.1.15; };
> };
> 
> zone "." {
> 	type hint;
> 	file "named.root";
> };
> 
> 
> 
> Here is a copy of the slave's /etc/named.conf file:
> 
> // generated by named-bootconf.pl
> 
> options {
> 	directory "/var/named";
> 	/*
> 	 * If there is a firewall between you and nameservers you want
> 	 * to talk to, you might need to uncomment the query-source
> 	 * directive below.  Previous versions of BIND always asked
> 	 * questions using port 53, but BIND 8.1 uses an unprivileged
> 	 * port by default.
> 	 */
> 	// query-source address * port 53;
> };
> 
> // 
> // a caching only nameserver config
> // 
> zone "ac-coin.com" {
> 	type slave;
> 	file "/etc/zone/ac-coin.com";
> 	masters {
> 		192.168.1.14;
> 	};
> };
> 
> zone "1.168.192.in-addr.arpa" {
> 	type slave;
> 	file "/etc/zone/192.168.1";
> 	masters {
> 		192.168.1.14;
> 	};
> };
> 
> zone "0.0.127.in-addr.arpa" {
> 	type master;
> 	file "/etc/zone/127.0.0";
> };
> 
> zone "." {
> 	type hint;
> 	file "named.root";
> };
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org