• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 290
  • Last Modified:

DNS Server Problem - DNS Not Being Updated


Have a problem with DNS Server, running on Windows 2008 Server and Windows 2003 Server.
Here is the scenio.

1) Primary Domain Controller was a Windows 2003 Server.  
2) Have some other Windows 2003 and 2008 domain controllers that were also DNS servers
3) PDC crashed and died this past weekend.
4) Made another Windows 2003 Server (DC) the PDC.
5) I accidently created a new PRIMARY ZONE on the PDC and lost all DNS info.
6) So, now have DNS running on 2 DCs and secondary zones running on some 2003/2008 file server/exchange servers.
7) Here is the problem.....  DNS is not updating HOST A records for PCs and I am having to manually add the HOST A records.  

Obviously I made a mistake when I created a new primary zone.....losing everything....but now it is not working properly.  The 2003 PDC and 2008 DC are both DHCP servers (1/2 the IP addresses on each server)

What have I done wrong and how can I get DNS to perform dynamic updates?

Also, want to do DNS replication to all DNS servers, but it will only allow me to do DNS replication to Domain Controllers.
  • 3
  • 3
3 Solutions
Henrik JohanssonSystems engineerCommented:
In zone properties, change the property of "dynamic updates" to allow either "Secure only" (AD-integrated zones can be restricted to only allow AD-members) or "Nonsecure and secure"
When having dynamic DNS-zones, also remember to enable automatic aging/scavenging (zone-properties->aging and server-properties->advanced), or you will in the time end up with orphan data when not automatically scavenge old stale records.

AD-integrated DNS-zones can only be hosted on DCs. To have member servers acting as DNS servers, you nead to configure the member servers to host secondary zones of the AD-zones.
rstuemkeAuthor Commented:
Cannot replicate DNS to all servers in the domain.

Tells me  "the name limit for the local computer network adapter card was exceeded"
Henrik JohanssonSystems engineerCommented:
As described in this KB, it sounds like you have a stub zone with the same name as the AD-integrated zone. Remove the stub zone.

This KB includes a hotfix for the problem.
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

rstuemkeAuthor Commented:
No stub zone in the site.  Check all of the DNS servers.  However, did have one before this problem occurred.  How would I find it?  The servers that had them, had the DNS zones deleted and had secondary zones created.  Any idea?
Henrik JohanssonSystems engineerCommented:
AD-integrated zones will be replicated between DCs, so I guess having secondary zones on DCs can cause the same scenario as having stub zone when trying to change the replication scope.
* AD-integrated zones on DCs
* Secondary zones on DNS servers that isn't DC.
rstuemkeAuthor Commented:
Deleted all the secondary zones and now just use DNS servers running on DCs.   Working much better.  
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now