Date: Thu, 29 Apr 1999 13:55:46 -0400 From: John.Shue@symmetron.com (John A. Shue) To: <davebullock@dwindledistribution.com>, <questions@freebsd.org> Subject: RE: named Message-ID: <000501be9269$8263c2f0$02baefce@mail.symmetron.com> In-Reply-To: <9904299254.AA925407555@mailhost.worldind.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I think that your directory line in named.boot shouldn't end with a slash.
Try:
directory /etc/namedb
as the first line of your named.boot file.
-john
---------------
John A. Shue
4000 Legato Road, Suite 600
Fairfax, VA 22033
(703) 591-5559
(703) 591-6337 FAX
-----Original Message-----
From: owner-freebsd-questions@FreeBSD.ORG
[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of
davebullock@dwindledistribution.com
Sent: Thursday, April 29, 1999 2:48 PM
To: questions@freebsd.org
Subject: named
I am having trouble setting up named. The error message is as follows:
Apr 27 17:17:25 eqp2 named[26555]: starting. named 8.1.2 Mon Feb 15 10:10:31
GMT 1999 jkh@usw3.freebsd.org:/usr/obj/usr/src/usr.sbin/named
Apr 27 17:17:25 eqp2 named[26555]: /etc/namedb/named.boot:1: syntax error near
directory
Apr 27 17:17:25 eqp2 named[26556]: Ready to answer queries.
I am following the instuictions in the book but they don't seem to remedy the
problem... what am i doing worng.
here is my db.eecue.com file:
eecue.com. IN SOA eQP2.eecue.com. root.eecue.com. (
19990422511
86400
7200
8640000
86400 )
eQP2 IN A 209.150.72.59
video IN A 90.0.0.25
IN NS ns
IN NS ns1
ns IN A 209.150.72.59
ns1 IN A 207.67.168.40
IN MX 50 eQP2.eecue.com.
IN MX 100 mal.cyberg8t.com.
here is eecue-reverse:
/*
zone "eecue.com" {
type slave;
file "db.eecue.com";
masters {
207.67.168.40;
};
};
zone "168.67.207.in-addr.arpa" {
type slave;
file "172.68.207.in-addr.arpa.bak";
masters {
209.150.72.59;
};
};
*/
here is named.boot:
directory /etc/namedb/
;type domain source host/file backup file
cache . named.root
primary eecue.com db.eecue.com
primary 72.150.209.IN-ADDR.ARPA eecue-reverse
forwarders 207.67.168.40 207.67.172.150
here is named.conf:
// $Id: named.conf,v 1.2 1998/05/11 11:26:28 peter Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy
// details of how DNS is working. Even with simple mistakes, you can
// break connectivity for affected parties, or cause huge amount of
// useless Internet traffic.
options {
directory "/etc/namedb";
// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
forwarders {
207.67.168.40;
};
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;
};
/*
// Note: the following will be supported in a future release.
host { any; } {
topology {
127.0.0.0/8;
};
};
*/
host { any; } {
topology {
127.0.0.0/8;
};
};
*/
// Setting up secondaries is way easier and the rough picture for this
// is explained below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// into your /etc/resolv.conf so this server will be queried first.
// Also, make sure to enable it in /etc/rc.conf.
/*
zone "." {
type hint;
file "named.root";
};
zone "72.150.209.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
*/
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone where your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is the first bytes of the respective IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to setup a primary zone, better make sure you fully
// understand how DNS and BIND works, however. There are sometimes
// unobvious pitfalls. Setting up a secondary is comparably simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
/*
zone "eecue.com" {
type slave;
file "db.eecue.com";
masters {
207.67.168.40;
};
};
zone "168.67.207.in-addr.arpa" {
type slave;
file "172.68.207.in-addr.arpa.bak";
masters {
209.150.72.59;
};
};
*/
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?000501be9269$8263c2f0$02baefce>