Automatic Reverse DNS entries + Automatic "Forward" DNS Entries
Mike
mike at kamloopsbc.com
Fri Jan 16 00:20:48 UTC 2004
Hello,
I'm using Bind 9.2.1 and after leafing through the book and some
sites, I'm still not sure if/how I can do the following:
I have 2 subnets (example IP's only. Real IP's are used in our
network):
192.168.0.1/25
192.168.5.128/25
We have an assortment of servers running, and want our nameservers to
provide reverse DNS entries in the following format for each IP we
have. For example:
0.1.mydomain.com --> 192.168.0.1 --> 0.1.mydomain.com
0.2.mydomain.com --> 192.168.0.2 --> 0.2.mydomain.com
0.3.mydomain.com --> 192.168.0.3 --> customerdomain.com -->
192.168.0.3
0.4.mydomain.com --> 192.168.0.4 --> 0.4.mydomain.com
0.5.mydomain.com --> 192.168.0.5 --> 0.5.mydomain.com
0.6.mydomain.com --> 192.168.0.6 --> 0.6.mydomain.com
So if you nslookup 0.1.mydomain.com it points to 192.168.0.1
If you nslookup 192.168.0.1 it points to 0.1.mydomain.com
NOTE: There is of course, an exception.
If you nslookup 0.3.mydomain.com it points to 192.168.0.3
If you nslookup 192.168.0.3 it points to customerdomain.com
If you nslookup customerdomain.com it points to 192.168.0.3
(essentially the first of this set is not needed, but keeps things
standard)
Basically, I know how to 'manually' set this for all DNS and rDNS
entries, but what I'm wondering is if there is a way for me to have an
entry in db.mydomain.com that says: From 192.168.0.1-->128 =
xxx.xxx.mydomain.com
Then on the reverse DNS for db.192.168.213 have a single entry that
says: From 192.168.0.1-->128 = xxx.xxx.mydomain.com unless
192.168.xxx.xxx has a valid rDNS entry.
Hopefully that makes sense. This would definitely make things easier
when adding more subnets.
More information about the bind-users
mailing list