If you define two A Records with the same IP address then when you come to define the Reverse Mapping zone file using the PTR RR it is perfectly legitimate to define more that one entry for any IP address. Increasingly mail systems as part of an anti-spam strategy and others may perform a dual look-up, IP to name then name to IP. Many mail systems will not correctly handle multiple RR responses (they may only see the first, in this joe entry).
; zone file fragment joe IN A 192.168.254.3 ; joe & www = same ip www IN A 192.168.254.3 ; reverse in-arpa file fragment .3 IN PTR joe.example.com.
In this simple case use of a CNAME record for www could fix the problem.
; zone file fragment joe IN CNAME www www IN A 192.168.254.3 ; reverse in-arpa file fragment .3 IN PTR www.example.com.
If you define multiple A Records for load balancing or to support a round robin strategy the same problem arises. In a dual look-up, IP to name then name to IP, system this will only work for mail in the example below not for any others.
; zone file fragment mail IN A 192.168.254.3 ; round robin IN A 192.168.254.4 IN A 192.168.254.5 ; reverse in-addr.arpa file fragment .3 IN PTR mail.example.com. .4 IN PTR mail1.example.com. .5 IN PTR mail2.example.com.
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