Date: Sun, 21 Jun 1998 02:22:43 +1000 From: justin <marcus@sensation.net.au> To: questions@FreeBSD.ORG, root@isc.org Subject: help please - bind8 Message-ID: <358BE1D1.6C32FBEA@sensation.net.au>
index | next in thread | raw e-mail
[-- Attachment #1 --]
hey :)
i was wondering if you could please help me with bind8??
ok well i can't seem to get tcp to listen on port 53, i HAVE read ALL
the faqs docs and everything about it, i have added to my named.conf all
the lines it should like
listen-on port 53 { any; }; and allow-transfer { any; }; and pretty much
everything it ses.
udp is working, but unfortunaly tcp is not. I have tried like every
possible thing in named.conf but tcp still fails to listen. Is there
something i should to make sure tcp on port 53 can work ??? because i no
/etc/services is fine...
is there some way to make tcp listen on port 53, using some command.
please help me, like i said i've read everything and done what they said
and its still no good.
thanks heaps :)
from justin !!
p.s i have attached my named.conf just to show u, thanks :)
[-- Attachment #2 --]
options {
directory "/etc/namedb"; // use current directory
named-xfer "/usr/libexec/named-xfer"; // _PATH_XFER
pid-file "/var/run/named.pid"; // _PATH_PIDFILE
check-names master fail;
check-names slave warn;
check-names response ignore;
datasize default;
stacksize default;
coresize default;
files unlimited;
recursion yes;
fetch-glue yes;
fake-iquery no;
notify yes; // send NOTIFY messages. You can set
// notify on a zone-by-zone
// basis in the "zone" statement
// see (below)
auth-nxdomain yes; // always set AA on NXDOMAIN.
// don't set this to 'no' unless
// you know what you're doing -- older
// servers won't like it.
multiple-cnames yes; // if yes, then a name my havemore
// than one CNAME RR. This use
// is non-standard and is not
// recommended, but it is available
// because previous releases supported
// it and it was used by large sites
// for load balancing.
allow-query { any; };
allow-transfer { any; };
transfers-in 10; // DEFAULT_XFERS_RUNNING, cannot be
// set > than MAX_XFERS_RUNNING (20)
transfers-per-ns 20; // DEFAULT_XFERS_PER_NS
transfers-out 10; // not implemented
max-transfer-time-in 120; // MAX_XFER_TIME; the default number
// of minutes an inbound zone transfer
// may run. May be set on a per-zone
// basis.
transfer-format one-answer;
query-source address * port 53;
};
zone "." {
type hint;
file "root.cache";
};
zone "warp-9.ml.org" {
type master; // what used to be called "primary"
file "warp-9.db";
check-names fail;
allow-update { none; };
allow-transfer { any; };
allow-query { any; };
notify yes;
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "127.0.0";
check-names fail;
allow-update { none; };
allow-transfer { none; };
allow-query { any; };
max-transfer-time-in 120;
};
/*
acl can_query { any; any; }; // network 1.2.3.0 mask 255.255.255.0
// is disallowed; rest are OK
acl can_axfr { any; can_query; }; // host 1.2.3.4 and any hostallowed
// by can_query are OK
*/
/*****
key sample_key { // for TSIG; supported by parser
algorithm hmac-md5; // but not yet implemented in the
secret "your secret here"; // rest of the server
};
key key2 {
algorithm hmac-md5;
secret "ereh terces rouy";
};
*****/
/*****
server { any; }; {
warp-9.ml.org no; // if yes, we won't query or listen
// to this server
transfer-format one-answer; // set transfer format for this
// server (see the description of
// 'transfer-format' above)
// if not specified, the global option
// will be used
transfers 0; // not implemented
keys { sample_key; key2; }; // for TSIG; supported by the parser
// but not yet implemented in the
// rest of the server
};
*****/
logging {
/*
* All log output goes to one or more "channels"; you can make as
* many of them as you want.
*/
channel syslog_errors { // this channel will send errors or
syslog user; // or worse to syslog (user facility)
severity error;
};
/*
* Channels have a severity level. Messages at severity levels
* greater than or equal to the channel's level will be logged on
* the channel. In order of decreasing severity, the levels are:
*
* critical a fatal error
* error
* warning
* notice a normal, but significant event
* info an informational message
* debug 1 the least detailed debugging info
* ...
* debug 99 the most detailed debugging info
*/
/*
* Here are the built-in channels:
*
* channel default_syslog {
* syslog daemon;
* severity info;
* };
*
* channel default_debug {
* file "named.run";
* severity dynamic; // this means log debugging
* // at whatever debugging level
* // the server is at, and don't
* // log anything if not
* // debugging
* };
*
* channel null { // this is the bit bucket;
* file "/dev/null" // any logging to this channel
* // is discarded.
* };
*
* channel default_stderr { // writes to stderr
* file "<stderr>"; // this is illustrative only;
* // there's currently no way
* // of saying "stderr" in the
* // configuration language.
* // i.e. don't try this at home.
* severity info;
* };
*
* default_stderr only works before the server daemonizes (i.e.
* during initial startup) or when it is running in foreground
* mode (-f command line option).
*/
/*
* There are many categories, so you can send the logs
* you want to see wherever you want, without seeing logs you
* don't want. Right now the categories are
*
* default the catch-all. many things still
* aren't classified into categories, and
* they all end up here. also, if you
* don't specify any channels for a
* category, the default category is used
* instead.
* config high-level configuration file
* processing
* parser low-level configuration file processing
* queries what used to be called "query logging"
* lame-servers messages like "Lame server on ..."
* statistics
* panic if the server has to shut itself
* down due to an internal problem, it
* logs the problem here (as well as
* in the problem's native category)
* update dynamic update
* ncache negative caching
* xfer-in zone transfers we're receiving
* xfer-out zone transfers we're sending
* db all database operations
* eventlib debugging info from the event system
* (see below)
* packet dumps of packets received and sent
* (see below)
* notify the NOTIFY protocol
* cname messages like "XX points to a CNAME"
* security approved/unapproved requests
* os operating system problems
* insist consistency check failures
* maintenance periodic maintenance
* load zone loading
* response-checks messages like
* "Malformed response ..."
* "wrong ans. name ..."
* "unrelated additional info ..."
* "invalid RR type ..."
* "bad referral ..."
*/
category parser {
syslog_errors; // you can log to as many channels
default_syslog; // as you want
};
category lame-servers { null; }; // don't log these at all
channel moderate_debug {
severity debug 3; // level 3 debugging to file
file "/var/log/named.log"; // foo
print-time yes; // timestamp log entries
print-category yes; // print category name
print-severity yes; // print severity level
/*
* Note that debugging must have been turned on either
* on the command line or with a signal to get debugging
* output (non-debugging output will still be written to
* this channel).
*/
};
/*
* If you don't want to see "zone XXXX loaded" messages but do
* want to see any problems, you could do the following.
*/
channel no_info_messages {
syslog;
severity notice;
};
category load { no_info_messages; };
/*
* You can also define category "default"; it gets used when no
* "category" statement has been given for a category.
*/
category default {
default_syslog;
moderate_debug;
};
/*
* If you don't define category default yourself, the default
* default category will be used. It is
*
* category default { default_syslog; default_debug; };
*/
/*
* If you don't define category panic yourself, the default
* panic category will be used. It is
*
* category panic { default_syslog; default_stderr; };
*/
/*
* Two categories, 'packet' and 'eventlib', are special. Only one
* channel may be assigned to each of them, and it must be a
* file channel. If you don't define them yourself, they default to
*
* category eventlib { default_debug; };
*
* category packet { default_debug; };
*/
};
//include "filename"; // can't do within a statement
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?358BE1D1.6C32FBEA>