Re: Changed Internet Service and Now Having E-mail Problems

Because all the top / bottom posting is very hard to follow, I have cut out all the previous postings.

Dan, I can telnet to your mail server using either the ip address or the domain name as shown in the mx records that are listed in the report. I have sent an email to dan@ the domain name, and it has not come back, (yet). Assuming that it does not, the mail is going somewhere, just not where we expect.

For the mail, more importantly than the stealth issue is the following. You should contact your isp and have all the issues corrected.
Because you have already posted the domain name, I have not munged it, but munging a public email address is silly anyway.
_____
Duplicate MX records WARNING: You have duplicate MX records. This means that mailservers may try delivering mail to the same IP more than once. Although technically valid, this is very confusing, and wastes resources. The duplicate MX records are:

marpia.com. and server.marpia.com. both resolve to 71.248.175.205.

FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
205.175.248.71.in-addr.arpa [Timeout (check it)]

Mail WARN Connect to mail servers WARNING: I could not complete a connection to 66% of your mailservers. This could lead to a performance issue in your reception of mail:
marpia.com: Timed out [Last data sent: [Did not connect]]
server.marpia.com: Timed out [Last data sent: [Did not connect]]



--
Larry


Larry:
So I guess I'm a litle confused. According to the DNS report, it
seems to connect to my SBS mail server just fine. Whats the purpose of
stealth name servers? Should I report this issue to dyndns and see
what they say, or is this a Verizon issue?

.

Relevant Pages

  • Re: Scared as hell with SBS 2003 Exchange
    ... public outside IP address and forwarding them to the outside interface of a Symantec Gateway Security 360 appliance, forwarding those same ports to SBS 2003's internal IP address. ... This same person told me I need to put the Exchange server on the PIX 501 DMZ interface and use a different public IP address just for Exchange. ... I've heard that I need to set up reverse DNS for my public IP address to allow messages being sent to certain domains such as verizon.net, nyc.rr.com, optonline.net, etc. I'm getting messages as follows: ... or send mail through your ISP's own mail server ...
    (microsoft.public.windows.server.sbs)
  • Cannot send email to hotmail.com !?!?
    ... are stuck on retry and are unable to get the mail delivered. ... mail server, but the reverse DNS entries are now fine and still ...
    (microsoft.public.exchange.admin)
  • Re: An SMTP protocol error occurred when sending to AOL and Compuserve
    ... correct reverse DNS registration for your sending mail server ... firewall settings - cisco PIX firewalls with DNS Fixup enabled can only ... This is too small for AOL ... > verified our reverse DNS entries; and I did their telnet test that shows ...
    (microsoft.public.exchange2000.admin)
  • Re: Reverse DNS/PTR
    ... What is PTR and what is that for? ... What are the differences between forward DNS and reverse DNS? ... pretending to be another reliable mail server; ... Hope my explanation was clear enough. ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot send mail out after default installation
    ... FAILURE: Reverse DNS entries for MX records ERROR: The IP of one or more ... it may mean that your DNS servers did not respond fast ... It is strongly urged that you have them, as many mailservers will ... SPF record Your domain does not have an SPF record. ...
    (microsoft.public.windows.server.sbs)