Bug 71042
| Summary: | Wrong field getting written as primary nameserver | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Jay Turner <jturner> |
| Component: | redhat-config-bind | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | limbo | CC: | srevivo |
| 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: | 2002-08-08 13:48:26 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: | |||
It seems like you are saving the forward zone without entering a Primary Nameserver (SOA). How are you doing this? I can not duplicate this here. Dan Yeah, pretty much I was being stupid. I didn't realize that you weren't requiring "@" in the SOA record anymore, so it wasn't getting accepted and it was really late and I didn't quite realize what was happening :-) Things appear to be working pretty well with redhat-config-bind-1.7.1-12. |
Description of Problem: With redhat-config-bind-1.7.1-10, it appears that the contact field is actually getting written to the zone file as the primary nameserver. Version-Release number of selected component (if applicable): How Reproducible: Steps to Reproduce: 1. Run redhat-config-bind 2. Create a forward master zone and save it 3. Now look at the resulting zone file in /var/named/ Actual Results: You will something like the following: $TTL 86400 @ IN SOA root.localhost ( 1 ; serial Where you can see that "root.localhost" has been written as the primary nameserver (SOA record.) Expected Results: Additional Information: