I am having a hell of a time getting our PTR record right.

Our current PTR zone looks like this:

$ttl 38400
@   IN  SOA ns1.domain.com. admin.domain.com. (
            1268669139
            10800
            3600
            604800
            38400 )

xxx.xxx.xxx.in-addr.arpa.   IN  NS  ns2.domain.com.
xxx.xxx.xxx.in-addr.arpa.   IN  NS  ns1.domain.com.
97 IN PTR mail.domain.com.
xxx.xxx.xxx.xxx.in-addr.arpa.   IN  PTR mail.domain.com.
97.96/28. IN PTR mail.domain.com

For some reason the only thing that works is the 97.96/28. When this line is in there it actually says I have a PTR record when reporting from intodns.com. If I remove that line, it says I have no PTR.

I have followed instructions from http://www.philchen.com/2007/04/04/configuring-reverse-dns and when I follow those instructions intodns.com says I have no PTR.

When it does work with the line 97.96/28., the PTR kicks back as (from intodns.com) :

97.xxx.xxx.xxx.in-addr.arpa ->  mail.domain.com.xxx.xxx.xxx.in-addr.arpa

Which is, to my knowledge, an incorrect PTR. I want it to just kick back as mail.domain.com, without the xxx.xxx.xxx.in-addr.arpa extension.

I have tried everything I can think of but I can't fix it. I can't help but think it's one of those things that is so stupid and simple I'm going to do the ol'facepalm.

Any help is greatly appreciated. Thanks!

In the event that the domain zone is needed, here it is:

$ttl 38400
@   IN  SOA domain.com. [email protected]. (
            1265221037
            10800
            3600
            604800
            38400 )
domain.com. IN  A   xxx.xxx.xxx.xxx
www.domain.com. IN  A   xxx.xxx.xxx.xxx
ftp.domain.com. IN  A   xxx.xxx.xxx.xxx
m.domain.com.   IN  A   xxx.xxx.xxx.xxx
localhost.domain.com.   IN  A   127.0.0.1
webmail.domain.com. IN  A   xxx.xxx.xxx.xxx
admin.domain.com.   IN  A   xxx.xxx.xxx.xxx
mail.domain.com.    IN  A   xxx.xxx.xxx.xxx
domain.com. IN  MX  5 mail.domain.com.
domain.com. IN  TXT "v=spf1 a mx a:domain.com ip4:xxx.xxx.xxx.xxx ?all"
domain.com. IN  NS  ns1
domain.com. IN  NS  ns2
ns1 IN  A   xxx.xxx.xxx.xxx
ns2 IN  A   xxx.xxx.xxx.xxx

Any double entries in different formats were part of my troubleshooting process.