Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 87
  • Last Modified:

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?
0
suriyaehnop
Asked:
suriyaehnop
  • 3
  • 3
1 Solution
 
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
 
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
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
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

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now