dns:multimaster_dns
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dns:multimaster_dns [2024/04/02 07:52] – [NIOS Multi Master] bstafford | dns:multimaster_dns [2024/08/21 14:33] (current) – [NIOS Multi Master] bstafford | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| Also consider it where GM/GMC are the DNS servers and you want to allow for DNS updates when GM dies and GMC hasn't been promoted yet. Multimaster is okay in smaller scenarios. | Also consider it where GM/GMC are the DNS servers and you want to allow for DNS updates when GM dies and GMC hasn't been promoted yet. Multimaster is okay in smaller scenarios. | ||
| - | Dynamic updates take priorities | + | Dynamic updates take priority |
| + | Example: If you have eight DC spread globally and each DC has a NIOS DNS server, do not make all of them Multi-master. Way too many. You should max it out at 3 or possibly 4. Remember, each primary has to feed its changes back up to the Grid Master. The GM has to then soft it out and track info and serial numbers for each primary and then redistribute it out. (Microsoft would just add it to LDAP for replication). This is all doubly true if Dynamic DNS is involved and even more so with GSS_TSIG. | ||
| + | |||
| + | NOTE: You cannot have multi-master enabled on a zone that has DNSSEC signing enabled. | ||
dns/multimaster_dns.1712044348.txt.gz · Last modified: by bstafford
