Error 404 - Not found - The document you requested is not found

I have been creating the DNS records for a second domain that will be pointing to the same IP address where the Web Site is being hosted.
The current domain - let's call it mydomain.com is working perfectly well, email is going to a In house Exchange server and the website is hosted with ISP.  No problems.  Then we purchased a new domain name -let's call it domain.com  and the DNS entries have been made.  
We are using Small Business Server 2003 R2
I created two host (A) entries:
@  - pointing to the ISP IP address where the website is being hosted
A  - host name is Portal   pointing to External IP of the business Location where the SBS Server is
I also created
www  as CNAME for @
MX  record pointing to Portal (being this the host name of the A entry made poiting to the SBS Server)
The problem is the following:
I use mydomain.com or www. mydomain.com and I get the webpage with no problem
I use domain.com or www.domain.com and I get this error message.
I would like to find out if there is an error in my DNS Entry or is it a problem with the website hosting or code in the webpages that need to be addressed?
All the other entries are working with "domain.com" domain name.
Please let me know.
mcnallyjairoAsked:
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.

Olaf De CeusterCommented:
Use www.dnsreport.com to test domains or post  real domain names and we can do it for you.
Olaf
0
frandshansenCommented:
Maybe it could also be a DNS TTL issue, if your cache still remembers the old configuration of DNS.
0
mcnallyjairoAuthor Commented:
Sorry guys but even though both were right when suggesting their possible solutions the true problem was an error that the ISP had made by not adding the host header to the website in IIS.  The problem was resolved.  Thank you for your prompt and willing help.

Regards
0

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
SBS

From novice to tech pro — start learning today.

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.