although in several posts it is mentioned that your ISP manages the PTR records for your IP, ISPConfig does generate a reverse zone file for bind. However the format is Code: GNU nano 1.3.12 File: reverse_zone.in-addr.arpa.master $TTL 86400 @ IN SOA {SERVER_BIND_NS1_DEFAULT}. hostmaster.{SERVER_DOMAIN}. ( {SERIAL} ; serial, todays date + todays serial # 28800 ; Refresh 7200 ; Retry 604800 ; Expire 86400) ; Minimum TTL NS {SERVER_BIND_NS1_DEFAULT}. NS {SERVER_BIND_NS2_DEFAULT}. <!-- BEGIN DYNAMIC BLOCK: reverse_records --> {IP_ENDE} PTR {DNS_SOA}. <!-- END DYNAMIC BLOCK: reverse_records --> ;;;; MAKE MANUAL ENTRIES BELOW THIS LINE! ;;;; in order to correctly resolve, my ISP recommended to add IN like Code: {IP_ENDE} IN PTR {DNS_SOA}. would that make sense?
I guess you mix up the domain PTR records and the IP reverse records. The IP reverse records can only managed by your ISP because you are normally not authoritive for a IP, the domain PTR records where managed by ISPConfig automatically.