Setup DNS

[Guest]

Hello
I have a win 2K Server with dns installed, AD installed and Exchange 2003
installed. I pull my email from 2 pop 3 accounts from my website host mail
server (my hosted domains). I also use a product called MailEssentials.

MailEssentials pull the mail down from pop 3 (no problem with that), it
passes it on to Exchange to be delivered (internal AD domain).

However, DNS seems to be providing some issues. I cannot send any email, it
says:

The destination server for this recipient could not be found in Domain Name
Service (DNS). Please verify the email address and retry. If that fails,
contact your administrator

I have dns zones setup for forwarding, but Im suspecting because of the
newby I am, they are incorrect.

Can anyone suggest anything that will allow me to send email (from outlook).
Normally, in outlook, I could just use my pop3 accounts and the smtp server.
But now in outlook, I have it setup to get email from exchange. Now when I
send email, it attempts to use exchange/dns to send the mail, which is
misconfigured somewhere.

 

[Herb Martin]

Hello
I have a win 2K Server with dns installed, AD installed and Exchange 2003
installed. I pull my email from 2 pop 3 accounts from my website host
mail
server (my hosted domains). I also use a product called MailEssentials.

MailEssentials pull the mail down from pop 3 (no problem with that), it
passes it on to Exchange to be delivered (internal AD domain).

However, DNS seems to be providing some issues. I cannot send any email,
it
says:

Sending mail has nothing to do with (most of the above)
Pop server etc.

The destination server for this recipient could not be found in Domain
Name
Service (DNS). Please verify the email address and retry. If that fails,
contact your administrator

Where does this appear? In Exchange logs or on clients
or on your external SMTP server?

In general (and you may need to ask Exchange specific questions
by cross-posting reasonably to the Exchange newsgroup) a sending
email server must use a DNS which can resolve the address so
if you suspect DNS, start with the CLIENT SETTINGS (of the
machine having the problem, e.g., the Exchange server client
settings) on the NIC->IP Properties->DNS server.

For internal machines that should ONLY contain the (internal) DNS
server (set) that resolve all internal (and external) names -- it must
NOT contain a mixed list of internal/external DNS servers as this
is unreliable and will offer intermittent results.

If it's an internal DNS client and points to an internal DNS server
then that server must be able to resolve BOTH internal and external
names (usually by forwarding the external requests.)

Chase the resolution from CLIENT command line (use NSLookup
or similar tools) to the immediate DNS server; then from the
command line of the DNS server to the forwarder (if any) and
make sure the entire chain works for names in general and the
particular names causing problems in specific.

I have dns zones setup for forwarding, but Im suspecting because of the
newby I am, they are incorrect.

Can anyone suggest anything that will allow me to send email (from
outlook).

Where does Outlook send the email? "Where" means to
which server (Exchange, SMTP, etc) does the Outlook
client use to send the email?

Generally this should be the Exchange server or an SMTP
server.

Outlook would NOT be sending the email directly to the
final destination so it would NOT be resolving the name
of the (final) recipient SMTP server but only the outbound
Exchange or SMTP.

Your OUTBOUND SMTP or Exchange server will be the
one trying to send the email to the final destination UNLESS
you are required to transmit it through an ISP or other relay
(many ISPs do this to control spam originating WITHIN their
network.)

Normally, in outlook, I could just use my pop3 accounts and the smtp
server.
But now in outlook, I have it setup to get email from exchange. Now when
I
send email, it attempts to use exchange/dns to send the mail, which is
misconfigured somewhere.

Likely the DNS settings of the Exchange server are (part of) the
source of the problem.

Start there with commands like:

nslookup -q=MX microsoft.com IP.Address.DNS.Server

By putting in the EXPLICIT IP Address of the target DNS
server(s) you can work through each one in the chain (internal,
Forwarder, etc) and prove that all are working or find the
culprit.

Notice that you must run such commands to test EVERY
DNS Server entry on the NIC->IP properties (not just one
or some of them.)

DNS clients expect EVERY DNS server listed to be
able to provide not only ACCURATE but also COMPLETE
(internal and external etc) resolution.

 

[Jmnts]

Hi

Smtp:
Assuming there is a constant Internet connection, Exchange sends Internet
mail by the following methods:

It uses DNS directly to contact the remote mail server.

It routes mail through a smart host that assumes responsibility for DNS name
resolution and mail delivery.



Outbound Internet mail flows through an Exchange Server 2003 server in the
following manner:

- An internal user sends a message to a recipient in a remote domain.

- To determine if the recipient is local or remote, the SMTP virtual server
on the sender's Exchange server uses internal transport functions to query
the global catalog server for the recipient address. If the recipient
address on the message is not in a recipient policy, it is not stored in
Active Directory; therefore, Exchange determines that the message is
destined for a remote domain.

- If necessary, the Exchange server delivers the message to the appropriate
SMTP virtual server.

- The SMTP virtual server uses its IIS metabase information to determine the
method for delivering a message to a remote domain.



The SMTP virtual server on the Exchange server then performs one of two
actions:

- Uses DNS to look up the IP address for the target domain, and then
attempts to deliver the message.

- Forwards the message to a smart host that assumes responsibility for the
DNS resolution and delivery of the message.



More inf: http://www.microsoft.com/exchange/default.mspx





So from the DNS prespective, you only need to confirm that your server can
resolve MX records (mail exchanger).


Start run
Type - Nslookup press enter
(Now you should see which dns is your server using)
Type - Set type=MX
Type - microsoft.com
(now among other records you should be able to see the MX records, this
records are responsible for the Email delivery)
microsoft.com MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com MX preference = 10, mail exchanger = mailb.microsoft.com

The destination server for this recipient could not be found in Domain
Name
Service (DNS). Please verify the email address and retry. If that fails,
contact your administrator

How did you configured the clients, are they Outlook Express Clients or MS
Outlook?
Did you change anything in Exchange Smtp Server? (By default after exchange
setup the exchange is able to send and receive mail)
Is the Smtp Service Started?
How are the exchange queues?
Do you have any FW that prevents The SMTP port (25)?
Are you using Connectors?


For troubleshooting check:
http://www.msexchange.org/tutorials/SMTPDIAGdiagnose-Exchange-2003-SMTP-DNS.html
http://www.microsoft.com/downloads/...c7-925d-4a29-bd42-71e8563c80a9&displaylang=en
For Exchange tools:
http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/tools.mspx


But as Herb said after you check Dns settings you should post this on
Exchange newsgroup


Best Regards
Systems Administrator
MCSA + Exchange