Re: PTR Records

Thanks, Herb, for your replies. I've often thought AOL really doesn't want
to receive email from the outside world.


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:eTkckJQ9FHA.2632@xxxxxxxxxxxxxxxxxxxxxxx
>> All of these changes didn't seem to fix the problem we're having sending
>> email to AOL and Compuserve, though. The strange thing is that one of our
>> 3 email servers can send mail to them; the other 2 cannot. The error I
>> see in the ESM is "an SMTP protocol error occurred", so I guess the PTR
>> records are still not right. For some reason, we have a ton of PTR
>> records that point to mail.coweta....that have ips that I don't
>> recognize. Should there just be the one record for dewey in there? I
>> don't know why all those other entries would be there.
>
> Sometimes even if you do everything correctly (over and above the RFCs
> even) AOL will still not work from time to time.
>
> They have the most hosed up email system of any large provider.
>
> --
> Herb Martin, MCSE, MVP
> Accelerated MCSE
> http://www.LearnQuick.Com
> [phone number on web site]
>
> "MC" <mccato@xxxxxxxxxxx> wrote in message
> news:eHMeNuP9FHA.632@xxxxxxxxxxxxxxxxxxxxxxx
>> Thanks so much, Kevin. I've made those changes; and I have another
>> question, if you don't mind. I created an SPF record, but it has mx in
>> there twice. I looked at some SPF records for other domains, and didn't
>> see that in their records. Will you take a look at it and see if looks
>> correct? Here it is:
>>
>> v=spf1 ip4:168.9.128.0/19 mx a:168.9.128.29 a:168.9.128.195
>> a:168.9.128.204 a:168.9.128.36 mx:dewey.cowetaschools.net ~all
>>
>> All of these changes didn't seem to fix the problem we're having sending
>> email to AOL and Compuserve, though. The strange thing is that one of our
>> 3 email servers can send mail to them; the other 2 cannot. The error I
>> see in the ESM is "an SMTP protocol error occurred", so I guess the PTR
>> records are still not right. For some reason, we have a ton of PTR
>> records that point to mail.coweta....that have ips that I don't
>> recognize. Should there just be the one record for dewey in there? I
>> don't know why all those other entries would be there.
>>
>> I can't tell you how much I appreciate your help!
>> Thanks!
>>
>> "Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx> wrote in message
>> news:ObJy8dP9FHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
>>> MC <mc@xxxxxxxx> wrote:
>>>> Thanks, Kevin. I got the A records for dewey and changed the MX
>>>> records; and deleted all of the MX records that pointed to mail@......
>>>>
>>>> I'm a little confused as to what to do with the CName records. We
>>>> receive email addressed to all of those domains. Here's what is
>>>> currently there:
>>>>
>>>> (same as parent folder) Host 168.9.128.18
>>>> (same as parent folder) Mail Exchanger [10] dewey.cowetaschools.net.
>>>> (same as parent folder) Name Server dns1.cowetaschools.org.
>>>> (same as parent folder) Name Server dns2.cowetaschools.org.
>>>> (same as parent folder) Start of Authority [2005100608],
>>>> dns1.cowetaschools.org., administrator.cowetaschools.org.
>>>> dewey Host 168.9.128.29
>>>> mail Host 168.9.128.29
>>>> pop Alias mail.cowetaschools.org.
>>>> smtp Alias mail.cowetaschools.org.
>>>
>>> You would have a lot cleaner zone if you just create the CNAME record,
>>> name
>>> it mail, pop or whatever and point that CNAME record to
>>> dewey.coetaschools.net. This way if the IP for dewey.cowetaschools.net
>>> ever
>>> changes all the CNAMES will get the updated IP. This won't be a big
>>> problem
>>> since all domains are hosted by the same DNS server.
>>>
>>>>
>>>> What do I need to change/add to fix that?
>>>> And how should I fix the NS record problems?
>>>
>>> Alright, lets use this domain, (cowetaschools.org) all you need to do is
>>> edit the NS records in this zone, and change the NS name to
>>> dns1.cowetaschools.net and dns2.cowetaschools.net.
>>> -Or-
>>> Edit the Domain at the registrar and change the public record to reflect
>>> the
>>> dns1.cowetaschools.org and dns2.cowetaschools.org that the zone says. If
>>> these name are already registered as name servers by your registrar,
>>> this
>>> would actually be the best route. This is because the DNS host records
>>> should actually be in the same TLD as the domain they host, it's not
>>> required, but it make resolving the domain from the root faster by
>>> skipping
>>> a step for resolving the NS records. You won't have any downtime since
>>> they
>>> are on the same DNS server.
>>>
>>> The point is, your DNS server should give the same NS records that are
>>> listed on the public record for the domain. If you will run DNS report
>>> for
>>> each of these domains it will tell you which are right and which aren't.
>>>
>>>> I really appreciate your help. As you can see, our DNS has been
>>>> needing attention for a long time.
>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Kevin D. Goodknecht Sr. [MVP]
>>> Hope This Helps
>>> ===================================
>>> When responding to posts, please "Reply to Group"
>>> via your newsreader so that others may learn and
>>> benefit from your issue, to respond directly to
>>> me remove the nospam. from my email address.
>>> ===================================
>>> http://www.lonestaramerica.com/
>>> http://support.wftx.us/
>>> https://secure.lsaol.com/
>>> ===================================
>>> Use Outlook Express?... Get OE_Quotefix:
>>> It will strip signature out and more
>>> http://home.in.tum.de/~jain/software/oe-quotefix/
>>> ===================================
>>> Keep a back up of your OE settings and folders
>>> with OEBackup:
>>> http://www.oehelp.com/OEBackup/Default.aspx
>>> ===================================
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: thanks and more questions
    ... I'd do it myself, but my corporate firewall ... all you have to do is use a different DNS server than the one your company provides and you can get around these blocked sites. ... Of course if *they* are using OpenDNS, then that won't work because they will already have OpenDNS setup to block sites for traffic coming from their routers. ... then you are just out of luck unless you have an AOL account and they will let you login to AOL. ...
    (rec.arts.disney.parks)
  • Re: SBS SMTP Connector issue
    ... > Lee Snyder wrote: ... i followed a previous string about AOL ... >> this prevented the AOL mail server from recieving my messages? ... > uses its own DNS server settings.... ...
    (microsoft.public.exchange.connectivity)
  • Re: who owns IP
    ... They could be just MSN and AOL members... ... >> Yes interesting, maybe mickysnot is trying to hit my DNS server, caught by ... > I catch both M$ and AOL systems at my firewall on occasion also. ...
    (comp.os.linux.security)
  • Re: Deleting Emails from Outlook Does Not Delete Them From the Server
    ... No. AOL also have POP access. ... that was when AOL was offering free domains they would register for you. ... with that Melbourne registrar for these free domains that provided POP ... I still have an old AOL Domains account under their @switched.com ...
    (microsoft.public.outlook.general)
Loading