Date: Tue, 12 Nov 2002 09:47:02 +1100 From: Iain <iain@voffice.myspinach.org> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>, freebsd-questions@FreeBSD.ORG Subject: Re: strange problems with BIND 9.2.1 Message-ID: <200211120947.02170.iain@voffice.myspinach.org> In-Reply-To: <20021111105726.GA5959@happy-idiot-talk.infracaninophi> References: <200211111601.40202.iain@voffice.myspinach.org> <200211112111.35154.iain@voffice.myspinach.org> <20021111105726.GA5959@happy-idiot-talk.infracaninophi>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
Well I tried disabling the zone with the CNAME warning and I still get th=
e=20
same behaviour. I am still getting the messages about TTL but that is jus=
t a=20
warning right?
cheers, Iain.
On Mon, 11 Nov 2002 09:57, Matthew Seaman wrote:
> problem is the errors in your zone files that named is complaining
> about. Bind 9 is rather stricter about several questionable
> constructs. The "CNAME and other data" thing is a case in point ---
> you can't mix CNAME's and other RR types for the same RRset:
>
> ; Illegal...
> foo IN CNAME bar
> IN MX blurfl
>
> You shouldn't even have multiple CNAME's in the same RRset:
>
> ; Illegal...
> foo IN CNAME foo1
> IN CNAME foo2
>
> although you used to be able to persuade Bind 8 to accept that given
> the correct options {}; statement.
>
> The "no TTL specified; using SOA MINTTL instead" thing you're seeing
> on those slave zones is just a warning and shouldn't prevent your
> server working. If the master for those zones is running Bind 8.2 or
> higher, you might prevail on the admin to add a reasonable default TTL
> at the top of the file:
>
> $TTL 7200 ; Default 3h TTL on RRs
>
> Cheers,
>
> Matthew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211120947.02170.iain>