Recently die to harware faikure
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
But why are these not happening on all the servers. Amongs 10 servers only 2 servers are complainging ?
Are you saying that the failed DC has permssions to ONLY change A records on the existing and NEW DNS servers ?
IS this error a problem or as it says a WARNING ? How do I remove this issue ?
Dont have DHCP being used at all.
This is not an immediate problem but it will get worse with time as some your DNS records may get out of date. Anything that relies on accurate DNS names will start to fail.
Take a look at the servers which are complaining. Isolate the records for which you get the warnings and take a look at their permissions. Do the DNS servers OR clients (depending on your setup) have the correct permissions to update the A records?
Since you don't have DHCP used, by guess is that DNS relies on clients to register their own DNS names. In this case you're looking for the "Authenticated Users" group's permissions and/or the "Everyone" permissions.
For testing purposes you can give the "Everyone" group full control to a problematic A record and then to an "ipconfig/registerdns" on the client. Make a note of any error messages being generated in your logs. If this works, your problem is permissions based. If it still doesn't work, we will need to keep looking.
Are you using AD integrated DNS?
Of the servers with entries in the event logs the permissions on the A record has no entry for the Server/Client to update. i.e. have looked at the A record of a server/client with no entries in the event log and it has an entry in permissions by its name.
But, in a live network and as we use static IP and records dont change, what is the knock on effect if any of adding the server/client in the permissions ?
As A records dont change , what is the effect if I dont change these settings ?
If you use static addresses, this will just be an annoying message you see in your logs. The clients will try to register themselves in DNS as a matter of course, but even if they fail, everything will keep working. The only thing you need to worry about if when you either change an IP address of an existing client or add a new client. You will have to double check the DNS entry manually to ensure that it's current. Since you do the IP addresses manually, it won't be that much more work to double check DNS settings.
Business Accounts
Answer for Membership
by: astrochimpPosted on 2009-06-30 at 05:19:47ID: 24744440
All of your old records' security settings only allow the old DNS server to modify them. Look at a sample A DNS record's security settings and see who the owner is and what kind of permissions your new server has.
You may want to use DNS dynamic registration credentials in your DHCP properties so that all DNS records are owned by a central account which will stay the same as you switch servers in the future.