• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 375
  • Last Modified:

authoritative domain

We have a domain that has been moved to a new location. I have taken this out of the authoritative domain list and removed from receipents email list but when the server that used to house this domain goes to send it dosesnt go anywhere and you just get a delayed delivery email. I have restarted the server and ensured that this domain dosent appear in exchange console also. Any other ideas or things that have worked for others .............
0
Mr_Wormald
Asked:
Mr_Wormald
  • 10
  • 8
2 Solutions
 
Alan HardistyCo-OwnerCommented:
Please run the following EMS command and advise if the domain is still listed:

Get-AcceptedDomain

Have you updated your GAL / OAB and Address Lists since removing the domain?
0
 
Mr_WormaldAuthor Commented:
The domain is not listed when I run Get-AcceptedDomain.

I forced GAL update using EMS yesterday and this has appeared to work, if I deselect cached mode in outlook but when i reselect the old email domain appears against the contact again. I have emailed both ways but still not leaving the queue.
0
 
Alan HardistyCo-OwnerCommented:
If you are replying to an email that originated on the server, then you will always have problems.

If you create a new email and type in the address in the To field, and don't select a name from the AutoComplete list, then that should also work, but if you select a name from the AutoComplete list, then that too will fail.

Are you doing any of the above?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Mr_WormaldAuthor Commented:
I have deleted all autocomplete entries for this user and retyping the whole email again the the to: field
0
 
Alan HardistyCo-OwnerCommented:
Okay - please lookup the domains MX record(s) on www.mxtoolbox.com and note the FQDN down - e.g., mail.domain.com, then on your Exchange server, from a command prompt, type the following:

nslookup mail.domain.com

What is returned as the answer?  The same IP Address as the mxtoolbox.com page or you Exchange Server's IP Address?
0
 
Mr_WormaldAuthor Commented:
the domain "mydomain.com.au" has two MX records and when I nslookup mail.mydomain.com.au on our exchange it appears with
*** ?????.????.local can't find mail.mydomain.com.au: Non-existent domain
0
 
Alan HardistyCo-OwnerCommented:
Do you have DNS forwarders configured on your DNS Server (Server properties> Forwarders Tab)?

If not - please add the IP Addresses of your ISP's DNS Servers to the Forwarders tab and try the nslookup check again.
0
 
Mr_WormaldAuthor Commented:
We have googles ..... 8.8.4.4 google-public-dns-b.google.com
0
 
Alan HardistyCo-OwnerCommented:
Okay - it has to be hiding somewhere!

Do you have any references to the problem domain in DNS internally?
0
 
Alan HardistyCo-OwnerCommented:
Might be worth losing the Google DNS forwarder and adding your ISP's DNS IP Address for now to test.  You can always put it back again afterwards.

If you can't resolve the FQDN for the mail server - it will be the root of your problem.
0
 
Mr_WormaldAuthor Commented:
we do we house the website internally. In DNS we have

(same as parent folder) | Name Server (NS) | domaincontroller.local | static
(same as parent folder) | Name Server (NS) | exchangeserver.local | static
(same as parent folder) | Name Server (NS) | secondarydomaincontroller.local | static
(same as parent folder) | Name Server (NS) | webserver.local | static
(same as parent folder) | Host (A) | webserver ipaddress | static
www | Host (A) | webserver ipaddress | static

After reading that should we remove the one that points to the exchange server?
0
 
Alan HardistyCo-OwnerCommented:
Okay - if you house the domain in DNS internally, add an A record internally for mail.domain.com and point it to the External IP Address (202.xxx.xxx.18) and you should be fine.
0
 
Mr_WormaldAuthor Commented:
We can now do an nslookup but the email is still not leaving the queue?
0
 
Alan HardistyCo-OwnerCommented:
Okay - you may need to an an MX record internally to as mail.domain.com
0
 
Mr_WormaldAuthor Commented:
so it now looks like this and still not going ...

(same as parent folder) | Name Server (NS) | domaincontroller.local | static
(same as parent folder) | Name Server (NS) | exchangeserver.local | static
(same as parent folder) | Name Server (NS) | secondarydomaincontroller.local | static
(same as parent folder) | Name Server (NS) | webserver.local | static
(same as parent folder) | Host (A) | webserver ipaddress | static
(same as parent folder) | Mail Exchanger (MX | [10] mail.domainname.com.au | static
mail | Host (A) | 202.xxx.xxx.18 | static
www | Host (A) | webserver ipaddress | static
0
 
Alan HardistyCo-OwnerCommented:
From a command prompt on the server, please type:

ipconfig /flushdns

Then can you restart both the DNS Server Service and then the Microsoft Exchange Transport Service please.

Any better?
0
 
Mr_WormaldAuthor Commented:
This is working! we deleted
(same as parent folder) | Host (A) | webserver ipaddress | static
and this seems to have fixed it and we tested the website and this is also still working!

Thanks for your help!
0
 
Alan HardistyCo-OwnerCommented:
Excellent - had to be DNS in one way or another :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

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