On 08/06/2021 02:10, Mike Wright wrote:
Perhaps a lot of the confusion comes from the dual uses of the term:
primary in search order (which is random)
primary source for zone data (which is fixed by an SOA)
To make matters more confusing there are more complex setups where the zone masters are also clients making them both primary and secondary.
I would state that somewhat differently. (And while, yes, violating my goal of not introducing tangents
in threads seeking answers.)
I would say that confusion arises when terms are used interchangeably when they shouldn't be. This
often happens when the meaning of the terms are understood based on context. The confusion can
be worse when the individual with different subject matter knowledge are involved in the conversation.
Anyway, I feel it would be helpful to use terms in a more consistent and "proper" manner.
primary/secondary should be used when discussing name resolution. The "old school" way of thinking
about this would be the order in which DNS servers are listed in /etc/resolv.conf. The first entry being
primary with subsequent entries being secondary.
master/slave should be used when speaking of the data held in DNS servers. That would coincide with
the terms used in, for example, the "zone type" declaration within the named.conf file of bind.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
