More information about Subnets and DNS-SD In the example below, it is assumed that the Mobility Print server has an IP address of 10.0.0.6, and clients will connect to subnets 10.0.0.0/24 and 10.0.1.0/24. If creating DNS records for two subnets like 10.0.1.0/24 and 10.0.2.0/24, then 10.0.1.0/23 cannot be used as a shortcut. The subnets that you enter here must exactly match the subnet of the device.These records are also needed when it is necessary to Restrict Printer Access per Subnet.This style of DNS-SD records do not need the DNS Search Suffix to be set on the client.These records are needed if the DNS Search Suffix ends in “.local” because of the way Apple products handle this domain name.and will be automatically generated by the Mobility Print server.
These DNS records are used when the admin specifies that the client has a “.local” DNS Search Suffix or when the administrator enters a list of subnets. Method B (Records go in Reverse Lookup Zones which point to a Conditional Forwarder) These records steer MacOS and iOS clients towards the “pc-printer-discovery” Delegated Subzone. Pictured above are the B and LB pointer records which Apple devices will natively check for. In the example below, it is assumed that the Mobility Print server has an IP address of 10.0.0.6, and clients on the network have a DNS Search Suffix of. This method will not work for iOS and macOS devices if the forward lookup zone or DNS search suffix ends with “.local” because of how Apple devices uniquely handle this top level domain name. Clients with the correct DNS Search Suffix that exactly matches the Forward Lookup Zone where the records are created will be able to discover the printers. These DNS records are used in most situations because they are the simplest to set up and troubleshoot and will be automatically generated by the Mobility Print server. Method A (All records go inside a Forward Lookup Zone) Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used. However, it’s still useful to know exactly what DNS records are getting created and why, especially if you need to delete the records and start over because of changes to your network. (The one exception to this is if you are intending to set up the DNS records for Multiple Mobility Print Servers, which can get a bit tricky.) 
During a normal setup, the Mobility Print server will guide you with questions about your environment to determine the best commands to run on your DNS server to set up the records necessary for clients to discover printing services.
0 kommentar(er)
