Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

SOA Serial numbers do not match

Posted on 2007-04-03
8
Medium Priority
?
3,462 Views
Last Modified: 2009-12-16
I'm having problems sending emails to certain email domain. I am running EX2003 server. I ran the SMTPDiag tool and it came up with "SOA serial numbers no match" error. Does anyone know what the error means? Any help is greatly appreciated.

Searching for Exchange external DNS settings.
Computer name is TAUSINIO.
VSI 1 has the following external DNS servers:
202.70.116.10,202.70.116.11
VSI 3 has the following external DNS servers:
202.70.116.10,202.70.116.11

Checking SOA for bluesky.as.
Checking external DNS servers.
Checking internal DNS servers.
Serial numbers do not match: 42676  2007020202
Serial numbers do not match: 42676  2007020202
Serial numbers do not match: 42676  2007020202
SOA serial number match: Failed with one or more failures.

Checking local domain records.
Checking MX records using TCP: ascc.as.
Checking MX records using UDP: ascc.as.
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Checking MX records using TCP: bluesky.as.
Checking MX records using UDP: bluesky.as.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for ethan.lake@bluesky.as.
Connecting to mx01.blueskynet.as [202.70.116.2] on port 25.
Successfully connected to mx01.blueskynet.as.
0
Comment
Question by:iemmsley
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
8 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 18847566
SOA errors are DNS errors. They have nothing to do with Exchange.
If you have multiple internal DNS servers then one of them is probably not replicating with the others in a timely manner.

Simon.
0
 

Author Comment

by:iemmsley
ID: 18848152
Sembee,

I only have one internal DNS server. How do I fix this problem?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18850154
If you only have one internal DNS server then you shouldn't have this problem.

Do you have external DNS servers in your network configuration? If so, remove them. Rule number one with AD domains - no external DNS servers in the network configuration of any AD clients - servers, workstations or domain controllers.
If you need to use external DNS servers then configure forwarders in the DNS Server applet on the domain controller.

Simon.
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.

 

Author Comment

by:iemmsley
ID: 18861395
All my network configs are pointing to my internal DNS. My Internal DNS already has DNS forwarders configured to an my ISP DNS servers.

Its weird because I ran SMTPDiag to other domain name and they go through without a problem.

?????
0
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 18865042
Do you think this is causing you a problem?
If you don't see any problems with DNS then I would tend to ignore the message.

It isn't clear from your original question whether the domain you were testing was an internal or external domain. If it was an external domain then the problem is out of your control anyway.

Simon.
0
 
LVL 1

Expert Comment

by:maynardinc
ID: 22338471
The person submitting was probably trying to troubleshoot why the Outlook clients run slow sometimes....and going thru the Exchange Troubleshooting document provided by Microsoft.

DNS and Exchange are related, because Exchange uses DNS to deliver mail, even internally. That's what the smtpdiag.exe tool is for.

Let's say that DC1 is the "first" domain controller, and DC2 is the "second". Both are internal, on site.
When you run the smptdiag.exe tool, it checks SOA for the domain.
Then, it checks tcp/udp SOA serial # using the 'first' dns server.
It will tell you if it fails or not.
Then, it checks the 'second' DC.
The error coming back is:
Failed: DNS server (IPAddy) may be down
DNS server (IPAddy) did not return a valid SOA record.
SOA serial number match: Failed with one or more failures.

I think the question is "how do you fix that".
0

Featured Post

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question