[newbe]

Hi WE are runing windows server 2003 We have changed isp to a different ip address range out dns has now been screwed up Is thre a quick fix or is it a rEvent Type: Information Event Source: DNS Event Category: None Event ID: 800 Date: ...

Hi

WE are runing windows server 2003 We have changed isp to a different ip address range out dns has now been screwed up Is thre a quick fix or is it a rEvent Type: Information

Event Source: DNS
Event Category: None
Event ID: 800
Date: 05/02/2009
Time: 20:32:42
User: N/A
Computer: LEX
Description:
The zone Test 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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ebuild of the server the error message are as follows

Then we get
Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 800
Date: 05/02/2009
Time: 20:32:42
User: N/A
Computer: LEX
Description:
The zone 3.168.192.in-addr.arpa 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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date: 03/02/2009
Time: 22:15:02
User: N/A
Computer: LEX
Description:
The DNS server encountered error 32 attempting to load zone tested 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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.