Bug 25378 – Bind 8.2.3 upgrade fails

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 25378 - Bind 8.2.3 upgrade fails

Summary:	Bind 8.2.3 upgrade fails

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bind (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-31 09:54 EST by Bruce Garlock
Modified:	2007-04-18 12:31 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-01-31 12:56:36 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bruce Garlock 2001-01-31 09:54:37 EST

After updating to bind-8.2.3 for RH 6.2, doing a nslookup gives me this:

*** Can't find server name for address 192.168.200.180: No response from server

When I back down to 8.2.2P7, everything works fine.

Comment 1 Daniel Roesen 2001-01-31 11:20:58 EST

Check your /var/log/messages for named startup errors. I guess your zone file(s)
have incorrect SOA syntax and were rejected upon BIND startup.

Comment 2 Bruce Garlock 2001-01-31 12:56:32 EST

Ahh!  That was it.  8.2.3 is less forgiving on syntax errors!  After I corrected the errors, everything is now fine.

Thanks for pointing me in the right direction.

Note You need to log in before you can comment on or make changes to this bug.