Confused with sbs2003 exchange setup / dns

Hi.. Im probably doing something very dumb but am having a problem receiving mail in my exchange.  I have set up MX records for autodiscover.domain.dom and remote.domain.dom with a records for both.  i have run the internet and email wizard and tried to repair the system, but I just keep getting mail undeliverable its been a while since i played with SBS 2003.. spoilt by SBS 2K8! anyway, I have the error 5.1.2 bad destination host DNS Hard error looking up but if I ping it, it comes back with my ip address.. must be the exchange server not recognizing the email address at domain name ( .  any help gratefully accepted.

Thanks.. Omar
Who is Participating?
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.

If you look at it seems that you have invalid DNS records for your domain names. Both are pointing to!!!

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
OmarSenussiAuthor Commented:
Strange.. this is the result of my query..:

24 hrs
reported by on Friday, September 02, 2011 at 1:24:15 PM (GMT-5)  a (outside of my firewall/router)
24 hrs
Reported by on Friday, September 02, 2011 at 1:23:40 PM (GMT-5) hosting co.
OmarSenussiAuthor Commented:
Oh.. I see what you mean.. I'll have to have a word with the hosting co... thanks..  I was checking the A records.
Will let you know
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Yep, if the names you gave above are correct.  Your MX records are missing an "r", i.e they're pointing to instead of
OmarSenussiAuthor Commented:
Oh man! I said it was probably something dumb!

Thanks guys.. I think I need a new pair of glasses .. and maybe a brain transplant!

While I'm here, I don't need to have a reference to the in my internal DNS do I? my internal domain is clarus.local.. should I have a OU for
strange that OWA and RWW both work fine..

Thanks again for your help
No. You should have that if your internal domain name was the same as external.
Again you don't need to have two host names listed as MX records (remote and autodiscovery) if they are actually the same server (IP address). Two different MX records you normally use if you have second backup SMTP server which have higher MX value. Autodiscovery DNS record is used only by external outlook clients to automatically discover/setup exchange account.
For basic operation, no you don't need to have a Forward Lookup Zone for  Or an OU, but that's a different matter.

However, if you want to utilize things like Outlook over the Internet (Outlook Anywhere, HTTP over RPC) without having to reconfigure your client each time they switch between inside the network and outside, then I would suggest yes, it would very helpful to configure the Forward Lookup Zone and add entries for remote and autodiscover that point to your internal IP instead of the public IP.  

The only caveat here is that if you have web pages or other resources that live in the domain that are externally hosted, you will need to create entries for them as well that point to their (public) IP, and these will need to be updated manually if they ever change.  You may see this referred to as a "split DNS".  Actually, I think I have come up with a way around this last issue.  Instead of creating a zone called "", create one called "".  Then create a single host (A) record that uses "same as parent" and point it to the internal IP.  Do the same thing for "".  This allows only these names to be resolved, while anything that ends with just "" will still be resolved by external DNS.  To be honest, I've only run this through one test scenario, and it appeared to work great, but I haven't implemented it on my production system yet, so I can't guarantee it, but the logic is sound.

As a side note, maybe I'm remembering incorrectly, but I don't think autodiscover will work with Exchange 2003, even if you're using Outlook 2007 or 2010.
Sorry, normally I do not comment other posts. Footech is right, but only in case if your router does not support DNS loopback, which is really rare case.
You can simply check that with this procedure:
If your owa can be accessed from internet at address (or if SBS 2008) try to access the same address from internal network. If you are able to access it, your router is DNS loopback capable.
@ davorin - No problem.  Discussion is always helpful for clarification.  You're absolutely correct.  Personally I like to implement it even when the router supports loopback, since equipment can change.  And I've experienced the issue enough to always keep it in mind.
OmarSenussiAuthor Commented:
Once again thanks all round.
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

From novice to tech pro — start learning today.