RE: Caching Nameserver

["CHAN Chow Chin, David" <ccchan my ncs-i com>]

Hey Art,

I must admit that I am a newbie at this as well. I don't know how
to configure the DNS very well. I only know enough to make it work. :P
I've been reading the HOWTOs and the knowledge that I get from it
is only that much. I follow word for word. So with that in mind, let's get
started.

The reason that I asked you to include the "forward first" is so that, it
can 
see pple on the outside world. That means you can surf and all that. 
The output you got is correct (in my eyes anyway). That means that the DNS
server that you were forwarding to, returned nothing, meaning that you do
not have a FQDN (Fully Qualified Domain Name) in 208.137.1.115. But you do 
have the domain name within your DNS. That's why it was an
"Non-authoritative answer:"
(that's what I concluded with my experimentation and understanding, ANYONE 
CORRECT ME IF I AM WRONG!!)
try to do a "nslookup localhost", you should get response.

Also note, that your other machines should be configured as DNS enabled with
your IP of your DNS machine. And in your DNS machine, your client machines
should be declared along with their fixed IP, if you have any.

Happy Learning, 
David.:)

-----Original Message-----
From: Art Ross [mailto:aross skyenet net]
Sent: Tuesday, 27 February, 2001 12:22 PM
To: redhat-install-list redhat com
Subject: Re: Caching Nameserver


Chan Chow Chin, David
  I implemented what you suggested and it appears that I might have a
working caching nameserver for my local home network.  I'm a bit confused
about my output from an 'nslookup einstein.linuxindayton.com'.  This is one
of the machines on my home network and has an IP of 192.168.1.3.  In fact
this is the nameserver.  I've included my name.conf and the output from the
nslookup command.
  Any help you can provide will be greatly appreciated.  This DNS stuff is
very interesting.  Unfortunately,  my experience is about two hours so far
and hasn't proven to be adequate.  The named.conf attachment is obvious.
The output file is the output from the nslookup command.
  My big question is the following; "Is the DNS really working?"  If so,
why is my machine being assigned the IP for the DNS of my ISP?
  Thank you for any assistance you can provide.
  Art

"CHAN Chow Chin, David" wrote:

> well, I think you're missing your forwarders in your named.conf file.
> Inside named.conf, under the "options" section, insert:-
>
> forward first;
> forwarders {
>         ip.of.dns.1;
>         ip.of.dns.2;
> };
>
> eg:
> forward first;
> forwarders{
>         161.142.2.17;
> };
>
> hope it helps. :),
> CHAN Chow Chin, David
>
> P.S. Oh! dont' forget to restart named.
>
> -----Original Message-----
> From: Art Ross [mailto:aross skyenet net]
> Sent: Monday, 26 February, 2001 12:43 PM
> To: redhat-install-list redhat com
> Subject: Caching Nameserver
>
> I'm trying to get a caching nameserver setup and operating on my home
> network.  I have downloaded an installed the rpm's from Redhat.  These
> included 'bind' and 'caching-nameserver'.  Using linuxconf, I've added a
> zone for my home network.  When I test it using 'nslookup', it tells me
> that it cannot find host/domain for the nameserver's ip.
>   Also, when I try an nslookup on any of my machines on the home
> network, I cannot find them.  What have I missed?  Will a caching
> nameserver eliminate the need for me to keep all the hosts files on
> every machine current?
>   Any help is appreciated.
>   Art
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list