CentOS - Jan 2012 - DNS and Reverse Adresses

Hi,

I do have a domain and a couple of different ip networks.

E.g. domainname.de and 172.17.0.0/16 and 192.168.200.0/24

In our old dns files I only have a reverse master zone for the
172.17.-lans, but also 192.168.200.x addresses in the forward zone config.

My question: dose maybe someone forgot the 192.168.200.x reverse zone
files and config and can I just create a file like that for the 172.17
hosts and adding the config for the reverse zone to my named.conf?

Any suggestions are welcome. Regards.

	G?tz who has to deal with some very old horses ... :)
-- 
G?tz Reinicke
IT-Koordinator

Tel. +49 7141 969 420
Fax  +49 7141 969 55 420
E-Mail goetz.reinicke at filmakademie.de

Filmakademie Baden-W?rttemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016

Vorsitzender des Aufsichtsrats:
J?rgen Walter MdL
Staatssekret?r im Ministerium f?r Wissenschaft,
Forschung und Kunst Baden-W?rttemberg

Gesch?ftsf?hrer:
Prof. Thomas Schadt

Hi G?tz, 
> My question: dose maybe someone forgot the 192.168.200.x reverse zone
> files and config
probably. 
> and can I just create a file like that for the 172.17
> hosts and adding the config for the reverse zone to my named.conf?
Yes, *if* you either have the only DNS in your network (not a hierarchically
lower level that gets its domains delegated from the next higher level) or the
200.168.192.in-addr.arpa domain has been delegated to you. Having the authority
over the 'domainname.de' domain and hostnames that resolve to
192.168.200.x addresses does not automatically mean that you have authority over
the said reverse lookup domain as well.

You can check whether some other name server resolves 192.168.200.x addresses by
entering

  dig -x 192.168.200.x

If you get NXDOMAIN, there is probably either more mis-configuration around
(happens frequently in my experience), or there actually is no other server that
could provide reverse lookup. You can also try to check the delegation of the
200.168.192.in-addr.arpa address by issuing the command

  dig 200.168.192.in-addr.arpa NS

The pointers you get in return (if any) should give you an indication whether
you have authority to resolve reverse lookups for 192.168.200.x addresses.

Again, if yours is/are the only or main authoritative DNS server(s) in the
(internal) network, these considerations do not apply.

Viele Gr??e, 

  Peter.