This file (192.168.0.rev) is the sample reverse map zone file used throughout this Chapter and has the following characteristics.
The Resource Records are all defined separately.
$TTL 86400 ; 24 hours could have been written as 24h $ORIGIN 0.168.192.IN-ADDR.ARPA. @ 1D IN SOA ns1.example.com. hostmaster.example.com. ( 2002022401 ; serial 3H ; refresh 15 ; retry 1w ; expire 3h ; minimum ) ; Name servers for the zone - both out-of-zone - no A RRs required IN NS ns1.example.com. IN NS ns2.smokeyjoe.com. ; server host definitions 1 IN PTR ns1.example.com. 5 IN PTR ns2.example.com. 2 IN PTR www.example.com. ; non server domain hosts 3 IN PTR bill.example.com. 4 IN PTR fred.example.com.
Hosts defined with CNAME Resource Records can have PTR records associated. Host ftp.example.com is CNAMEd in the forward map to host 192.168.0.2 we just happened to only map the www.example.com using a PTR RR for no very god reason. We could have added
2 IN PTR ftp.example.com.
if we had wanted to define both.
Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.
3 reverse map
4 dns types
5 install bind
8 zone records
12 bind api's
13 dns security
bits & bytes
notes & tips
This work is licensed under a Creative Commons License.
If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Firefox