From: joy <gracecott@sancharnet.in>
To: linux-admin@vger.kernel.org
Subject: setting up bind
Date: Fri, 02 Jul 2004 19:42:55 +0530 [thread overview]
Message-ID: <40E56D67.3010204@sancharnet.in> (raw)
Hi everyone,
Sorry for the long post , but I don't think I could've done it in less.....
I'm trying to setup a name server using bind 9 and have run into a
peculiar problem:
The computers on my lan have hostnames like xxx.pcm.com and this
nameserver is an internal one to
serve these machines.
so i wrote a zone for "pcm.com" and made my server the master for the zone.
the records look somthing like this:
xxx.pcm.com IN A 192.xx.xx.xx (is this right?)
to test it ,I ran dig for one of the hostnames and it appears that
there is already a master for pcm.com somewhere else
which (obviously) does not have a record for my machine.
To make my machine not query other nameservers, I made my nameserver the
only one in resolv.conf.
and made it a slave for queries on zone "com" with the main NS outside
as the master.
however this causes dig to give a timed out error.
Am I missing something here?
What I feel is that dig first tries to resolve "." (root)zone and is
not able to because my NS does not hold any info on it.
Am I right in thinking so?
My NS had a different hostname before and dig could return a valid
ip.However, my employer insists
that the hostnames end with pcm.com (for some administrtive reasons )
So, my question is,
how do I make dig search for xxx.pcm.com on my NS before forwarding it
to the outside?
Also,
Do I need to to write the PTR records for every A record I add?
Thanx (a lot ) in advance,
Joy.M.M
next reply other threads:[~2004-07-02 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 14:12 joy [this message]
2004-07-02 22:23 ` setting up bind Glynn Clements
2004-07-07 7:00 ` Ahsan Ali
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 7:21 gracecott
2004-07-08 7:34 ` setting " Ahsan Ali
2004-07-08 7:51 gracecott
2004-07-09 3:57 ` Glynn Clements
2004-07-10 7:02 ` setting " joy
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=40E56D67.3010204@sancharnet.in \
--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).