Brent400
asked on
Exchange and DNS
Do I have to enter an external DNS server for exchange to use or should I us internal DNS?
NutrientMS
Internal. Your exchange server needs to be able to see your Domain Controller.
Sorry, to clarify that. Your internal DNS server should have a forwarder set to your next-hop DNS server (ISP usually). This is so all internal queries go to your Domain Controller and respond, and ones destined for external sites will be passed along to the external DNS server.
Never, have your Exchange or as a matter of fact any one your internal server pointing to external DNS server - ONLY and ONLY your DNS should have forwarders set pointing to external DNS server.
Reason, your internal DNS might not have all the information in the world about DNS servers - this job gets done when you have external DNS set to respond to your queries - this is done by setting the ip address on the forwarders list.
:)
Reason, your internal DNS might not have all the information in the world about DNS servers - this job gets done when you have external DNS set to respond to your queries - this is done by setting the ip address on the forwarders list.
:)
ASKER
That's what I thought and that's the way it is configured.
I guess the problem is more on the DNS server.
My forwarders are set to 198.6.1.1 and 198.6.1.2. These I believe are UU.net servers. Should I be setting them to somthing else or add a few more servers? Add my ISP's?
I guess the problem is more on the DNS server.
My forwarders are set to 198.6.1.1 and 198.6.1.2. These I believe are UU.net servers. Should I be setting them to somthing else or add a few more servers? Add my ISP's?
ASKER
The problem I'm really try to figure out is why I have a few domains that I have trouble recieving email from.
I tested an address using Smtpdiag and DNS was not resolving. I tried the Smtpdiag with the -d option and
I connected. The I tried the standard Smtpdiag with email address and /v option that failed before and it worked fine.
Did the DNS server cache the new IP from the -d option?
I tested an address using Smtpdiag and DNS was not resolving. I tried the Smtpdiag with the -d option and
I connected. The I tried the standard Smtpdiag with email address and /v option that failed before and it worked fine.
Did the DNS server cache the new IP from the -d option?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That should only be an issue if you were trying to send to them yes? If you were having issues receiving from them would mean that either their SMTP server was having issues connecting to your Exchange server on port 25, or if DNS is an issue, if you run an Anti-Spam filter that has Sender Address Verification running if would not be able to resolve the senders email address.
For some testing:
On your Exchange server, open command prompt
open nslookup
type: set type=mx
type: domain.com (obviously the domain you are having issues with)
check the result (google.com MX preference = 10, mail exchanger = smtp1.google.com)
type: exit
type: telnet <nslookup result> 25
eg: telnet smtp1.google.com 25
See if the server responds. If this all works, then outbound SMTP shouldn't be a problem. If it doesn't, post the response of your NSLOOKUP.
Cheers.
For some testing:
On your Exchange server, open command prompt
open nslookup
type: set type=mx
type: domain.com (obviously the domain you are having issues with)
check the result (google.com MX preference = 10, mail exchanger = smtp1.google.com)
type: exit
type: telnet <nslookup result> 25
eg: telnet smtp1.google.com 25
See if the server responds. If this all works, then outbound SMTP shouldn't be a problem. If it doesn't, post the response of your NSLOOKUP.
Cheers.