exchange 2013 accepted domain issue

We have put a domain into a new install of exchange server 2013. It so transpires that we have to use this domain on a different network so we have deleted the domain from accepted domains. Also removed addresses on mailboxes and checked the domain had been removed with ADSI edit.
But now we try to send to this domain we get it stuck in queue with 4.4.1 error encountered with primary target IP address

Any ideas?
techies123Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
Did you checked send connector settings. Check DNS also. It seems you are unable to resolve it.
techies123Author Commented:
Can ping the domains
AmitIT ArchitectCommented:
Are you able to do telnet to that domain on Port 25. Possible chances it might be blocked via firewall.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Get the Guide
techies123Author Commented:
It is receiving emails from everyone else except our new domain.
techies123Author Commented:
I believe it is a problem because we put it into exchange 2013
AmitIT ArchitectCommented:
Test using telnet. Use telnet to submit an email and share the result.
Murali ReddyExchange ExpertCommented:
Do you use any email provider for scanning outboud/inbound emails? See if there is any mention of the domain in their records.

Also see if there are any send connectors or transport rules for that address space causing the failure.

Or else create a dedicated send connector for that address space and point to the new domain's HUB server (as smart host), as a work around till you figured it out.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.