Score:0

DNS best practice for large resilience orientated org

fi flag

I have been asked to investigate the resiliency of our DNS and it's config. What's the industry best practice around this?

The following have been suggested: the DNSAdmin group (which is usually created by default when creating a domain) has been removed from all the DNS servers. I doubt this would cause any issues as there are no members in this group, however what's the easiest way to add it top level and for inheritance to work (tested it in a lab environment and inheritance didn't work).

Thanks.

cn flag
Bob
Are you talking about your internal DNS and resolving (workstations, printers, internal servers and services), or rather your public DNS (your internet presence, your public web site(s), SMTP e-mail and the online services you may offer ) as those are usually rather different, both in purpose, tools and the (operational) risks and threats.
fi flag
It's the internal DNS
fi flag
We have 3 site organisation. The links between all 3 organisation are okay and the bandwidth is more than enough.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.