Sure, another zone file.
Reverse lookups for local addresses are your responsibility.
Your first note cited M.ROOT-SERVERS.NET (by IPv6 addr).
That server would never be able to resolve 172.n.n.n with a name
that matches your internal network. But if your local BIND owned that
zone it would not have forwarded the request.
I'll expose some of my personal network:
I use 192.168.29.x and have /var/named/master/192.168.29
(no further extension, but some people like to add ".db").
That gets mapped with this stanza in /etc/named.conf ...
zone "29.168.192.in-addr.arpa" in {
type master;
file "master/192.168.29";
};
(Previous global statement 'directory "/var/named";' sets the prefix.)
Take note of the reversal of IPv4 octets for the IN-ADDR.ARPA pseudo
domain.
An example line from the zone file is ...
11 IN PTR jeremiah.casita.net.
Thus "192.168.29.11" resolves to "jeremiah.casita.net".
Works.
Reversing is fairly easy, use "PTR" instead of "A" or "AAAA".
Am guessing you have a solid handle on the other statements in zone
files, but if you need a hand, just holler.
-- R; <><
On Thu, 2015-10-29 at 13:36 -0400, Michael Weiner wrote:
> Agreed, which I do have that. But, 172. is my local network for my laptop.
> Do I need another zone for local IP's?
>
> On Thu, Oct 29, 2015 at 1:33 PM, Mark Post <mp...@suse.com> wrote:
>
> > >>> On 10/29/2015 at 01:29 PM, Michael Weiner <mwei...@infinite-blue.com>
> > wrote:
> > > Do I need a zone for my local network being 172.16.1.*?
> > >
> > > Oct 29 08:52:41 dnsserver named[25110]: client 10.100.0.191#50757: query:
> > > 182.1.16.172.in-addr.arpa IN PTR +
> > > Oct 29 08:52:41 dnsserver named[25110]: client 10.100.0.191#50757: query
> > > (cache) '182.1.16.172.in-addr.arpa/PTR/IN' denied
> > > Oct 29 08:52:50 dnsserver named[25110]: client 10.100.0.191#43924: query:
> > > 182.1.16.172.in-addr.arpa IN PTR +
> > > Oct 29 08:52:50 dnsserver named[25110]: client 10.100.0.191#43924: query
> > > (cache) '182.1.16.172.in-addr.arpa/PTR/IN' denied
> >
> > I have always considered missing reverse lookups to be misconfiguration.
> > If you have control over the server, you should have both forward and
> > reverse lookups defined.
> >
> >
> > Mark Post
> >
> > ----------------------------------------------------------------------
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > ----------------------------------------------------------------------
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
>
>
>
> --
> Michael Weiner
> Systems Admin
> Infinity Systems Software, Inc.
> One Penn Plaza Suite 2010
> New York, NY 10119
> o: (646) 405-9300
> c: (845) 641-0517
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
