Red Hat Bugzilla – Bug 71042
Wrong field getting written as primary nameserver
Last modified: 2015-01-07 18:58:51 EST
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:
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.