Exchange Server 2003 on win 2003 entr edt. Source:MSExchangeAL Event ID:8231

thank you so much for your help well that's right the exchange is unable to feel the DNS Server. I forgot to tell that there are two network adapter in the exchange server on is for the LAN and configured like this:

Mode: STATIC
IP:          150.1.2.2
subnet:   255.255.0.0
DNS:      150.1.2.1
WINS:    150.1.2.1

the other adapter is for the internet and configured like this

Mode: STATIC
IP:             212.33.150.240
SUBNET:    255.255.255.248
DG:           212.33.150.200
DNS:         212.33.170.10
                212.33.170.20
these numbers are like an example only. I meant to say is the dns in the wan adapter making problems
thank you

I don't recommend dual homing an Exchange server. That usually causes more problems than it is worth. My preference is to have everything inside and then use a router to provide the internet connection.

I would suggest removing the DNS settings from the WAN connection, so that the only DNS available is the internal DNS.
On the domain controller, configure DNS forwarders and use the ISPs DNS servers as the forwarders.

Simon.

First of all I would like to thank you Mr. Simon for all your efforts.
I tried what you said but it didn't work.
I think you are right the problem in the DNS Server I feel that to. but could you tell me how to check the DNS Server and how to solve the problem.

while my DNS Server services is:

-Domain Controller
-DNS Server
-DHCP Server
-Active Dirctory
and there is only one LAN Adapter configured as :
IP:          150.1.2.1
subnet:   255.255.0.0
DNS:       150.1.2.1

thank you

Oh, I someone told to try the NSLOOKUP command to see and I did from a client pc and I got this:
*** Can't find server name for address 150.1.2.1: Non-existent domain
*** Default servers are nhot available
Default Server: Unknow
Address 150.1.2.1
I hope you can find something
thank you

The message about "non-existent domain" is caused by not having a reverse DNS zone on your AD DNS servers.
That is easily fixed by creating a reverse lookup zone in DNS on your domain controller. Make it AD integrated so that it is kept up to date.

If removing the IP addresses from the WAN adaptor didn't work, then I would suggest dropping the machine as being dual homed totally. Put a router in place instead. As I put in a post above, I find that dual home Exchange servers cause more problems and bring no benefit at all to the deployment.

Simon.

Dear mr. Simon
I think I found the problem someone from the IT made changes on the dns and that's way the mail server was crying and there's a ghost image from the server before the changes I restored it and the mail server now is fine.

but the DNS server now is all right except is giving a message in the Event Log like this:
 First:
Even ID: 3000
Descr.
The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.

Second:
Even ID:7062
Descr.
The DNS server encountered a packet addressed to itself on IP address 150.1.2.1. The packet is for the DNS name "_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.alnahdico.com.". The packet will be discarded. This condition usually indicates a configuration error.
 
Check the following areas for possible self-send configuration errors:
  1) Forwarders list. (DNS servers should not forward to themselves).
  2) Master lists of secondary zones.
  3) Notify lists of primary zones.
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server.
  5) Root hints.
 
Example of self-delegation:
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
  (bar.example.microsoft.com NS dns1.example.microsoft.com)
  -> BUT the bar.example.microsoft.com zone is NOT on this server.
 
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result.  If found, the subzone DNS server admin should remove the offending NS record.
 
You can use the DNS server debug logging facility to track down the cause of this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

could you please help me with this
thank you.

It looks your DNS configuration isn't correct.

The way that I set DNS is very easy.

All machines are set to use the domain controllers ONLY for DNS.
The domain controllers point to themselves as primary and another DC as secondary.
On the DNS Server applet forwarders are configured which point to the ISP's DNS servers.

That combination has always worked for me.

If you continue to get DNS errors then I would suggest a post in either the Windows 2003 topic area, or the Microsoft Networking topic area for further assistance.

Simon.

Thank you for everything I will