Some hints on DNS config? [part 2]

Kimi Ostro kimimeister at gmail.com
Thu Jul 14 12:33:41 UTC 2005


On 7/14/05, Brad Knowles <brad at stop.mail-abuse.org> wrote:
>         Caching is turned on by default.  If you want caching, then all
> you have to do is make sure you don't turn it off.
>=20

Arghhh!! I think there is some distortion between my fingers hitting
the keyboard, and what is being sent to the list. Sorry.

I know caching is what BIND does by default out of the box, which is
pretty much crystal clear.

So for my caching name servers named.conf I have:

include "etc/rndc.key"

options {
 directory "/var/named";
 allow-transfer{"none";};
};

acl "internal" {
 "localhost";
 "localnets";
};

view "internal" {
 match-clients { "internal"; };
 match-destinations { "internal"; };
 allow-recursion { "internal"; };

 zone "." {
  type hint;
  file "standard/root.hintss";
 };
 zone "localhost" in{
  type master;
  file "master/localhost";
 };
 zone "0.0.127.in-addr.arpa" in{
  type master;
  file "master/localhost.rev";
 };
};
// EOF

fine, great. now a master authoratative named.conf:

include "etc/rndc.key"

options {
 directory "/var/named";
 recursion no;
 allow-transfer{none;};
};

acl "internal" {
 "localhost";
 "localnets";
};

view "internal" {
 match-clients { "internal"; };
 match-destinations { "internal"; };

 zone "example.com" in{
  type master;
  file "master/master.example.com";
  allow-transfer { 192.168.20.10; 192.168.20.20; );
 };
 zone "20.168.192.IN-ADDR.ARPA" in{
  type master;
  file "master/192.168.20.rev";
 };
 zone "localhost" in{
  type master;
  file "master/localhost";
 };
 zone "0.0.127.in-addr.arpa" in{
  type master;
  file "master/localhost.rev";
 };
};
// EOF

now a slave authoratative:

include "etc/rndc.key"

options {
 directory "/var/named";
 recursion no;
 allow-transfer{none;};
};

acl "internal" {
 "localhost";
 "localnets";
};

view "internal" {
 match-clients { "internal"; };
 match-destinations { "internal"; };

 zone "example.com" in{
  type slave;
  file "slave/example.com";
  masters { 192.168.20.30; };
 };
 zone "20.168.192.IN-ADDR.ARPA" in{
  type slave;
  file "slave/192.168.20.rev";
  masters { 192.168.20.30; };
 };
 zone "localhost" in{
  type master;
  file "master/localhost";
 };
 zone "0.0.127.in-addr.arpa" in{
  type master;
  file "master/localhost.rev";
 };
};
// EOF

Great. there probably some "holes" to be picked.

It isn't this part of the config I am having problems with, what I am
trying to establish is this; *who* (nameservers? resolvers?) needs to
know about the caching nameserver(s)?

Because at the moment I cannot see how the cache is to be used, if
no-one knows about it?

Once this part is figured out, everything about DNS will be a walk in the p=
ark.

Regards,

PS: also found http://www.zytrax.com/books/dns/ quite helpful :)
--=20
Kimi



More information about the bind-users mailing list