In my very early DNS days, I used to feel uncomfortable typing "slave" though I've become used to it now that I don't think twice. We've had some discussions about this in my previous DNS team about "master" and "slave" in DNS terminology. Note that the preferred terms now are "primary" and "secondary" respectively per RFC 7719. I'll use master and slave below because I want the descriptions to make sense in that context. In DNS, the meaning of master/slave, from a driver perspective, doesn't strictly capture what happens in the DNS protocol. It is the slave that queries the master to do something for it (return zone data), and the master does work on the slave's behalf. It is the slave that drives it - the master strictly cannot instruct the slave to do something (NOTIFY is a notification that a slave can avoid or not even handle). >From a coupling perspective, though the slave for a zone synchronizes its zone data to the data on the respective master, there's no requirement in DNS for the slave to be tightly coupled to the master. i.e., it is the slave's choice whether it feels like updating this moment, and it may not do so, whereby after a time interval it should stop serving the zone. There is also another concept of "master" in DNS which is the master file. Though it describes presentation format (a syntax) for zone data storage, the concept of master here is used analogous to "master copy" e.g, for a video or audio recording, i.e., something like the main copy of the data. When there are other and better terms to describe the entities such as "primary" and "secondary", there's no need to stick to words that offend some people. It may not offend you, but you may not have lived a life in a family/community where such things have affected you. IMO, there's no need to drive out all references to master/slave usage, but newer usage should try to find more appropiate terms, and software should allow usage of alternate terms. If "slave" is the only English term that you can find, just ask a colleague. These are generic usage terms and do not identify a product such as a trademark to cling onto them. E.g., GIMP (GNU image manipulation program) gets a lot of complaints again and again about its name. But re-branding it is not a small feat - it would break a lot of things. One could say GIMP has redefined the term too (e.g., if you do a web search, you'd find very results of the derogatory usage). Master/slave is not like that, at least in my limited area of DNS. Mukund
