mail2clk
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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)?
Is the domain correctly spelled? Did someone internally send to it? Who is the sender of the message (internal user or Administrator / Postmaster)?
ASKER
i can send an email from administrator to administrator internally.
Is the domain a domain external to your mail server or an internal domain that you are hosting?
ASKER
Domain company.co.uk is external.
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
Thanks
Alan
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Claranet confirmed we are not blacklisted.
Okay - but please visit the link and check your fixed IP Address - just for my peace of mind!
ASKER
Looks ok blacklist:79.123.xxx.xxx. Please delete address
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dns address is set to itself the server ip address. passed the test, flushed dns but cannot find mx non-existent domain.
Are you using DNS forwarders and are they correct?
ASKER
yes dns is correct
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Could it be a server issue ? Why would the domain be non-existent?
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\driver s\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.
You may also have an entry in the hosts file on your server for some daft reason. Please check c:\windows\system32\driver
Any entries in there for this domain? If so - delete the lines please.
ASKER
Nothing in either file.
Okay - did you see my earlier comment?
ASKER
i checked another server with a different company same setup and the message cannot find domain comes up but emails work fine
ASKER
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.
Okay - please talk to your ISP as you are using their forwarders - they may be able to throw some light on this.
Alan
Alan
ASKER
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.
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.
Brilliant - thanks for the update.
A bit heavy-handed - but if it worked - I won't knock it.
A bit heavy-handed - but if it worked - I won't knock it.
So nothing I said helped you in any small way to resolve the problem?
ASKER
I need to allocate some points.
ASKER
I provided my own solution.
ASKER
a message comes up. server.company.local. cannot find mx. domain is non-existent.