incomprehensible error message starting 9.2.0/FreeBSD4.3

Marc Kandel mkandel at ttlc.net
Wed Aug 7 16:18:25 UTC 2002


named-checkconf returned 0 when i ran it against my bad named.conf. =20

--marc


> -----Original Message-----
> From: Pete Ehlke [mailto:pde at ehlke.net]
> Sent: Wednesday, August 07, 2002 12:13 PM
> To: Marc Kandel
> Cc: phn at icke-reklam.ipsec.nu; comp-protocols-dns-bind at isc.org
> Subject: Re: incomprehensible error message starting 9.2.0/FreeBSD4.3
>=20
>=20
> On Wed, Aug 07, 2002 at 12:07:24PM -0400, Marc Kandel wrote:
> >=20
> > i did find my problem though ... someone had added an entry=20
> in ALL CAPS =3D
> > for a domain we already had without caps (ie. we had biz.com and =3D
> > BIZ.COM) so named was choking on the duplicate entry.  i=20
> had written a =3D
> > script to look at named.conf, grab all the domainnames=20
> (from the zone =3D
> > entries) to see if there were any duplicates ... as far as=20
> UNIX goes, =3D
> > the case sensitivity caused no domains to show twice ... a=20
> "grep -i" =3D
> > would have saved me a lot of time ...
> >=20
> named-checkconf is your friend. Consider processing your named.conf
> through it first, before starting or reconfiguring your=20
> server. There's
> really no reason at all any more for name servers to refuse=20
> to start due
> to config or zone file errors.
>=20
> -Pete
>=20


More information about the bind-users mailing list