BIND 9.3.2 and temp box.

[Eric Berg]

You may be able to do lookups, but it sounds like you may be missing 
records -- like the one that raised the bad owner name error.

I recently wrote a perl script that would take zone files and perform 
name resolution for each entry in each zone file to verify that the 
config was resolving all the same hosts identically on the "new" dns 
servers.  That helps assure me that all of my tweaking, upgrading and 
changing stuff hasn't left anything behind.

-EB.

Mueller, Rex wrote:
> Eric, 
>
> I am able to DIG or NSLOOKUP against the temporary box, My guess is the
> SOATTL is because our zone files are a bit antiquated and not up to
> standards.. 
>
> I may defer that for a different time and question the check-names did
> the trick as far as lookups. 
>
> -----Original Message-----
> From: Eric Berg [mailto:eberg at bergbrains.com] 
> Sent: Monday, December 04, 2006 4:22 PM
> To: Mueller, Rex
> Cc: bind-users at isc.org; Mark Andrews
> Subject: Re: BIND 9.3.2 and temp box.
>
> Rex, looks like you have some bad names in your zone files.  I mainly 
> have run into this when I try to float names that have illegal 
> characters in them.  Depends on the version of bind your running too, 
> because the validation rules have changed from version to version.
>
> I couldn't change my host names that contain underscores "_", so I added
>
> this config which you might want to consider:
>
> options {
> 	check-names master ignore;
> };
>
>
> -Eric.
>
>
> Mueller, Rex wrote:
>   
>> All, 
>>  
>>
>> I have a temporary fedora box built up so I can rebuild our primary
>>     
> DNS
>   
>> box. 
>>
>> I copied the old file structure i.e. Zone Files and named.conf from
>>     
> the
>   
>> old server, and placed on the new server under /var/named/chroot/etc 
>>
>> Ran "/etc/init.d/named start" get some odd errors in the
>> /var/log/messages file
>>
>> bad owner name (check-names) hits the majority of the zone files, 
>>
>> Also when run rndc status the following returns: 
>> rndc status
>>
>> number of zones: 245
>>
>> debug level: 0
>>
>> xfers running: 0
>>
>> xfers deferred: 0
>>
>> soa queries in progress: 0
>>
>> query logging is OFF
>>
>> recursive clients: 0/1000
>>
>> tcp clients: 0/100
>>
>> server is up and running
>>
>>  
>>
>> So it appears it is seeing the zone files.. 
>>
>>  
>>
>> Can someone point me in a direction to head with this? 
>>
>>  
>>
>> Is it because the primary server is still active? And this temp box
>> doesn't know how to play in the same network? What am I missing ? 
>>
>>
>>
>>   
>>     
>
>
>