1.4 Relationship to Other Protocols

The DNS Server Management Protocol relies on RPC [MS-RPCE] as a transport. It is used to manage servers that implement DNS [RFC1035], [RFC1183], [RFC1876], [RFC1995], [RFC1996], [RFC2065], [RFC2136], [RFC2535], [RFC2671], [RFC2672], [RFC2782], [RFC2845], [RFC2915], [RFC2931], [RFC3596], [RFC4034], and [RFC4701]. It also interacts with the Netlogon protocol [MS-NRPC].

The following diagram illustrates the relationship of the DNS Server Management Protocol and how it relates to RPC [MS-RPCE].

Figure 2: How the DNS Server Management Protocol uses RPC

The DNS server relies on the LDAP protocol [RFC4511] to retrieve and modify DNS information when it is stored in a directory server. In this case, the DNS server is the client of the LDAP protocol, acting on behalf of and impersonating (using RPC impersonation), the client of the DNS Server Management Protocol. LDAP's relationship with other protocols is covered in [RFC4511] section 5. Note that although an LDAP provider can support transports other than TCP, the DNS server is required to open LDAP connections specifying the TCP transport using port 389.

The following diagram shows the relationship of the DNS Server Management Protocol to LDAP and TCP:

Figure 3: How the DNS Server Management Protocol uses LDAP

The following diagram illustrates the interaction between DNS Server Management Protocol Clients, DNS Servers, and directory servers.

Figure 4: Relationship between DNS Server Management Protocol Clients, DNS Servers, and Directory Servers