spaces in named.conf

[M. Yu]

>
> are they allowed?
>
> This is what was breaking my zone transfer.

AFAIK, they are (although that would probably depend on where this space
is).  A similar situation almost drove me crazy when I implemented RH6.2's
last bind update rpm from the original rpm.  The new one kept spitting out
errors about invalid serial numbers in my zone files which I could not find
(and which worked on the previous rpm).  Out of frustration (which usually
inspires me to do crazy things), I put all entries in my zone files on 1
VERY long line.  I restarted it and much to my suprise, it worked.  It
became obvious that several carriage returns was causing the problem so I
hunted for it in bind's docs from the website and sure enough there it
was.....setting treat-cr-as-space to yes solved my problem (honestly, I
didn't know such a tag was there from previous versions).

So if you're like me and plan to "beautify" your zone files with formatting
don't forget that tag.  My zone file's format is below:

@ <tab> IN <tab> SOA <tab> blah.blah.com <tab> dnsmaster.blah.com <cr>
<tab> <tab> <tab> { <cr>
<tab> <tab> <tab> <tab> 12414234132; <cr>
<tab> <tab> <tab> } <cr>


M. Yu