Re: We are not getting mails from some domains :(
- From: guzzi <guzzi@xxxxxxxxxxxxxx>
- Date: Sat, 13 May 2006 15:05:08 +0200
Nuevo wrote / napi'sal(a):
Start by getting a copy of the NDRs. Take a look at your SMTP logs and Message Tracking. Look in the event viewer.in Event log found that:
Nue
"guzzi" <guzzi@xxxxxxxxxxxxxx> wrote in message news:%234uo$9FdGHA.1436@xxxxxxxxxxxxxxxxxxxxxxxHi
I have a strange problem (not from the begining of exchange existance)
Some people report us that their mails could not be delivered to our exchange server and they get those mail returned.
Other external customer report us that his mail could be delivered only to one mailbox, when he try to send a mail to any other - he get returned mail.
What should i check to get it working well?
TIA
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: SMTP Protocol
Event ID: 7002
Date: 12. 5. 2006
Time: 12:43:59
User: N/A
Computer: ISERVER
Description:
This is an SMTP protocol warning log for virtual server ID 1, connection #3158. The remote host "199.185.x.x", responded to the SMTP command "rcpt" with "450 <NAME.SURNAME@xxxxxxxxxxxx>: Sender address rejected: Domain not found ". The full command sent was "RCPT TO:<name@xxxxxxxxxxxxx> ". This may cause the connection to fail.
For more information, click http://www.microsoft.com/contentredirect.asp.
other:
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: SMTP Protocol
Event ID: 7002
Date: 12. 5. 2006
Time: 2:00:34
User: N/A
Computer: ISERVER
Description:
This is an SMTP protocol warning log for virtual server ID 1, connection #3069. The remote host "213.180.x.x", responded to the SMTP command "mail" with "450 4.4.3 Hello [MyIP], for your input: <NAME.SURNAME@xxxxxxxxxxxx> policy analysis reports temporary DNS error with your source domain. ". The full command sent was "MAIL FROM:<NAME.SURNAME@xxxxxxxxxxxx> SIZE=951 ". This may cause the connection to fail.
For more information, click http://www.microsoft.com/contentredirect.asp.
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Connection Manager
Event ID: 4000
Date: 13. 5. 2006
Time: 11:20:38
User: N/A
Computer: ISERVER
Description:
Message delivery to the remote domain 'ip.adsl.hu' failed for the following reason: Unable to bind to the destination server in DNS.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d5 02 04 c0 O~..A`
other events i've found in event viewer
451 Unable to complete command, DNS not available or timed out
or
Event ID 2012/2013 SMTP could not connect to the DNS server
It seams to be a problem with DNS. But i didn't even toutch DNS server over a 9 month, so i think it's not my fail?!
I went to www.dnsreport.com and found few warnings and errors:
WARN
Glue at parent nameservers
WARNING. The parent servers (I checked with m.gtld-servers.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
====================
WARN
All nameservers report identical NS records
WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
62.168.96.4 returns 0 answers (may be a referral)
(this is DNS of mine ISP) I have that IP in my TCP/IP settings as a second DNS. The same ip is in Exchange settings as a forwarder.
====================
FAIL
Lame nameservers
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
62.168.96.4
===================
and SOA
Your SOA record [TTL=3600] is:
Primary nameserver: MyDomain
Hostmaster E-mail address: hostmaster.MyDomain
Serial #: 8 - WARNING
Refresh: 900 - WARNING
Retry: 600
Expire: 86400 - WARNING
Default TTL: 3600
Please help me, what should i do?
TIA :)
.
- Follow-Ups:
- Re: We are not getting mails from some domains :(
- From: Rich Matheisen [MVP]
- Re: We are not getting mails from some domains :(
- References:
- We are not getting mails from some domains :(
- From: guzzi
- Re: We are not getting mails from some domains :(
- From: Nuevo
- We are not getting mails from some domains :(
- Prev by Date: Re: Cannot Move Mailboxes
- Next by Date: Re: Two computers in office used by same user...problems
- Previous by thread: Re: We are not getting mails from some domains :(
- Next by thread: Re: We are not getting mails from some domains :(
- Index(es):
Relevant Pages
|