|
|
 |
bind 9
date posted 21st June 2002 13:24
This is a multi-part message in MIME format.
------=_NextPart_000_0115_01C21927.83BC2640
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hi,
Thanks for all your help on bind 9.
I've changed pz/127.0.0 like you say but still get the same error.
I've included the 2 files, would it be possible for you top have a look at
them as its really doing me nut in why it won't run properly.
I've followed the protocol at www.linix-sxs.org/bind9.html is this right?
can you suggest another/better way? or is this how you do it?
It instructs to create a pz/127.0.0 file which obviously is the loopback,
but it also suggests to create a 192.168.1 file which I'm unsure of why this
number? The IP address of the machine bind is running on is 192.168.254.209
and the hostname is ns1.pserve.co.uk.
i've also included my named.conf file.
it would highly highly highly appreciated if anyone could shed any light on
it!!!
Robin Garbutt
Portfolio Art & Design Ltd
Tel - +44 (0) 1204 383822
Fax - +44 (0) 1204 383866
Mob - +44 (0) 7811 185490
e-mail - [EMAIL REMOVED]
For further information please visit us at :-
www.portfoliodesign.net
The contents of this e-mail are confidential to the ordinary user of the
e-mail address to which it was addressed and may also be privileged. If you
are not the addressee of this e-mail you may not copy, forward, disclose or
otherwise use it or any part of it in any form whatsoever. If you have
received this e-mail in error please e-mail the sender.
------=_NextPart_000_0115_01C21927.83BC2640
Content-Type: application/octet-stream;
name="127.0.0"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="127.0.0"
=0A=
$TTL 1D=0A=
=0A=
@ IN SOA localhost. root.localhost. (=0A=
2002060900 ;serial (d. adams)=0A=
3600 ;refresh=0A=
900 ;retry=0A=
3600000 ;expiry=0A=
3600 ) ;minimum=0A=
=0A=
1D IN NS localhost.=0A=
1 1D IN PTR localhost.=0A=
------=_NextPart_000_0115_01C21927.83BC2640
Content-Type: application/octet-stream;
name="192.168.1"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="192.168.1"
$TTL 3D
@ IN SOA localhost. root.localhost. (
199609206 ;serial (d. adams)
8H ;refresh
2H ;retry
4W ;expiry
1D ) ;minimum
1D IN NS localhost.
1 1D IN PTR localhost.
localhost A 127.0.0.1
router A 192.168.254.209
localhost. A 192.168.254.209
www A 192.168.254.209
------=_NextPart_000_0115_01C21927.83BC2640
Content-Type: application/octet-stream;
name="named.conf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="named.conf"
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.4 2001/12/05 22:10:12 cjc =
Exp $=0A=
//=0A=
// Refer to the named.conf(5) and named(8) man pages for details. If=0A=
// you are ever going to setup a primary server, make sure you've=0A=
// understood the hairy details of how DNS is working. Even with=0A=
// simple mistakes, you can break connectivity for affected parties,=0A=
// or cause huge amount of useless Internet traffic.=0A=
//=0A=
//options -- point named at the appropriate files=0A=
=0A=
options {=0A=
directory "/var/named";=0A=
allow-transfer { any; };=0A=
//allow-v6-synthesis { any;};=0A=
// check-names master warn;=0A=
// memstatistics-file "named.memstats";=0A=
datasize 20M;=0A=
dump-file "named_dump.db";=0A=
interface-interval 0;=0A=
listen-on { any ; };=0A=
max-cache-size 20M;=0A=
pid-file "/var/run/named.pid";=0A=
query-source address * port 53;=0A=
statistics-file "named.stats";=0A=
// use-id-pool yes;=0A=
version "This is not the port you're looking for.";=0A=
zone-statistics yes;=0A=
};=0A=
controls {=0A=
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };=0A=
};=0A=
key "rndc-key" {=0A=
algorithm hmac-md5;=0A=
secret "aHVz";=0A=
};=0A=
logging {=0A=
channel named_info {=0A=
syslog;=0A=
print-category yes;=0A=
print-severity yes;=0A=
print-time yes;=0A=
};=0A=
category client { named_info; };=0A=
category config { named_info; };=0A=
category database { named_info; };=0A=
category default { named_info; };=0A=
category general { named_info; };=0A=
//category lame-servers { null; };=0A=
category notify { named_info; };=0A=
category network { named_info; };=0A=
category resolver { named_info; };=0A=
category security { named_info; };=0A=
category update { named_info; };=0A=
category queries { named_info; };=0A=
category xfer-out { named_info; };=0A=
};=0A=
=0A=
view "external-chaos" chaos {=0A=
match-clients { any; };=0A=
recursion no;=0A=
zone "." {=0A=
type hint;=0A=
//this causes a null response to queries about the bind version=0A=
file "/dev/null";=0A=
};=0A=
};=0A=
=0A=
view "external" {=0A=
match-clients { any; };=0A=
zone "." {=0A=
type hint;=0A=
file "root.hints";=0A=
};=0A=
};=0A=
=0A=
view "external-127" {=0A=
match-clients { any; };=0A=
zone "0.0.127.in-addr.arpa" {=0A=
type master;=0A=
file "pz/127.0.0";=0A=
allow-update {=0A=
none;=0A=
};=0A=
};=0A=
};=0A=
=0A=
view "external-192" {=0A=
match-clients { any; };=0A=
zone "1.168.192.in-addr.arpa" {=0A=
type master;=0A=
file "pz/192.168.1";=0A=
allow-update {=0A=
none;=0A=
};=0A=
};=0A=
};=0A=
=0A=
// In addition to the "forwarders" clause, you can force your name=0A=
// server to never initiate queries of its own, but always ask its=0A=
// forwarders only, by enabling the following line:=0A=
//=0A=
// forward only;=0A=
=0A=
// If you've got a DNS server around at your upstream provider, enter=0A=
// its IP address here, and enable the line below. This will make you=0A=
// benefit from its cache, thus reduce overall DNS traffic in the =
Internet.=0A=
=0A=
=0A=
------=_NextPart_000_0115_01C21927.83BC2640--
|
|
|
