Server 2003 Standard DNS Errors, Error 32 attempting to load zone with Active Directory

As it said, it may be just a transient condition. It normally occurs when booting up a Domain Controller (if at all). Is that when you see the message? If you open up the DNS console can you see all your zones?

Chris

it only showes me the Zone i created, not the default MS settings like all my other servers.

"Default MS Settings", what are those?

Do you mean it's not showing you a replicated version of the zone? And that you added a zone? If so, what type of zone did you add?

Generally, if you have an additional DC you don't need to add zones at all. Any zone set to AD Integrated will appear on the DC a short time after it successfully replicates.

Chris

The zone ZONE1 is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

This is what i am getting now.  nslookup does not work on the server,  This is the new PDC in the active directory.  

There's not really enough detail here for me to even begin telling you what's wrong at the moment. I need to know a few things about your environment to build up a picture of where you stand.

Do you have any other Domain Controllers in this domain? Or is this a new Domain Controller for a new Domain and Forest?

> nslookup does not work on the server

What do you mean by this? I'm afraid it's a pretty useless statement at the moment. NSLookup always works, it is entirely possible the DNS Server you're trying to query doesn't.

Basically, please be specific if you want us to help you. Perhaps paste the error message if you're not sure what you're looking at.

Chris

I havd another 2k3 standard server that was running DHCP, DNS, File sharing, and Exchange.  This server has a bad perc controler.    So we have replaced this with another server.  due to hardware, HD's and speed.  The new server is setup as 2003 server standard, and is the PDC.  I have DHCP, DNS, Files shring, and Exchange setup on here.  After i setup DNS it gave me theh error 32.  It has never looked right to me from the start.  The two domain's have not been on the network the same time.  So what i would like to do is set this server up just like the other server i had setup 5 years ago.  It is the only DNS server in the network.    The only problems i am having is a very slow network due to DNS not running properly on the server.
As for the NSLOOKUP, when i run ths command in dos it says "DNS request timed out.  ***can's find server name ofr address 172.16.1.100: timed out.  Default server: unknown    address 172.16.1.100"
below is the DNS event log error
The zone ZONE1 is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.


Thanks for the help.
 

i guess what i am talking about is under the old server i have a zone named _msdcs.mydomain.com  and under this zone i have a number of settings DC, Domains, GC, PDC,

my new server does not have any of these entry's  Thanks again.

This one first because it has an easy explanation.

> DNS request timed out.  ***can's find server name ofr address172.16.1.100: timed out.  
> Default server: unknown    address172.16.1.100

You get this error if there's no PTR Record in a Reverse Lookup Zone for the server you're using NSLookup again.

Add the Reverse Lookup Zone for your IP Range, run "ipconfig /registerdns" and that problem should disappear.

The important thing to note about that is while it complains it's harmless. It won't cause you name resolution problems.

Can you at the moment lookup www.google.com (nslookup www.google.com)? If not, do you have any Forwarders configured on your DNS Server? That's Properties for the server in the DNS Console, then the Forwarders tab.

What value is currently in the SOA Record? And the NS Records?

If it's a new server you might have more luck simply deleting the existing zone and adding a new one as Primary, AD Integrated (with all DNS Servers in the Domain as the replication scope).

The Service Records, those under _msdcs, are supposed to be dynamically registered by the NetLogon Service. As such you can force it to try and register them by restarting that service. They don't necessarily appear in their own zone, they can happily exist under the zone for your domain name so don' tbe too put off that you don't see that exact zone name.

Chris

Chris,

I setup my reverse dns, but still no go. I setup a reverse dns and ran dns flush, then registered again but no success.

my forwards work, i was able to resolve google.com.  

the SOA has 2k3server.mydomain.com listed.  

under name servers it will not resolve the server's ip address????

Troy

In the Forward Lookup Zone, is there a Host (A) Record for your server name? I take it mydomain.com is the name of the Forward Lookup Zone, and the name of your AD Domain?

I take it there's currently no _msdcs sub-folder in there?

Are you seeing DNS Registration failures in the Event Log?

Can you let me know the current Replication Scope for the zone?

And if you could note any DNS Servers listed in your servers TCP/IP configuration? It looks like you're fine, but I wanted to verify you have nothing but 172.16.1.100 in there, and that the IP belongs to your server?

Chris

In the Forward Lookup Zone, is there a Host (A) Record for your server name? I take it mydomain.com is the name of the Forward Lookup Zone, and the name of your AD Domain? = NO A RECORD.

I take it there's currently no _msdcs sub-folder in there?
= NO that is what i was talking about earler.

Are you seeing DNS Registration failures in the Event Log?
Yes.  The DNS server encountered error 32 attempting to load zone 1.16.172.in-addr.arpa from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.


Can you let me know the current Replication Scope for the zone?
Sorry i dont know where to find that.

And if you could note any DNS Servers listed in your servers TCP/IP configuration? It looks like you're fine, but I wanted to verify you have nothing but 172.16.1.100 in there, and that the IP belongs to your server?
Yes my servers ip is the only listed.


Thanks again for all the help.