• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do I get a PTR record set up for my mail server?

M

Mr N8

Diamond Member
Does anyone know how / where I need to set up my PTR record for my exchange server? I'm being blocked by some domains that we need to send to because of a lack of PTR record.

Thanks.
 
send an email to whom ever gave you your IP block and ask them to add a PTR for you. (mail.whoeveryouare.com -> out going SMTP IP address)
 
OK, according to DNSreport.com I do have the PTR record set up, because they can do a reverse DNS lookup on my IP. However, when I run the test from DNSstuff.com, it shows that it get's to 20 hops, and says that it's stuck in a loop. RoadRunner's blocked mail lookup lists my reverse DNS as servefail, most likely because it takes too many steps to locate it.

Does anyone know what steps I need to take to make the DNS resolve faster?
 
You may have to use your ISPs mail relay service and have them settup the PTR for that instead. If you are on a buisness class t-1 they should not be blocking anything to your address range.
 
It is a business class T-1 through SBC. Not sure why the reverse DNS isn't resolving in less than 3 hops.
 
That's pretty weird. Our Cox Business Cable Modem connection hands out a Reverse DNS in four hops.
---------------------------------------
Asking a.root-servers.net.....
Asking henna.arin.net.....
Asking ns.west.cox.net.....
Asking ns1.coxmail.com.....and there it is.
----------------------------------------
What are your twenty hops?
 
No, nothing is resolved, so far. When I do a reverse DNS lookup, I get this:


How I am searching:
Asking a.root-servers.net for 178.90.78.68.in-addr.arpa PTR record:
a.root-servers.net says to go to epazote.arin.net. (zone: 68.in-addr.arpa.)
Asking epazote.arin.net. for 178.90.78.68.in-addr.arpa PTR record:
epazote.arin.net [192.41.162.32] says to go to NS2.AMERITECH.NET. (zone: 78.68.in-addr.arpa.)
Asking NS2.AMERITECH.NET. for 178.90.78.68.in-addr.arpa PTR record: Got CNAME referral to 178.176.90.78.68.in-addr.arpa. at server ns1.net-spec.net. (zone 176.90.78.68.in-addr.arpa.) [from 206.141.193.168]
Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.ameritech.net [206.141.193.168] says to go to ns2.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.ameritech.net [206.141.193.168] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns2.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.ameritech.net [206.141.193.168] says to go to ns1.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.ameritech.net [206.141.251.2] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.ameritech.net [206.141.251.2] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns1.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.ameritech.net [206.141.251.2] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record: Timed out [at 68.73.79.52]. Trying again.
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.ameritech.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Asking ns1.ameritech.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.ameritech.net [206.141.251.2] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

WARNING: Duplicate zone found (176.90.78.68.in-addr.arpa. is repeated). This can prevent the lookup from continuing
(BIND8 and BIND9 will cause a 'server failure' response). Although I will continue, be aware that
most DNS servers will not see your reverse DNS entry.

Error: It looks like you've stuck me in a loop!.

Details:
I am programmed to stop after 20 DNS queries, since most reverse DNS lookups can be finished
after just 3 queries. It sounds like you're stuck in a loop.
 
Asking NS2.AMERITECH.NET. for 178.90.78.68.in-addr.arpa PTR record: Got CNAME referral to 178.176.90.78.68.in-addr.arpa. at server ns1.net-spec.net. (zone 176.90.78.68.in-addr.arpa.) [from 206.141.193.168]
Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

Whoops.

Domain Name: NET-SPEC.NET
Administrative Contact , Technical Contact :
Network Specialists of Racine, Inc.
noc@NET-SPEC.NET
1616 Oakes Road
Racine, WI 53406
US
Phone: 262-886-9000
Fax: 262-886-9201

Domain Name: AMERITECH.NET
Administrative Contact , Technical Contact :
Southwestern, Bell
DNSCONTACT@SBCIS.SBC.COM
1701 Alma dr
Plano, TX 75075
US
Phone: 1-877-722-3755
Fax: 214-473-2253
 
Originally posted by: RebateMonger
Asking NS2.AMERITECH.NET. for 178.90.78.68.in-addr.arpa PTR record: Got CNAME referral to 178.176.90.78.68.in-addr.arpa. at server ns1.net-spec.net. (zone 176.90.78.68.in-addr.arpa.) [from 206.141.193.168]
Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)

Whoops.

Domain Name: NET-SPEC.NET
Administrative Contact , Technical Contact :
Network Specialists of Racine, Inc.
noc@NET-SPEC.NET
1616 Oakes Road
Racine, WI 53406
US
Phone: 262-886-9000
Fax: 262-886-9201

Domain Name: AMERITECH.NET
Administrative Contact , Technical Contact :
Southwestern, Bell
DNSCONTACT@SBCIS.SBC.COM
1701 Alma dr
Plano, TX 75075
US
Phone: 1-877-722-3755
Fax: 214-473-2253
Click to expand...

So, does that mean that the DNS is stuck in a loop at Network Specialists? They have our Name Servers for our domain. I'm lost on how to read the DNS entries there.

Thanks
 
Originally posted by: Mr N8
Originally posted by: RebateMonger
Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Click to expand...
So, does that mean that the DNS is stuck in a loop at Network Specialists? They have our Name Servers for our domain. I'm lost on how to read the DNS entries there.
Click to expand...
Well, I don't know much about Reverse DNS (since ISPs generally take care of it), but it certainly appears that the DNS records on Net-Spec.net's ns1 and ns2 nameservers are messed up. They should both be delivering a PTR record, not referring to each other in a loop.
 
Originally posted by: RebateMonger
Originally posted by: Mr N8
Originally posted by: RebateMonger
Asking ns1.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns1.net-spec.net [68.73.79.51] says to go to ns2.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Asking ns2.net-spec.net. for 178.176.90.78.68.in-addr.arpa. PTR record:
ns2.net-spec.net [68.73.79.52] says to go to ns1.net-spec.net. (zone: 176.90.78.68.in-addr.arpa.)
Click to expand...
So, does that mean that the DNS is stuck in a loop at Network Specialists? They have our Name Servers for our domain. I'm lost on how to read the DNS entries there.
Click to expand...
Well, I don't know much about Reverse DNS (since ISPs generally take care of it), but it certainly appears that the DNS records on Net-Spec.net's ns1 and ns2 nameservers are messed up. They should both be delivering a PTR record, not referring to each other in a loop.
Click to expand...


Thanks. I've contacted Network Specialists, and hopefully we'll be able to get this taken care of quickly. I've got very well-paid people on my back about this...
 
My ISP (SBC / AT&T) and the company that the reverse DNS has been delegated to are supposed to be working on it. Still having the issues, but it's out of my hands at this point.
 
Hope they resolve it soon. While I'm not in love with Qwest, I can go on their self-service web site and create a (working) PTR record for my IP address in about two minutes.
 
I finally got the whole PTR / Reverse DNS situation worked out with my ISP. I still am not able to send to RoadRunner addresses. I'm hoping that there's just a delay / cache that's stopping me at this point. I've checked to see how rr.com sees my server by running the tool at security.rr.com and they see my domain and don't show me on any of their blocked lists.

 
Glad to hear you got it working. Too bad it took so long for your ISP to get it fixed for you. Somebody messed up that PTR record pretty badly.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top