New Zone Appears to Work but Can't be read

[Martin McCormick]

	Here is a followup report since I think it is important
to at least let those who tried to help know what happened.

	I may have corrupted the zone file and then compounded
the error by using named-checkzone against the wrong zone file.
(too big of a hurry).

	The second time around, I generated a zone file with dig
which is much more human-readable than the dynamically generated
zone file of our master dns.  Oh!  That file is quite readable,
but I may have overlooked some of the old information due to the
hashing.

	I then reconstructed the new zone with all the right NS
records and none of the old information that went to the new zone
and it all worked perfectly.  Thanks anyway for your help.

Mark_Andrews at isc.org writes:
>
>> 	We have just made a new zone out of a domain that was
>> simply a mid-level domain in our main zone.  I wrote a new zone
>> file for that zone and named-checkzone seems to like it.
>> 
>> 	I installed NS records in our main zone pointing queries
>> for this domain to the new zone.
>> 
>> 	I then removed all MX, TXT, CNAME and A records from our
>> main zone and put them in the new zone and restarted everything.
>> 
>> 	The new zone propagates to slave servers looking for it
>> but you can't do any queries against any of the addresses in it.
>> 
>> 	What else should I check for!!? 
>
>	Do you have a allow-query in the options that needs to be
>	overridden at the zone level?
> 
>> 	The mail zone and the new split-off zone are both running
>> on the same bind process.  I have a suspicion that this may have
>> something to do with the impass.
>> 
>> 
>> Martin McCormick WB5AGZ  Stillwater, OK 
>> OSU Center for Computing and Information Services Network Operations Group
>> 
>--
>Mark Andrews, Internet Software Consortium
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org
>