Safe to say that some folks here need to educate themselves on DNS... Thought I night teach some folks to fish today, looks like I was too optimistic
name class type data time to live mail.imcu.com IN A 192.171.14.74 600s (10m) name class type data time to live imcu.com IN TXT v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 ~all 600s (10m) imcu.com IN TXT "v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 ~all" 600s (10m) On Sun, Dec 6, 2015 at 12:53 PM Michael Tavares <[email protected]> wrote: > So do we know what the IP address of the PTR in question is? > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Don Ely > *Sent:* Sunday, December 06, 2015 3:22 PM > > > *To:* [email protected] > *Subject:* Re: [NTSysADM] RE: ptr records > > > > *67.222.132.213 is a non-cached DNS Server* > > > > On Sun, Dec 6, 2015 at 12:13 PM Michael Tavares <[email protected]> > wrote: > > Did I miss something, the link the link below has 67.222.132.213 in the > query so I was assuming that is the address of the problem PTR record. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Don Ely > *Sent:* Sunday, December 06, 2015 2:58 PM > > > *To:* [email protected] > *Subject:* Re: [NTSysADM] RE: ptr records > > > > 67.222.132.213 is a non-cached DNS Server > > > > On Sun, Dec 6, 2015 at 11:56 AM Don Ely <[email protected]> wrote: > > Not sure where you got your info... > > > > name class type data time to live > > mail.imcu.com IN A 192.171.14.74 600s (10m) > > > > name class type data time to live > > imcu.com IN TXT v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 ~all 600s > (10m) > > imcu.com IN TXT "v=spf1 ip4:184.72.242.195 ip4:192.171.14.74 ~all" 600s > (10m) > > > > > > > > > > On Sun, Dec 6, 2015 at 11:53 AM Michael Tavares <[email protected]> > wrote: > > There is a PTR record currently configured for 67.222.132.213 that point > to tailormadeservers.com (see nslookup results below). Digging deeper > into it the netblock that 67.222.132.213 falls into is owned by DFW > DataCenter. The DNS server currently handing out the PTR record is 72.9.144.3 > (NS.Tailormadeservers.com) > > > > So at this point NS.Tailormadeservers.com DNS server is the authoritative > DNS for the netblock that you are currently using. If you are getting your > IP’s from Tailormadeservers they will need to update the PTR record for > you, otherwise your ISP is going to have to get that transferred to the DNS > server that you are making the changes on. Once that happens you should > see your published PTR records start propagating around the DNS. The > current TTL is 86400 so it will take 24+ hours for the cached entries to > start updating. > > > > > > C:\Users\speeddemon>nslookup > > Default Server: UnKnown > > Address: 192.168.1.1 > > > > > set type=ptr > > > 67.222.132.213 > > Server: UnKnown > > Address: 192.168.1.1 > > > > Non-authoritative answer: > > 213.132.222.67.in-addr.arpa name = > 67.222.132.213.tailormadeservers.com > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *David McSpadden > *Sent:* Sunday, December 06, 2015 1:27 PM > *To:* [email protected] > *Subject:* Re: [NTSysADM] RE: ptr records > > > > We just bought our own and migrated last week. > > > > Sent from my iPhone > > > On Dec 6, 2015, at 1:17 PM, Don Ely <[email protected]> wrote: > > There should only be a PTR record for the inbound/outbound smtp relay. > Currently, it does not appear you have one. I'm surprised you aren't > having more trouble with email without the PTR... I'm going to guess your > ISP owns the IP space? > > > > > http://network-tools.com/nslook/Default.asp?domain=imcu.com&type=12&server=67.222.132.213&class=1&port=53&timeout=5000&advanced=true&go.x=21&go.y=18 > > > > On Sun, Dec 6, 2015 at 9:01 AM David McSpadden <[email protected]> wrote: > > 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]] *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. > >
