David Logan
asked on
NDR 5.4.0 server not found in Destination DNS
Hi I have been getting the following errors from our exchange.
The following recipient(s) could not be reached:
name@domain.co.uk on 03/03/2014 12:35
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
and this error
The following recipient(s) could not be reached:
invalid@email.address on 27/02/2014 16:29
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
The following recipient(s) could not be reached:
name@domain.co.uk on 03/03/2014 12:35
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
and this error
The following recipient(s) could not be reached:
invalid@email.address on 27/02/2014 16:29
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi
We use sbs 2003 and exchange 2003. Our ISP if BT (uk based) and we have a cathcall pop3 download from their office 365 service. Emails are sent our from our server - no relay that i know of.
I know our MX records don't point direct. We are migrating to sbs 2011 soon and I hope to have our server deal direct with emails and have our mx records updated.
running nslookup command I get the following.
server: localhost
address:127.0.0.1
No-authoratuve answer:
ourdomain.org.uk mx preferance = 1 mail exchanger = ourdomain-org-uk.mail.eo.o
ourdomain.org.uk mx preferance = 10 exchanger = ibmr.btconnect.com
Hope you can point me in the right direction.
Thanks
David.
We use sbs 2003 and exchange 2003. Our ISP if BT (uk based) and we have a cathcall pop3 download from their office 365 service. Emails are sent our from our server - no relay that i know of.
I know our MX records don't point direct. We are migrating to sbs 2011 soon and I hope to have our server deal direct with emails and have our mx records updated.
running nslookup command I get the following.
server: localhost
address:127.0.0.1
No-authoratuve answer:
ourdomain.org.uk mx preferance = 1 mail exchanger = ourdomain-org-uk.mail.eo.o
ourdomain.org.uk mx preferance = 10 exchanger = ibmr.btconnect.com
Hope you can point me in the right direction.
Thanks
David.
Have you, in fact, verified the email addresses in question as the messages suggest?
Then, your MX records aren't even a factor in outbound email -- what is important is if you have a SmartHost configured and if that is working properly.
To see if you have one configured, open the properties of the Default SMTP Virtual Server, click the Delivery Tab and then click Advanced.
Then, your MX records aren't even a factor in outbound email -- what is important is if you have a SmartHost configured and if that is working properly.
To see if you have one configured, open the properties of the Default SMTP Virtual Server, click the Delivery Tab and then click Advanced.
ASKER
Hi we have emailed this person before.
We have our server.ourdomain.local listed as our FQDN, smart host is blank, masquerade domain is blank and external DNS fields are blank.
I think this how we always has our system setup, although i seem to remember out FQDN being our actual front end domain .org.uk listed!!.
Thanks
David.
We have our server.ourdomain.local listed as our FQDN, smart host is blank, masquerade domain is blank and external DNS fields are blank.
I think this how we always has our system setup, although i seem to remember out FQDN being our actual front end domain .org.uk listed!!.
Thanks
David.
If you open a command prompt on your server can you ping the host name of the destination server you are getting the error on?
You may need to look up the MX record of their domain to find the exact host name.
You can do this at mxtoolbox.com
Jeff
You may need to look up the MX record of their domain to find the exact host name.
You can do this at mxtoolbox.com
Jeff
ASKER
Hi Jeff, Thanks for coming back to be. No MX records exist for this domain!!. I know the company got took over, Not sure f the domain transferred with it.
I notice that when I ping my own domain i get timed out!.
we are getting this error returned from internal mail.
The following recipient(s) could not be reached:
invalid@email.address on 27/02/2014 16:29
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
I notice that when I ping my own domain i get timed out!.
we are getting this error returned from internal mail.
The following recipient(s) could not be reached:
invalid@email.address on 27/02/2014 16:29
The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
<ourserver.ourdomain.LOCAL
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If there are no MX records for the domain then that is the problem. Nothing you can do about it -- they can't receive email.
It's not your problem, it's theirs.
It's not your problem, it's theirs.
ASKER
Hi Jeff,
No domain exists, they seem to have let it go or made it up!.
Any ideas regarding our own internal mails returning invalid@email.address?.
No domain exists, they seem to have let it go or made it up!.
Any ideas regarding our own internal mails returning invalid@email.address?.
HI,
Can you please verify you get the same error by using outlook web access when sending to internal users (should use imap for delivery)?
if you still get the same error, can you verify under NSLOOKUP/DNS
that ourserver.ourdomain.LOCAL has A record and PTR record set?
is it possible that you make those tests when logged on to the server itself?
Can you please verify you get the same error by using outlook web access when sending to internal users (should use imap for delivery)?
if you still get the same error, can you verify under NSLOOKUP/DNS
that ourserver.ourdomain.LOCAL has A record and PTR record set?
is it possible that you make those tests when logged on to the server itself?
ASKER
Hi when I run DNS i get
*** DOMAIN>LOCAL cant find dns: non-existant domain.
*** DOMAIN>LOCAL cant find dns: non-existant domain.
Hi Dlogan83,
I need to know few things before we continue.
1. do you have an admin access to your server ?
2. is your server windows server 2003 with service pack 2 32 or 64 bit, and what service pack is your exchange setup?
3. just to make sure, when you say you've ran DNS did you use nslookup from the server itself?
4. when you type the server's ip address under nslookup do you get the full FQDN
as an answer (indicates that PTR record exists on the dns server)
5. can you send to internal users using OWA ? (outlook web services, should be under http://servername/owa OR HTTPS://servername/owa)
6. please download and install support tools for your server (if 32 bit then http://www.microsoft.com/en-us/download/details.aspx?id=15326 ) and run the tool NETDIAG and post results.
if you are having any troubles with one of the steps please post back with any question in regards, I need full answers in order to help you..
Gilad
I need to know few things before we continue.
1. do you have an admin access to your server ?
2. is your server windows server 2003 with service pack 2 32 or 64 bit, and what service pack is your exchange setup?
3. just to make sure, when you say you've ran DNS did you use nslookup from the server itself?
4. when you type the server's ip address under nslookup do you get the full FQDN
as an answer (indicates that PTR record exists on the dns server)
5. can you send to internal users using OWA ? (outlook web services, should be under http://servername/owa OR HTTPS://servername/owa)
6. please download and install support tools for your server (if 32 bit then http://www.microsoft.com/en-us/download/details.aspx?id=15326 ) and run the tool NETDIAG and post results.
if you are having any troubles with one of the steps please post back with any question in regards, I need full answers in order to help you..
Gilad
another thing..
check that domain.co.uk (replace with real domain) also does not exists in nslookup query.
you can even try to ping it using the command
ping domain.co.uk
from command line.
execute from the server please..
Gilad
check that domain.co.uk (replace with real domain) also does not exists in nslookup query.
you can even try to ping it using the command
ping domain.co.uk
from command line.
execute from the server please..
Gilad
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
I have ran best practice analyzer and exchange trouble shooter. Which flagged a few errors.
After fixing them I then got 4.4.7 failed messages so i changed our outgoing virtual smtp delivery FQDN back to out web domain rather than our .local and emails seem to go fine again.
should my FQDN be set to my .local address and i use the masquerade domain for out .org.uk domain name?
I have ran best practice analyzer and exchange trouble shooter. Which flagged a few errors.
After fixing them I then got 4.4.7 failed messages so i changed our outgoing virtual smtp delivery FQDN back to out web domain rather than our .local and emails seem to go fine again.
should my FQDN be set to my .local address and i use the masquerade domain for out .org.uk domain name?
No, it should stay as your external domain name. However... The proper way to configure an SBS 2003 is to run the CEICW (Configure Email and Internet Connection Wizard) which will properly fill in all of the configuration items for Exchange to run properly.
Jeff
Jeff
Stop the SMTP service (Simple Mail Transfer Protocol) from start>>run>>services.msc. Wait for some time (let the replication to happen) and start the service and see whether still you are getting the NDR 5 errros?