Whats wrong with my zone files?

[Karl Auer]

On Fri, 2008-07-18 at 15:13 +0100, Jon Harris wrote:
> "no TTL specified; using SOA MINTTL instead" 
> 
> If I put the TTL in the front:
> 
> @ 86400 IN SOA ns0.mydomain.net. root.ns0.mydomain.net. (2008071801
> 10800 3600 604800 86400 )
> 
> - no warning.
> 
> Q1. Aren't I specifying the TTL twice? 
The "TTLs" in the SOA relate to the zone as a whole; the TTL that is
"missing" is the one for each separate entry in the zone. They all have
separate TTLs anyway, even if you don't specify them. BIND9 is just
telling you the value it is using for those TTLS in the absence of
information in the zone files.

> Q2. I hate seeing processes start with a screen full of errors (assuming
> it will start) , so if I have to do this, is their a way I can script
> the change/bulk convert? - I have over 400 zone files to move.

It's not an error, it's just a warning, so it should not of itself
prevent startup. In fact, BIND9 is taking this step precisely so as to
avoid having to not load the (actually invalid) zone file. If 86400 is
an acceptable TTL value to you, you can ignore the warnings.

But I agree it would be nicer without them. It might be simplest to
script the addition of "$TTL 86400" to the top of each zone file:

for each here/filename
   echo "$TTL 86400" > there/filename
   cat here/filename >> there/filename
   mv there/filename here/filename

... or suchlike.

86400 seems a longish TTL if you ask me. Not that you did :-)

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/~kauer/                  +61-428-957160 (mob)

GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28
Public key at  : random.sks.keyserver.penguin.de