DNS error -- server not resolving its own name?

I just upgraded all of my DC's from 2000-SP4 to 2003-SP1.  In the process of the upgrade, I moved all of the FSMO roles (all except infrastructure) and authoritative DNS to a new server.  Everything appears to be working properly, but I'm seeing the following DNS error repeat on this new DC.  It appears to be having issues resolving its own machine name.

Type: Error
Source: NTDS Replication
Category: DS RPC Client
Event ID: 1960
Computer: SERVER1

Internal Event:  The following domain controller received an exception from a remote procedure call (RPC) connection.  The operation may have failed.

Process ID 764

Reported error information:
Error Value
The RPC Server is unavailable (1722)
Domain Controller

Extended error information
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond (10060).
Domain Controller

Additional Data
Internal ID

Any ideas?  The RPC service is running on the server.  Replication is running without error to the other DC's.  Name resolution is working properly.  BUT, since it is having issues with its own name, I don't want to ignore it.
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.

similar problem for me yesterday except my system would not resolve its own name when i tried nslookup

if you try the nslookup util on that machine does it resolve itself,

if not, recreate the host record for the server
Greetings blotto99,

  This type of error detaled description and possible solutions are menctioned in this microsoft KB take a look at this


One more link with some interesting discussions in microsoft public groups.


hope this helps

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
You said you moved DNS? Did you change the DNS search order so the DC can find the new DNS server?
blotto99Author Commented:
The errors went away and have not returned after no changes.
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
Windows Server 2003

From novice to tech pro — start learning today.