SIG RR in bind8

[Mark.Andrews at nominum.com]

	This is a known bug and with be fixed 8.2.4.  You may also want
	to take a look at upgrading to BIND 9.1.1rc? if you are working
	with signed zones as BIND 9 has a more complete implementation.

	Mark

Index: src/bin/named/db_load.c
===================================================================
RCS file: /proj/cvs/isc/bind8/src/bin/named/db_load.c,v
retrieving revision 8.111
retrieving revision 8.112
diff -u -r8.111 -r8.112
--- db_load.c	2001/02/04 13:10:45	8.111
+++ db_load.c	2001/02/06 13:35:32	8.112
@@ -2178,8 +2178,7 @@
 	} else {
 		/* Parse and output OTTL; scan TEXP */
 		origTTL = wordtouint32(buf);
-		if (origTTL >= 0 || wordtouint32_error ||
-		    (origTTL > 0x7fffffff))
+		if (wordtouint32_error || (origTTL > 0x7fffffffU))
 			ERRTO("Original TTL value bad");
 		cp = &data[i];
 		PUTLONG(origTTL, cp);
> Alohas,
> 
> I have a signed zone with KEY and SIG records. This is running smootly
> on the master nameserver (bind9) however the slave servers running
> bind8 (8.2.3) will refuse this zone with the error
> 	"Original TTL value bad"
> 
> The source reveals that this has to do with the OTTL field of a SIG
> record. However, it seems to me that bind8 will reject the zone no
> matter what OTTL you specify. Can anybody explain to me what I am
> missing here?
> 
> The relevant portion of parse_sig_rr() in db_load.c (ln.2179):
> 
> 	/* Parse and output OTTL; scan TEXP */
> 	origTTL = wordtouint32(buf);
> 	if (origTTL >= 0 || wordtouint32_error ||
> 		(origTTL > 0x7fffffff))
> 			ERRTO("Original TTL value bad");
>  
> Is it just me, or does this actually mean that any zone with an OTTL >= 0
> will be rejected? And if so, why is that?
> 
> 
> Greetings,
> Johan van Selst
> johans at stack.nl
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com