The Domain Master Browser is necessary on a routed TCP/IP network, that is, when a Windows domain spans more than one TCP/IP network. When a Windows domain spans multiple subnets each of the subnets has an independent browser called the Master Browser. The Master Browser is responsible for the browse list within its respective subnet and portion of the domain on its subnet. The Domain Master Browser is used to collect information from each of the Master Browsers via the NetServerEnum API call. Once collected the list is merged with the Domain Master Browsers list for its own subnet. This merged list forms the enterprise wide browse list for the domain. This merged list is then distributed to the Master Browsers in each subnet so that the enterprise list can be available to computers requesting services.[1]
As part of the Microsoft Windows Server Operating Systems, the browser service is used to host information of other Windows computers within the same Windows domain or TCP/IP network...[2] the Domain Master Browser coordinates browse lists from all the local browsers in a workgroup, no matter what their network segments.[3] Browsing in these terms is specific to viewing network resources within the Windows network such as the available domains and computers. The information, called a Browse List, is held by the browser and primarily consists of the computer names and the services each of the computers offers. There are several browser roles: the Backup Browser, the Master Browser, and the Domain Master Browser.
The Domain Master Browser is located on the domain Primary Domain Controller, or PDC.[4]