BIND 9.3.2 and temp box.

[Mueller, Rex]

In my /var/log/messages I am getting the following message: 

no TTL specified - using SOA MINTTL instead

Currently our zone files have the following information in the SOA area:

@       IN      SOA     ns1.OURDOMAIN.org.  dns.ns1.OURDOMAIN.org. (
                        200612050 ;Serial
                        43200   ; Refresh - 12 hours
                        1800    ; Retry - 1 minute
                        604800  ; Expire - 2 weeks
                        86400)  ; Minimum - 12 hours


IF I put an entry as 
$TTL 86400
Above the SOA will the error/message go away? 

Does the TTL directive need to be at the top of the zone file or the
bottom or does it require that it be in the SOA section? 



-----Original Message-----
From: Eric Berg [mailto:eberg at bergbrains.com] 
Sent: Tuesday, December 05, 2006 6:52 AM
To: Mueller, Rex
Cc: bind-users at isc.org; Mark Andrews
Subject: Re: BIND 9.3.2 and temp box.

Rex,

I didn't have this particular problem.  I think that one of the things 
that become more strict in the latest bind is some of the 
inheritance-related stuff.  Now you actually have to have your TTL 
wherever it belongs. 

-E.

Mueller, Rex wrote:
> From that it indicates the TTL is required does this require and entry
> in each zone file? 
>
> What was your work around? Did you write an awk script to insert a
line
> below the SOA? Or is TTL something that can be placed in the
named.conf
> and passed along? 
>
> -----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 ? 
>>
>>
>>
>>   
>>     
>
>
>