Bug 33691
| Summary: | dns records removed or not updating after upgrade to bind 8.2.3 | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Michael Bradley <bearizona> |
| Component: | bind | Assignee: | Bernhard Rosenkraenzer <bero> |
| Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-03-28 22:19:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) After performing the bind upgrade from 8.2.2 to 8.3.1-1 new dns records do not take / propagate and some older dns records vanish although information still exists in named.conf and db.foo.com text file. However, after going back to pervious version of bind all reappears and will disappear again once the upgrade is reinstated. Reproducible: Always Steps to Reproduce: 1.downloading RPMs for upgrading Bind for i386 (bind-8.2.3-1.i386.rpm, devel, and utils) 2.installing RPMs using "rpm -Fvh bind*" while logged in as root user. 3.adding / altering db.foo.com and adding any additional records ("A", MX, CNAME, etc.), verifying pointer from /etc/named.conf points back to db.foo.com file. 4.issuing reload on named process via "/etc/init.d/named reload" command 5.performing nslookup on new record and getting back "Non-existent host/domain" error. Actual Results: after performing above steps new named record(s) are not added to the dns database (for lack of better description) and fails upon performing an nslookup. In addition, any new domain names added fail to be recognized. Expected Results: information to propagate to internal DNS database for broadcast to other name (DNS) servers. in addition, one domain who's information was lost during the upgrade had 52 characters including the .com suffix. all service patch advisories up to this release date (1-29-01) have been implimented on this server. rpm's upgrading bind from 8.2.2 to 8.2.3-1 were done so using "rpm -Fvh bind*" with no other actions or tasks completed during installation. Upon going back to 8.2.2 from 8.2.3 all new records propagate and are varified via performing an nslookup.