[Cialug] DNS Reverse Lookup

Tom Sellers tomsellers2001 at yahoo.com
Wed May 20 13:07:48 CDT 2009


Thanks for the tips below!  I had already figured out the typo issue which seems to have resolved the problem that I was seeing.  As for the # signs in the file,  I did that because the example I followed did it that way.
  
I can get both forward lookups and reverse lookups as well now.  I'm just experimenting with all the operations now.  My next step is to understand how to implement the ability to dynamically enter IP addresses assigned by my DHCP server into the DNS.  

I still am seeing some unexplained network traffic such as requests to both my DNS server and my outside ISP's DNS at nearly the same time.  I thought it would not send a request to the ISP unless my DNS server could not resolve the name.  Still looking at that issue (from a Windows 98 client workstation) to determine if I have the client set up incorrectly.

I appreciate your responses! I'm always open to suggestions.

--- On Tue, 5/19/09, Aaron Porter <atporter at gmail.com> wrote:

> From: Aaron Porter <atporter at gmail.com>
> Subject: Re: [Cialug] DNS Reverse Lookup
> To: "Central Iowa Linux Users Group" <cialug at cialug.org>
> Date: Tuesday, May 19, 2009, 3:15 PM
> On Mon, May 18, 2009 at 10:14 AM, Tom
> Sellers <tomsellers2001 at yahoo.com>
> wrote:
> > named.conf.local
> > # Our domain zone
> > # For reverse DNS
> 
> Don't use #'s for comments with BIND
> 
> > zone "1.168.192.inaddr.arpa" {
> >   type master;
> >   file "/etc/bind/zones/rev.1.168.192.in-addr.arpa";
> > };
> 
> Looks like a typo here -- inaddr vs in-addr.
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
> 


      


More information about the Cialug mailing list