Date: Mon, 15 Nov 1999 10:00:18 +0000 From: Richard Morte <ric@sinclairassoc.force9.co.uk> To: Michael Kennett <mike@laurasia.com.au>, John <papalia@UDel.Edu> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: DNS (was: DNS & Virtual hosting) Message-ID: <382FD9B2.985E8A8B@sinclairassoc.force9.co.uk> References: <199911150457.MAA06677@laurasia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
John
Have you tried running nslint? It usually picks up very well on
configuration errors. There are a few occasions when you may not want
reverse mapping (IP address ==> Name); for instance, we have an Apache
server on our FreebSD box, configured for name-virtual hosting. All the
names of the virtual domains share the same IP address, so we have a
zone that provides this mapping, but no reverse mapping (ie no PTR
records).
nslint complains about the fact that there are no PTR records for our
'Apache' domains, but this is nslint being too conservative in this
instance.
Recommend you try it! (Apologies if you already have!)
Ric
Michael Kennett wrote:
>
> Hello John,
>
> > Mike,
> >
> > My "flawless" installation of named seems to have some bugs, but I think
> > they're "user error"... upon bootup, I get the following messages:
> >
> > merlin# Nov 14 23:08:42 merlin named[394]: reloading nameserver
> > Nov 14 23:08:42 merlin named[394]: /etc/namedb/named.conf:64: syntax error
> > near zo
> > ne
> > Nov 14 23:08:42 merlin named[394]: /etc/namedb/named.conf:97: cannot
> > redefine zone
> > '75.175.128.in-addr.arpa' class 1
> > Nov 14 23:08:42 merlin named[394]: /etc/namedb/named.conf:107: cannot
> > redefine zon
> > e '75.175.128.in-addr.arpa' class 1
> > Nov 14 23:08:42 merlin named[394]: Ready to answer queries.Nov: No match.
> >
> > Seems easy enough to trackdown, rite? Well, this is where the text is
> > tripping up:
> >
> > The syntax error near line 64:
> >
> > //};
> ^^^^ (see comment below)
>
> The snippet:
>
> >
> > zone "0.0.127.IN-ADDR.ARPA" {
> > type master;
> > file "s/named.localhost.rev";
> > };
>
> looks fine to me.
> >
> > I don't see a syntax error?
>
> Neither do I! What about any syntax errors before this snippet? E.g. does
> the 'options' declaration have a closing brace? Is it possible that you've
> commented it out? The zone declarations must be in a different block from
> the options declarations.
>
> If you can't find the problem, it would help if you send the entire named.conf
> file to the list.
>
> >
> > As for the "can't redefine zones", here are examples of my zones. Are
> > these allowed: Please recall that I'm planning on setting up 3 domains on
> > a single IP. In the examples, taking 1.2.3.4 to be my IP and 192.168.1.*
> > to be my internal subnet. Given that there are 3 domains, are the 2nd and
> > third zones for reverse IP's needed, or is there something to do inside the
> > single reverse to make it happen
>
> The reverse mapping is taking an IP address and converting it into a name.
> By setting up three different reverse mapping rules, how can this conversion
> be done uniquely? It can't.
>
> So named is quite correct at barfing about the redeclarations of the
> reverse mappings in the 3.2.1.in-addr.arpa zone. You'll have to decide
> which of the three domain names is most important, and use that alone for
> the reverse mapping.
>
> >
> > Thanks again!!!
> > --John
> >
>
> No worries. Hope it helps,
>
> Mike Kennett
> (mike@laurasia.com.au)
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
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?382FD9B2.985E8A8B>