Jason Watson
New Member
Emails started getting kicked back about 3 weeks ago due to reverse DNS failures. When I do a DNS check on okaloosapa.com I get this:
Revers DNS Failure
- Thread starter Jason Watson
- Start date
Hi there
as you are using your own primary mailserver: mail.okaloosapa.com...
PTR records are actually created at the organization that provides you with your IP addresses and/or net block information.
Please contact that organization and ask them if they will provide that service. If not .. ask if they would allow a third party DNS company like zoneedit
to provide the reverse services. If they do..,. you can use the add a domain link on your zoneedit members page to add the net block data. Once the invoice has been paid you can set the PTR records through the DNS settings tab for that net block.
thanks
sandy
as you are using your own primary mailserver: mail.okaloosapa.com...
PTR records are actually created at the organization that provides you with your IP addresses and/or net block information.
Please contact that organization and ask them if they will provide that service. If not .. ask if they would allow a third party DNS company like zoneedit
to provide the reverse services. If they do..,. you can use the add a domain link on your zoneedit members page to add the net block data. Once the invoice has been paid you can set the PTR records through the DNS settings tab for that net block.
thanks
sandy
Jason Watson
New Member
It also looks like NS18 and NS7 arent replicating...See the error I am getting:
One or more addresses referenced by MX records do not have a matching reverse DNS entry. This can cause problems for mail deliverability for these servers. Some mail platforms will not accept or will delay email coming from mismatched addresses. The addresses without matching reverse DNS entries are:
23.27.48.62 has mail.okaloosapa.com. | 204.49.21.251 listed.
198.199.82.247 has mail.okaloosapa.com. | 204.49.21.251 listed.
One or more addresses referenced by MX records do not have a matching reverse DNS entry. This can cause problems for mail deliverability for these servers. Some mail platforms will not accept or will delay email coming from mismatched addresses. The addresses without matching reverse DNS entries are:
23.27.48.62 has mail.okaloosapa.com. | 204.49.21.251 listed.
198.199.82.247 has mail.okaloosapa.com. | 204.49.21.251 listed.
Jason Watson
New Member
Nameserver SOAs do not agree on the serial number. This is bad because your nameservers may contain different resource record data and cause delays or misrouting of packets. It is possible that you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. The nameserver SOAs and their mismatched serial numbers are:
ns18.zoneedit.com. has Serial #: 1460488125 and ns7.zoneedit.com. has Serial #: 1460561013
ns18.zoneedit.com. has Serial #: 1460488125 and ns7.zoneedit.com. has Serial #: 1460561013
Hi Jason
I just noticed that the domain is set to be a secondary DNS domain but as the primary IP you have 198.199.82.247
(pdns2.zoneedit.com).. that primary should be your primary IP and not one from zonedit... did you want to be on secondary or primary DNS services?
sandy
I just noticed that the domain is set to be a secondary DNS domain but as the primary IP you have 198.199.82.247
(pdns2.zoneedit.com).. that primary should be your primary IP and not one from zonedit... did you want to be on secondary or primary DNS services?
sandy
Jason Watson
New Member
So you are saying that should be our domain IP?
Jason Watson
New Member
I did a reverse DNS lookup on our public facing IP for the mail server listed at zoneedit and it returned no results, wouldnt that be listed at zoneedit as well? 204.49.21.251
that IP does not have a PTR record but the net block is delegated to centurylink.net:
dig +trace 251.21.49.204.in-addr.arpa
; <<>> DiG 9.8.3-P1 <<>> +trace 251.21.49.204.in-addr.arpa
;; global options: +cmd
. 518355 IN NS a.root-servers.net.
. 518355 IN NS d.root-servers.net.
. 518355 IN NS e.root-servers.net.
. 518355 IN NS c.root-servers.net.
. 518355 IN NS j.root-servers.net.
. 518355 IN NS i.root-servers.net.
. 518355 IN NS l.root-servers.net.
. 518355 IN NS h.root-servers.net.
. 518355 IN NS g.root-servers.net.
. 518355 IN NS b.root-servers.net.
. 518355 IN NS f.root-servers.net.
. 518355 IN NS m.root-servers.net.
. 518355 IN NS k.root-servers.net.
;; Received 496 bytes from 205.210.42.40#53(205.210.42.40) in 166 ms
in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
;; Received 420 bytes from 192.36.148.17#53(192.36.148.17) in 1092 ms
204.in-addr.arpa. 86400 IN NS r.arin.net.
204.in-addr.arpa. 86400 IN NS u.arin.net.
204.in-addr.arpa. 86400 IN NS x.arin.net.
204.in-addr.arpa. 86400 IN NS y.arin.net.
204.in-addr.arpa. 86400 IN NS z.arin.net.
204.in-addr.arpa. 86400 IN NS arin.authdns.ripe.net.
;; Received 164 bytes from 196.216.169.10#53(196.216.169.10) in 346 ms
49.204.in-addr.arpa. 86400 IN NS authns2.centurylink.net.
49.204.in-addr.arpa. 86400 IN NS authns1.centurylink.net.
;; Received 103 bytes from 199.180.180.63#53(199.180.180.63) in 35 ms
21.49.204.in-addr.arpa. 86400 IN NS eagle.co.okaloosa.fl.us.
;; Received 81 bytes from 208.44.130.120#53(208.44.130.120) in 40 ms
dig +trace 251.21.49.204.in-addr.arpa
; <<>> DiG 9.8.3-P1 <<>> +trace 251.21.49.204.in-addr.arpa
;; global options: +cmd
. 518355 IN NS a.root-servers.net.
. 518355 IN NS d.root-servers.net.
. 518355 IN NS e.root-servers.net.
. 518355 IN NS c.root-servers.net.
. 518355 IN NS j.root-servers.net.
. 518355 IN NS i.root-servers.net.
. 518355 IN NS l.root-servers.net.
. 518355 IN NS h.root-servers.net.
. 518355 IN NS g.root-servers.net.
. 518355 IN NS b.root-servers.net.
. 518355 IN NS f.root-servers.net.
. 518355 IN NS m.root-servers.net.
. 518355 IN NS k.root-servers.net.
;; Received 496 bytes from 205.210.42.40#53(205.210.42.40) in 166 ms
in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
;; Received 420 bytes from 192.36.148.17#53(192.36.148.17) in 1092 ms
204.in-addr.arpa. 86400 IN NS r.arin.net.
204.in-addr.arpa. 86400 IN NS u.arin.net.
204.in-addr.arpa. 86400 IN NS x.arin.net.
204.in-addr.arpa. 86400 IN NS y.arin.net.
204.in-addr.arpa. 86400 IN NS z.arin.net.
204.in-addr.arpa. 86400 IN NS arin.authdns.ripe.net.
;; Received 164 bytes from 196.216.169.10#53(196.216.169.10) in 346 ms
49.204.in-addr.arpa. 86400 IN NS authns2.centurylink.net.
49.204.in-addr.arpa. 86400 IN NS authns1.centurylink.net.
;; Received 103 bytes from 199.180.180.63#53(199.180.180.63) in 35 ms
21.49.204.in-addr.arpa. 86400 IN NS eagle.co.okaloosa.fl.us.
;; Received 81 bytes from 208.44.130.120#53(208.44.130.120) in 40 ms