Windows 2003 DNS not working after IP change

September 29, 2011 at 11:14:09
Specs: Windows Vista
After changing the IP address of my Windows Server 2003 the DNS is not working properly. I get this error,

The DNS server encountered error 32 attempting to load zone from Active Directory.
Event ID: 4521

Any help appreciated, thank you.


See More: Windows 2003 DNS not working after IP change

Report •

#1
September 29, 2011 at 11:22:05
Gee I have a problem. How do I fix it?

How about starting with what the ip address was and what/why you changed it.

Did you update the host and ptr records for the server in dns?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
September 29, 2011 at 11:37:12
Thanks, I can take a bit of sarcasm and whining in return :)

We got a SonicWall TZ200 which ports have been configured individually, so the IP on the previous router used to be 192.168.0.xxx and now is 192.168.168.xxx

I created new DNS records to reflect the change (not 100% sure) and I'm using the SonicWall for DHCP while the DNS is managed by the server (it was like that). If I change the DNS on the domain computers to that of the router they can access the internet but if I point the DNS to the IP of the server they can't. The server can't access the internet either.


Report •

#3
September 29, 2011 at 12:27:20
Did you not understand that you only had to change the sonicwalls lan subnet to match yours? No other network changes required. Please do so.

"If I change the DNS on the domain computers to that of the router they can access the internet but if I point the DNS to the IP of the server they can't. The server can't access the internet either."

Of course. You changed the dns servers ip but none of the ips listed for hosts/ptr records in dns.

Simplest solution is change the sonicwall lan subnet to the same one you have previously and put the servers ip address back the way it was.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
September 29, 2011 at 12:45:51
The subnet mask remained the same after the hardware change 255.255.255.0 before and after, however the IPs did change. The server's IP can't go back though it might be the simplest solution. We have a new set up of IP Range per Port on the SonicWall and we have to get it to work the way it is.

I restarted the server and the error chnaged from Event ID: 4521 previouly mentioned to these two,

Event ID: 4015 -- The DNS server has encountered a critical error from the Active Directory.

Event ID: 4004 -- The DNS server was unable to complete directory service enumeration of the zone...


Report •

#5
September 29, 2011 at 14:48:35
You will need to go into the DNS server and change every host and ptr record to the new ip addressses being used starting with the servers. Best of luck.

whoever setup the sonicwall messed you over not understanding your ip plan.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#6
September 29, 2011 at 17:38:09
I messed it up myself. I did all the changes and I intend to learn from the solutions. In any case I found an entry in Forwarders (domain's forwarder IP address list) pointing to the previous router IP, I might've done that trying things. I deleted the entry and immediately both the server and the domain PCs resumed access to the internet.

I still get the error Event ID: 4015 though, so if any ideas please post them here.


Report •

#7
September 29, 2011 at 22:16:59
Hi all,

Brduran, You are facing an issue related to DNA server AD integration,
Try doing the troubleshooting:
Restart the DNS Server service:

On the DNS server>start Server Manager>click Start>click Administrative Tools>click Server Manager.
In the console tree>expand Roles>expand DNS Server>expand DNS.
Right-click the DNS server>click All Tasks>then click Restart.
If the problem persists, restart the computer, use Server Manager to confirm that the DNS Server service has started.

Now restart the computer.
Now confirm that the DNS Server service has started or not:

On the DNS server>start Server Manager.
In the console tree>expand Roles>click DNS Server.
The System Services list shows the state of the DNS Server service.

Now please verify that Event IDs 4523 and 4524 are being logged and no events in the range 4000 to 4019 appear in the DNS event log.
Thank you
Anil
www.lepide.com


Report •

#8
September 30, 2011 at 11:07:05
Thank you,

Restating the DNS server doesn't yield any errors. The error Event ID: 4015 happens when I restart the server.


Report •

#9
September 30, 2011 at 14:28:49
have you gone into ad sites and services? old ip range listed here?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#10
September 30, 2011 at 15:01:55
Nope, no IP range. It has reference to Default-First-Site-Name but no IPs at all.

Report •

#11
October 1, 2011 at 08:04:15
Following the recommendation by Dave Patrick on this thread
http://social.technet.microsoft.com...

I disabled the Hamachi VPN and restarted the server, the VPN came back enabled again but this time (notice below) the LAN Adapter appears on top and the VPN second. Error Event ID: 4015 went away and now everything is working fine.

Out of curiosity, how's that related to Active Directory?

SERVER ipconfig /all

------------------------------------------------------------------------Windows IP Configuration

Host Name . . . . . . . . . . . . : serv03sb
Primary Dns Suffix . . . . . . . : tecnician.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : tecnician.local

Ethernet adapter LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21143-Based PCI Fast Ethernet Adapter (Generic)
Physical Address. . . . . . . . . : 00-60-67-36-D9-C9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.168.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.168
DNS Servers . . . . . . . . . . . : 192.168.168.8
Primary WINS Server . . . . . . . : 192.168.168.8

Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-59-64-63
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
IP Address. . . . . . . . . . . . : 5.89.100.99
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 5.0.0.1
Lease Obtained. . . . . . . . . . : Saturday, October 01, 2011 7:20:20 AM
Lease Expires . . . . . . . . . . : Sunday, September 30, 2012 7:20:20 AM


Report •

#12
October 13, 2011 at 22:23:22
Hi,

I would like to suggest you refer to the following threads for more ideas:

event id: 4521

http://social.technet.microsoft.com...

DNS event ID 4521

http://social.technet.microsoft.com...

Event ID 4521/Error 32 while trying to set up new domain controller

http://social.technet.microsoft.com...

go through some articles like: http://www.manageactivedirectory.com/

Hope this helps.

Best Regards,


Report •

Ask Question