Thanks David.

I don't know what the forwarding bit is all about yet. I sent the wife out 
to the bookstore to pick up Bind and DNS from O'Reilly, so I should be able 
to read up on that any moment now.

Here's what I did.

I ran the graphic utility "bindconf". As a result of my clumsy stumbling 
around it added the following to /etc/named.conf :-

========= <- my delineators for this email, not actually in the file!
zone    "julianop.swdata.com" {
          type master;
         file "julianop.swdata.com.zone";
};
========= <- my delineators for this email, not actually in the file!

And sure enough, it also created /var/named/julianop.swdata.com.zone, which 
is comprised of  :-

========= <- my delineators for this email, not actually in the file!
$TTL 86400
@       IN      SOA     @ root.localhost (
                         3  ; serial
                         28800 ; refresh
                         7200 ; retry
                         604800 ; expire
                         86400 ; ttl
                         )

@       IN      NS      anoka.julianop.swdata.com

pongo.julianop.swdata.com       IN      A       10.0.0.5
sierra.julianop.swdata.com      IN      A       10.0.0.3
monsta.julianop.swdata.com      IN      A       10.0.0.4
anoka.julianop.swdata.com       IN      A       10.0.0.2
========= <- my delineators for this email, not actually in the file!

Now to my amazement, that all works - allowing Winboxes on the LAN to 
resolve IP addresses from IP names (not NETBIOS names - that always works, 
courtesy of NETBIOS under TCP/IP) of other Winboxes on the LAN, AND real 
Internet names out in the wild blue yonder.

My only worry now is if there's a door I haven't closed which is even now 
trying to tell the world about my local LAN!

So this all seems to do the same as your configuration, but I haven't yet 
mentioned the word "forwarder".

Now a DNS guru is going to step up and tell us the pros and cons of our two 
approaches, right? :-)

Julian.
===================
At 01:46 PM 1/5/02 -0500, you wrote:
> > From: "Leonard den Ottolander" <[EMAIL PROTECTED]>
> >
> >               Hi Julian,
> >
> > > My question should have been:- how does the machine running bind satisfy
> > > DNS requests from OTHER machines on local (private) network if it 
> doesn't look
> > > at hosts ?
> >
> >  It looks at the zone files in /var/named, or queries another name server.
>
>
>This long thread has prompted me to set up a caching DNS server (I
>think it works).
>
>About all I changed from a stock Red Hat 7.2 system was part of
>/etc/named.conf so that it now looks like (where XXX.XXX.XXX.XXX are
>my ISP's 2 DNS servers)
>
>options {
>         directory "/var/named";
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>         // query-source address * port 53;
>         forward first;
>         forwarders {
>                 XXX.XXX.XXX.XXX;
>                 XXX.XXX.XXX.XXX;
>             };
>};
>
>-----------------------------------------------------------------
>
>I then put the IP number of my local machine in /etc/resolv.conf (and
>the /etc/resolv.conf of the other machines on my local network) and
>started named. That appears to me all that is necessary - correct?
>
>I think it's working since the second time I run 'host some.name.com',
>the light for the router machine on my switch does not blink so it
>appears to be getting it from the machine running the caching DNS.
>
>My question now is, where does the cache of DNS names reside and how
>is there a limit on how big it will get? Is it in memory or on the
>disk? And of course, if I did something wrong, please let me know :-)
>
>I guess the next step is to make it handle the names of my local
>network, but since I only have 4 machines (plus the router running
>Coyote Linux), keeping a /etc/hosts file on each machine is not very
>difficult
>
>Thanks,
>Dave
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list

----------------------------------------------------------------
Just because I'm paranoid doesn't mean they aren't after me ...

Julian Opificius. ICQ 3268206.
----------------------------------------------------------------



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to