SRV records are used to specify the location of a service inside an infrastructure. For example, if you have a web server in the infrastructure, using an SRV record, you can specify the protocol, service, and domain name and define the service location. In an AD environment, SRV records are important as they have been used to locate the domain controllers in the infrastructure. In the previous chapters, I explained AD sites; if you have multiple sites when a user logs in, system needs to point the user to site's local domain controller instead of the domain controller in the hub. This is done via SRV records.

In an SRV record, the following information can be specified:

• Service: This will define the service this SRV record is assigned with.
• Protocol: This will define the protocol it will use. It can be either TCP or UDP.
• Priority: This will define the service priority if the service supports this function.
• Weight: This will help define the order it should serve along with the similar type of records.
• Port number: This will define the service port number.
• Host offering this service: This will define the server offering this particular service. It needs to use FQDN.

The AD-integrated DNS environment has a set of default SRV records created.

SRV records can be listed using the following command:

Get-DnsServerResourceRecord -ZoneName "REBELADMIN.COM" -RRType "SRV"

Detailed output can be viewed using the following command:

Get-DnsServerResourceRecord -ZoneName "REBELADMIN.COM" -RRType "SRV" | Select-Object -ExpandProperty RecordData