SOA Serial numbers do not match

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.
iemmsleyAsked:
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.

SembeeCommented:
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
iemmsleyAuthor Commented:
Sembee,

I only have one internal DNS server. How do I fix this problem?
0
SembeeCommented:
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.

iemmsleyAuthor Commented:
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
SembeeCommented:
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

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
maynardincSysadminCommented:
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
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.