[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 811
  • Last Modified:

unable to bind to destination server in dns

I am having problems sending and receiving emails. On the message queue is the following message.

unable to bind to destination server in dns

I can ping the dns servers and I am using a smart host relay.

Does anyone have any suggestions?

I was cleaning up some WMI issues previously and I am not sure if this was the cause.
0
mail2clk
Asked:
mail2clk
  • 14
  • 14
4 Solutions
 
Alan HardistyCo-OwnerCommented:
This suggests that the server in question or rather the domain for the email that is stuck, is not working properly, or the domain does not exist.

If you bring up a command prompt and type the following:

nslookup {press enter}
set type=mx {press enter}
problemdomain.com {press enter} (change problem domain with the domain name you are having issues with)

What response do you get?
0
 
mail2clkAuthor Commented:
after entering MX

a message comes up. server.company.local. cannot find mx.  domain is non-existent.

0
 
Alan HardistyCo-OwnerCommented:
Then that is the answer - the domain does not exist.

Is the domain correctly spelled?  Did someone internally send to it?  Who is the sender of the message (internal user or Administrator / Postmaster)?
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
mail2clkAuthor Commented:
i can send an email from administrator to administrator internally.
0
 
Alan HardistyCo-OwnerCommented:
Is the domain a domain external to your mail server or an internal domain that you are hosting?
0
 
mail2clkAuthor Commented:
Domain company.co.uk is external.
0
 
Alan HardistyCo-OwnerCommented:
Okay - please post the full domain name (which I will obscure to protect their identity) so I can check to see what is up.

Thanks

Alan
0
 
Alan HardistyCo-OwnerCommented:
Okay - I see that they use Messagelabs to filter their email.

Testing a connection to them from my IP I can easily connect to both MX records - which might suggest that either you cannot resolve their name in DNS which means your DNS settings ar enot correct, or you might be blacklisted by them.

Can you check your IP Address on www.mxtoolbox.com/blacklists.aspx and make sure you don't pop up on any blacklists please.
0
 
mail2clkAuthor Commented:
Claranet confirmed we are not blacklisted.
0
 
Alan HardistyCo-OwnerCommented:
Okay - but please visit the link and check your fixed IP Address - just for my peace of mind!
0
 
mail2clkAuthor Commented:
Looks ok blacklist:79.123.xxx.xxx. Please delete address
0
 
Alan HardistyCo-OwnerCommented:
Yep - looking good.

Okay - so that leaves DNS issues!

On your server - what is the Server's LAN DNS IP Address set to?  It should be itself and nothing else.

Have you got DNS forwarders setup on the Forwarders TAB of the DNS server?  Start> Programs> Administrative Tools> DNS> Right-Click Server Name and choose Properties> Forwarders Tab.

You should have your ISP's DNS Server IP Addresses configured here.  If not - please add them, click Apply, then click on the Monitoring Tab and check both Test Types (Simple / Recursive) and click Test Now.  If you see PASS PASS in the Test Result window all is well.  Uncheck both Test Types and click OK.

Then return to the command prompt and type:

ipconfig /flushdns

then

nslookup {enter}
set type=mx {enter}
theirdomain.co.uk {enter}

Any better?
0
 
mail2clkAuthor Commented:
Dns address is set to itself the server ip address. passed the test, flushed dns but cannot find mx non-existent domain.
0
 
Alan HardistyCo-OwnerCommented:
Are you using DNS forwarders and are they correct?
0
 
mail2clkAuthor Commented:
yes dns is correct
0
 
Alan HardistyCo-OwnerCommented:
Can you add 158.43.240.4 to the DNS forwarders and then make sure it is at the top of the list, then In DNS Admin Tool, right-click the Servername and choose Clear Cache and then Right-Click and Choose Scavenge Stale Resource Records.

Re-run the command prompt check.

Any better?
0
 
mail2clkAuthor Commented:
Could it be a server issue ? Why would the domain be non-existent?
0
 
Alan HardistyCo-OwnerCommented:
It is only non-existent to your server because it can't find it in DNS!

You may also have an entry in the hosts file on your server for some daft reason. Please check c:\windows\system32\drivers\etc hosts and lmhosts.sam (both should open with notepad.exe easily.

Any entries in there for this domain?  If so - delete the lines please.
0
 
mail2clkAuthor Commented:
Nothing in either file.
0
 
Alan HardistyCo-OwnerCommented:
Okay - did you see my earlier comment?
0
 
mail2clkAuthor Commented:
i checked another server with a different company same setup and the message cannot find domain comes up but emails work fine
0
 
mail2clkAuthor Commented:
I added the ip address in the forwarders and cleared cache and scavenge stale records. Dean the command and the same message.non-existent domain.
0
 
Alan HardistyCo-OwnerCommented:
Okay - please talk to your ISP as you are using their forwarders - they may be able to throw some light on this.

Alan
0
 
mail2clkAuthor Commented:
Alan

I got it to work. Thanks for your help

I followed these steps.

To work around this issue, remove the external DNS server references in Exchange System Manager, and then restart Microsoft Internet Information Services (IIS).

To remove the external DNS server references, follow these steps:
Start Exchange System Manager.
If administrative groups are enabled, expand Administrative Groups, and then expand First Administrative Group.

If administrative groups are not enabled, go directly to step 3.
Expand the Servers container, and then expand the Your_Server_Name container.
Expand the Protocols container, and then expand the SMTP container.
Right-click Default SMTP Server, and then click Properties.
Click the Delivery tab, and then click Advanced.
Click Configure, and then click the first entry in the External DNS list.
Click Remove.
Remove each remaining entry from the External DNS list.
Click OK three times.
Quit Exchange System Manager.
To restart IIS, follow these steps:
Open the Services snap-in.
Right-click the IIS Admin Service, and then click Restart.
In the Restart Other Services dialog box, click Yes to restart the dependency services.
0
 
Alan HardistyCo-OwnerCommented:
Brilliant - thanks for the update.

A bit heavy-handed - but if it worked - I won't knock it.
0
 
Alan HardistyCo-OwnerCommented:
So nothing I said helped you in any small way to resolve the problem?
0
 
mail2clkAuthor Commented:
I need to allocate some points.
0
 
mail2clkAuthor Commented:
I provided my own solution.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 14
  • 14
Tackle projects and never again get stuck behind a technical roadblock.
Join Now