From: gracecott@sancharnet.in
To: linux-admin@vger.kernel.org
Subject: Re:setting up bind(sorry)
Date: Fri, 09 Jul 2004 12:19:12 +0530 (GMT+05:30) [thread overview]
Message-ID: <33525726.1089355752341.JavaMail.nobody@ndl1pp2-a-fixed> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hello again :-( ,
I did what Ahsan told me to do
and ran named-checkzone on db.pcm.com
and it gives me an error:
no current owner name
and no OK (obviously) after finising up.
I would've read up more before I asked this but
I have 4 days before my 4 Sem., exams and really can't read up
too much now and would like to get this up before D-day.
Thanx in advance,
Joy.M.M
[-- Attachment #2: Attached file: db.192 --]
[-- Type: application/octet-stream, Size: 354 bytes --]
$TTL 604800
@ IN SOA parrot.pcm.com. root.pcm.com.(
204774084 ;serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ NS parrot.pcm.com
16.2.168 IN PTR parrot.pcm.com.
11.2.168 IN PTR eagle.pcm.com.
14.2.168 IN PTR swan1.pcm.com.
15.2.168 IN PTR swan2.pcm.com.
13.2.168 IN PTR peacock.pcm.com.
[-- Attachment #3: Attached file: db.pcm.com --]
[-- Type: application/octet-stream, Size: 436 bytes --]
$TTL 86400
@ 1D IN SOA parrot.pcm.com. root.pcm.com.(
20384765 ;serial
10000 ;refresh
500 ;retry
2419200 ; expire
604800 );negative TTL
;
@ 604800 IN NS parrot.pcm.com.
parrot.pcm.com. 604800 IN A 192.168.2.16
eagle.pcm.com. 604800 IN A 192.168.2.11
swan1.pcm.com. 604800 IN A 192.168.2.14
swan2.pcm.com. 604800 IN A 192.168.2.15
peacock.pcm.com. 604800 IN A 192.168.2.13
pcm.com. 7155 IN A 209.233.130.34
[-- Attachment #4: Attached file: named.conf --]
[-- Type: application/octet-stream, Size: 1085 bytes --]
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
//zone "com" { type delegation-only; };
zone "net" { type delegation-only; };
zone "pcm.com" IN{
type master;
file "/etc/bind/db.pcm.com";
};
zone "192.in-addr.arpa"{
type master;
file "/etc/bind/db.192";
};
next reply other threads:[~2004-07-09 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 6:49 gracecott [this message]
2004-07-10 3:28 ` Re:setting up bind(sorry) Richard Nairn
2004-07-10 7:27 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33525726.1089355752341.JavaMail.nobody@ndl1pp2-a-fixed \
--to=gracecott@sancharnet.in \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).