Remaining issues holding up BIND 8.2.3?

David R. Conrad David.Conrad at nominum.com
Thu Jun 8 05:04:20 UTC 2000


Hi,

> What are the NT bugs?

OK, I lied.  There are 2 bugs and another issue which I'll address first:

- we're told it doesn't compile because some files can't be found,
specifically:

	Subject: Compile problem with BIND V8.2.3-T5B
	Date: Thu, 1 Jun 2000 14:22:59 -0400

	...

	As part of my "research" on this bug, I downloaded V8.2.3-T5B 
	from the isc.org website.  I've been able to compile almost 
	everything, but there are critical files missing from the 
	/src/port/winnt/BINDInstall directory, so the installer cannot 
	be created.

	In particular, I know at least that BINDInstall.mak and 
	VersionInfo.h are missing...possibly others.

	Is there anything you can do to help get a complete copy of 
	the BINDInstall directory (or the entire WinNT port) so that
	I can try out 8.2.3?   Do I need to "officially" report that
	the WinNT port of 8.2.3-T5B doesn't build the installer?  
	(I'm sure that nobody wants to release it with missing files!)

	...

- listen-on doesn't, that is, BIND on NT won't recognize/use more than one
interface

- BIND on NT crashes when subjected to a large number of A records in a
response:

	Subject: [BIND-BUGS #927] query results set crashes 
		 NT port of BIND 8.2.2 p5
	Date: Wed, 31 May 2000 06:05:21 +0200

	Hello ISC,

	This following dig will crash named on bindnt.nsmachine.com:

	# dig @bindnt.nsmachine.com adsdl.conducent.com a

	; <<>> DiG 8.2 <<>> adsdl.conducent.com a
	;; res options: init recurs defnam dnsrch
	;; got answer:
	;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
	;; flags: qr rd ra; QUERY: 1, ANSWER: 48, AUTHORITY: 5, 
	;; ADDITIONAL: 5
	;; QUERY SECTION:
	;;      adsdl.conducent.com, type = A, class = IN

	;; ANSWER SECTION:
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.120
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.91
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.95
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.97
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.64
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.67
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.69
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.52
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.55
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.94
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.96
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.111
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.113
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.115
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.117
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.119
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.63
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.65
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.68
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.51
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.53
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.56
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.57
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.58
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.59
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.60
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.61
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.62
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.63
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.64
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.65
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.67
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.68
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.69
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.70
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.71
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.72
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.73
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.60
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.61
	adsdl.conducent.com.    17h51m48s IN A  216.33.210.62
	adsdl.conducent.com.    17h51m48s IN A  216.35.217.66
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.90
	adsdl.conducent.com.    17h51m48s IN A  216.32.73.120
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.112
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.114
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.116
	adsdl.conducent.com.    17h51m48s IN A  216.33.199.118

	;; AUTHORITY SECTION:
	CONDUCENT.com.          17h51m48s IN NS  dns1.CONDUCENT.com.
	CONDUCENT.com.          17h51m48s IN NS  sec1.dns.psi.net.
	CONDUCENT.com.          17h51m48s IN NS  sec2.dns.psi.net.
	CONDUCENT.com.          17h51m48s IN NS  sca02.sec.dns.exodus.net.
	CONDUCENT.com.          17h51m48s IN NS  sca03.sec.dns.exodus.net.

	;; ADDITIONAL SECTION:
	dns1.CONDUCENT.com.     1d17h51m48s IN A  216.35.217.254
	sec1.dns.psi.net.       1h34m24s IN A   38.8.92.2
	sec2.dns.psi.net.       1h34m24s IN A   38.8.93.2
	sca02.sec.dns.exodus.net.  1d23h59m13s IN A  209.1.235.120
	sca03.sec.dns.exodus.net.  1d23h59m13s IN A  216.32.126.150

	;; Total query time: 33 msec
	;; FROM: mgw1.meiway.com to SERVER: default -- 212.73.210.69
	;; WHEN: Wed May 31 14:01:27 2000
	;; MSG SIZE  sent: 37  rcvd: 1021

Any help anyone can provide for this would be much appreciated.

Thanks,
-drc
 
> -Kevin
> 
> At 08:39 AM 06/07/2000 -0700, David R. Conrad wrote:
> >Joe,
> >
> > > Just out of curiosity, what are the issues that remain with the
> > > BIND 8.2.3 release which are preventing it from being formally
> > > released?
> >
> >There are two bugs with the NT port that we're aware of.  I have told
> >Paul not
> >to cut final until those issues are resolved.  Unfortunately, we don't
> >have a
> >lot of NT folk here, so we've been hoping folks with NT experience on
> >bind-workers or bind-winners will help us out.
> >
> >We've also be hesitant to cut 8.2.3 final due to continuing complaints
> >about
> >security issues with 8.2.2-P5, however in all cases, we have been unable
> >to
> >find any evidence that the problem is in 8.2.2-P5 (typically, people
> >have
> >installed 8.2.2-P5, but have not killed off the running 8.2.1).
> >
> > > What's the current thinking on when 8.2.3 will
> > > become official?
> >
> >Hopefully, within the next week or two.
> >
> >Rgds,
> >-drc





More information about the bind-workers mailing list