Sorry I messed UP the arpa names (must be in reverse order vs IPs) On a DNS server, you should have a 74.14.171.192.in-addr.arpa. zone then a PTR setting like : 74.14.171.192.in-addr.arpa. 86400 IN PTR mail.imcu.com.
Bertrand 2015-12-07 11:03 GMT-05:00 Bertrand ELLEN-PREVOT <[email protected]>: > I replied in the other thread but the more I read, the more i'm sure PTR > records don't belong to domain's zone (by domain I mean imcu.com). > > Yes, this means there are "DNS servers" for IP addresses. > > When PTR are queried, your client queries Arin to know which DNS server is > responsible for this IP, then you get the answer from this DNS server (can > be at ARIN directly for occasional users) : > > When querying a PTR, you're not hitting your imcu.com dns server since > you're querying an IP. > > Previously, on your ISP IP's, it was managed by them on their system for > reverse DNS/PTR. > > from : > http://www.itworld.com/article/2833006/networking/how-to-setup-reverse-dns-and-ptr-records.html > > On a DNS server, you should have a 192.171.14.74.in-addr.arpa. zone > then a PTR setting like : > 192.171.14.74.in-addr.arpa. 86400 IN PTR mail.imcu.com. > > then you'll have to specify at ARIN to use this DNS server for PTR for > your IP block (Delegation). > > Or use their interface if you have few PTR records to setup ("occasional > user") > https://www.arin.net/resources/request/reversedns.html > > Best > > Bertrand > > 2015-12-07 9:53 GMT-05:00 David McSpadden <[email protected]>: > >> No worries. >> >> We purchased a class c. >> >> We migrated from our ISP to our own class c addresses. >> >> Web Solutions at Fiserv hosts our website and offers DNS management. >> >> They are responsible for our DNS updates. >> >> Looks to me like they have not removed some PTR’s and have not added some >> PTR’s. >> >> Once I have a clean Zone I’ll let everyone know. >> >> And we can see about any other issues that may be out there. >> >> What I want to see is this: >> >> >> imcu.com. >> >> @ 86400 >> IN SOA pdns206.ultradns.com. bill\.krause.fiserv.com. ( >> >> >> 2014081271 ;Serial >> >> >> 10800 ;Refresh >> >> >> 3600 ;Retry >> >> >> 2592000 ;Expire >> >> >> 86400 ;Minimum >> >> >> ) >> >> @ 86400 >> IN NS pdns206.ultradns.org. >> >> @ 86400 >> IN NS pdns206.ultradns.com. >> >> @ 86400 >> IN NS pdns206.ultradns.net. >> >> @ 86400 >> IN NS pdns206.ultradns.biz. >> >> @ 86400 >> IN A 12.145.177.146 >> >> @ 86400 >> IN MX 10 mail.imcu.com. >> >> @ 86400 >> IN TXT "v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 ~all" >> >> @ 86400 >> IN TXT "\"v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 >> ~all\"" >> >> www 86400 >> IN A 12.145.177.146 >> >> mail 600 >> IN A 192.171.14.74 >> >> autodiscover 600 >> IN A 192.171.14.74 >> >> legacymail 600 >> IN A 192.171.14.74 >> >> outlook 600 >> IN A 192.171.14.74 >> >> secure 600 >> IN A 192.171.14.73 >> >> ftp 600 >> IN A 192.171.14.72 >> >> vpn 86400 >> IN A 38.109.185.130 >> >> m 86400 >> IN CNAME ml-http-generic-300922534.us-east-1.elb.amazonaws.com. >> >> 74.14.171.192.in-addr.arpa 86400 IN PTR >> mail.imcu.com. >> >> 72.14.171.192.in-addr.arpa 86400 IN PTR >> ftp.imcu.com. >> >> 73.14.171.192.in-addr.arpa 86400 IN PTR >> secure.imcu.com. >> >> 130.185.109.38.in-addr.arpa 86400 IN PTR >> VPN.IMCU.COM. >> >> >> >> But the PTR’s are not there at all and these old PTR’s are still hanging >> out there: >> >> 193.185.109.38.in-addr.arpa 86400 IN PTR >> mail.IMCU.COM. >> >> 194.185.109.38.in-addr.arpa 86400 IN PTR >> board.IMCU.COM. >> >> 196.185.109.38.in-addr.arpa 86400 IN PTR >> ftp.IMCU.COM. >> >> 193.185.109.38.in-addr.arpa 86400 IN PTR >> mx1.IMCU.COM. >> >> 206.185.109.38.in-addr.arpa 86400 IN PTR >> secure.IMCU.COM. >> >> >> >> ATT.net, Comcast.net, sbcglobal.net, and Aol.com are all bouncing my >> outbound email. >> >> >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Kennedy, Jim >> *Sent:* Monday, December 7, 2015 9:44 AM >> >> *To:* [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> >> >> Who owns/controls the IP addresses? That is who has to do the PTR >> records. What is the sending IP address? >> >> >> >> Sorry, I was out of touch this weekend so I didn’t get through the whole >> thread of you issue….. >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *David McSpadden >> *Sent:* Monday, December 7, 2015 9:41 AM >> *To:* [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> >> >> It might be since it doesn’t appear that my new PTR records are there. >> >> It’s like the company I am using did the A, CNAME, MX records but did not >> remove the old or add the new. >> >> >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Kennedy, Jim >> *Sent:* Monday, December 7, 2015 9:37 AM >> *To:* [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> >> >> The old PTR records won’t cause this issue. Consider the process that is >> happening…… >> >> >> >> You HELO mailout.imcu.com and connect with from 192.168.1.1 >> >> >> >> The receiving server looks at the A record for mailout.imcu.com…it must >> match 192.168.1.1 >> >> It then looks at the PTR for 192.168.1.1 it must return mailout.imcu.com >> >> >> >> They are not looking at your old PTR records, they don’t even know about >> them anymore. That isn’t your issue. >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *David McSpadden >> *Sent:* Monday, December 7, 2015 9:31 AM >> *To:* [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> >> >> Or maybe just maybe I need to ask them to show me the old PTR’s we >> migrated from. >> >> Just happened to think this morning that maybe the old PTR’s were out >> there. >> >> They are right there like always. >> >> Have asked them to remove the old PTR for the old IP’s. >> >> You would think after this many years I would know to ask that type of >> question. >> >> >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *HELP_PC >> *Sent:* Monday, December 7, 2015 12:50 AM >> *To:* [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> >> >> As long as you have a A record recorded for your domain the ISP should >> have a subsequent PTR record >> >> >> >> GuidoElia >> HELPPC-HELPPCSERVICE >> ------------------------------ >> >> *Da:* [email protected] [[email protected]] >> per conto di David McSpadden [[email protected]] >> *Inviato:* domenica 6 dicembre 2015 17.59 >> *A:* [email protected]; [email protected] >> *Oggetto:* [NTSysADM] RE: ptr records >> >> Thank you all >> >> The PTR records are still not out there. >> >> Gonna be a busy day Monday. >> >> >> >> AT&T and Comcast are refusing our traffic. >> >> >> ------------------------------ >> >> *From:* [email protected] [[email protected]] >> on behalf of Brian Desmond [[email protected]] >> *Sent:* Saturday, December 05, 2015 6:17 PM >> *To:* [email protected]; [email protected] >> *Subject:* [NTSysADM] RE: ptr records >> >> *No, they’re not necessary. * >> >> >> >> *Thanks,* >> >> *Brian Desmond* >> >> >> >> *w – 312.625.1438 | c – 312.731.3132* >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *David McSpadden >> *Sent:* Friday, December 4, 2015 1:55 PM >> *To:* [email protected]; [email protected] >> *Subject:* [NTSysADM] ptr records >> >> >> >> Do I need PTR records for Legacymail, outlook, and autodiscover? >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are >> not one of the named recipient(s) or otherwise have reason to believe that >> you have received this message in error, please notify the sender and >> delete this message immediately from your computer. Any other use, >> retention, dissemination, forwarding, printing, or copying of this email is >> strictly prohibited. >> >> >> >> Please consider the environment before printing this email. >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are >> not one of the named recipient(s) or otherwise have reason to believe that >> you have received this message in error, please notify the sender and >> delete this message immediately from your computer. Any other use, >> retention, dissemination, forwarding, printing, or copying of this email is >> strictly prohibited. >> >> >> >> Please consider the environment before printing this email. >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are >> not one of the named recipient(s) or otherwise have reason to believe that >> you have received this message in error, please notify the sender and >> delete this message immediately from your computer. Any other use, >> retention, dissemination, forwarding, printing, or copying of this email is >> strictly prohibited. >> >> >> >> Please consider the environment before printing this email. >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are >> not one of the named recipient(s) or otherwise have reason to believe that >> you have received this message in error, please notify the sender and >> delete this message immediately from your computer. Any other use, >> retention, dissemination, forwarding, printing, or copying of this email is >> strictly prohibited. >> >> >> >> Please consider the environment before printing this email. >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are >> not one of the named recipient(s) or otherwise have reason to believe that >> you have received this message in error, please notify the sender and >> delete this message immediately from your computer. Any other use, >> retention, dissemination, forwarding, printing, or copying of this email is >> strictly prohibited. >> >> Please consider the environment before printing this email. >> > >
