Computing.Net > Forums > Windows Server 2003 > Exchange DNS problems

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Click here to start participating now! Also, check out the New User Guide.

Exchange DNS problems

Reply to Message Icon

Name: Ghoti
Date: January 19, 2007 at 08:44:56 Pacific
OS: Windows Server 2003
CPU/Ram: 3GHz Xeon / 2GB
Product: Gateway
Comment:

I'm having some problems setting up an Exchange server, and I think it's because I have my DNS server set up incorrectly. I have an A record set up for mydomain.com, and then a CNAME record set up for mail.mydomain.com. When I do an nslookup on mail.mydomain.com, I get the correct (local) IP of 192.168.0.1, however when I try to ping mail.mydomain.com, it doesn't work because it's trying to ping the global IP of the server. This doesn't make a lot of sense to me. Any ideas?

From a client computer, all of the emails I try to send to another local user get bounced back with this error:

#5.1.8 smtp;553 5.1.8 <swieser@mydomain.com>... Domain of sender address user@servername.local does not exist>

Thanks in advance,
Scott



Sponsored Link
Ads by Google

Response Number 1
Name: Ghoti
Date: January 19, 2007 at 09:48:27 Pacific
Reply:

P.S. The MX record for mydomain.com points to mail.mydomain.com


0

Response Number 2
Name: heropsycho2177
Date: January 19, 2007 at 09:49:36 Pacific
Reply:

Why are you using a CNAME record?

"#5.1.8 smtp;553 5.1.8 <swieser@mydomain.com>... Domain of sender address user@servername.local does not exist>"

Your recipient policies then don't have mydomain.com in them to stamp your user accounts with that address...

"Enough, enough bowing down to disillusion!
Hats off & applause to rogues & evolution!
The ripple effect is too good not to mention.
If you’re not affected, you’re not paying attention!"


0

Response Number 3
Name: Ghoti
Date: January 19, 2007 at 13:27:01 Pacific
Reply:

I'm using a CNAME record because I have no idea what I'm doing. I changed the CNAME record to an A record. I also changed the recipient policies to have mydomain.com instead of myserver.local, and that completely fixed the problem.

Thanks a lot!


0

Response Number 4
Name: heropsycho2177
Date: January 19, 2007 at 13:43:49 Pacific
Reply:

As a precaution, I would highly recommend you run dcdiag to check for DNS issues that could be related to AD. Doesn't hurt or cost anything, and you could avert a potential problem down the road.

Glad I could help you otherwise!

"Enough, enough bowing down to disillusion!
Hats off & applause to rogues & evolution!
The ripple effect is too good not to mention.
If you’re not affected, you’re not paying attention!"


0
Reply to Message Icon

Related Posts

See More


OS Restart after login sc... Windows Updates Notificat...



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Exchange DNS problems

DNS problem www.computing.net/answers/windows-2003/dns-problem/6616.html

dns problem www.computing.net/answers/windows-2003/dns-problem-/3649.html

1 SERVER run IIS Exchange DNS VPN www.computing.net/answers/windows-2003/1-server-run-iis-exchange-dns-vpn/2759.html