Exchange Edge 2007 Server

Recently we have inbound mail stuck at Edge server with error 451 4.4.0 DNS Query Failed..due to primary DNS was shutdown. After we switch on primary DNS , the mail flow to internal became normal.

As Microsoft mentioned it was due to this problem commonly occurs as a result of a mistake in the configuration of the DNS settings of the Edge Transport server. Therefore, you can resolve this problem by correcting the DNS configuation.

This is only one times happened in 2 years. So i not sure if this really a DNS configration issue.

The edge server has 2 network cards.

Network1 was label as External Lan has Public IP address (IPv4) and 2 internal DNS assigned.
Network2 was label as Internal Lan has Public IP adddress (IPv4),subnet mask but NO DNS assigned.

The adapter and bindings at "Advanced Settings" was set Network2 at top follow by Network1

The DNS configuration on the Edge Transport server:

Internal DNS Lookups - set to All availablle
External DNS lookups - set to All available.

http://technet.microsoft.com/en-us/library/bb851512(v=exchg.80).aspx

When we reboot Primary DNS, and do nslookup for internal servers on Edge server, nslookup failed to resolve the internal server. It seems that it doesn't query Secondary DNS server when primary DNS not available.

Does the DNS configuration settings is correct on Edge server?
Why nslookup failed when primary DNS reboot?
It is possibility that the "internal DNS lookups" on Edge look for Network 2 (NO DNS assigned) which cause the issue?
LVL 19
suriyaehnopAsked:
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.

Jian An LimSolutions ArchitectCommented:
i wonder why your external lan has internal DNS.


the best practice is if it is external facing, use external dns
and setup the internal facing to use internal dns.
http://technet.microsoft.com/en-us/library/bb124896(v=exchg.80).aspx
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
suriyaehnopAuthor Commented:
I not sure why...this is one of our client.
0
Jian An LimSolutions ArchitectCommented:
can we change it accordingly to the recommendation?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

suriyaehnopAuthor Commented:
afraid not
0
Jian An LimSolutions ArchitectCommented:
as what technet suggest, the proper way is to setup external lan to external dns,  and internal lan to internal dns

so what do you expect from us?
0
suriyaehnopAuthor Commented:
thank you
0
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
Exchange

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.