On Thu, Jan 23, 2003 at 03:25:05AM +0100, list@xxxxxxxxxxxx wrote:
> When using the Caching-only Nameserver in the ARM sample config, what should
> the records file localhost.rev look like?
Espen,
An example localhost.rev file is attached. In general, the records
should be PTR resource records for the 0.0.127.in-addr.arpa zone.
RFC1918 has a lot of information that can help you avoid bad DNS
configurations. In particular, there are domains specified on the
list of "should be included in every name server configuration" which
are not included in the example in the BIND v9 ARM. Section 4.1 lists
the following zones:
localhost
0.0.127.in-addr.arpa
255.in-addr.arpa
0.in-addr.arpa
> And am I on the right track with a Caching-only Nameserver if i only
> want my local network to be able to look each other up by hostnames,
> with no outside access?
No. You need an authoritative server to answer queries for the
caching-only name server to put in it's cache. A caching name server
only has as much information as it is able to obtain from other
sources. If you have data inside of your network which the rest of
the Internet does not know about, you need an authoritative server to
answer queries about that data. You (also) need to configure your
recursive (caching-only) server to request that data from your
authoritative server.
-rob
-- Attached file included as plaintext by Ecartis --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+MXyAOVBTTvic5hMRAnLCAKDgF5bTLeijWA/SEnTLh7KgY8KIxwCgjPeb
hFrGNw9Wi9yfWa38kdPPfoM=
=g7bm
-----END PGP SIGNATURE-----
|
