Mobility Print DNS Record Examples

KB Home   |   Mobility Print DNS Record Examples

Main.MobilityPrintDNSRecordExamples History

Hide minor edits - Show changes to output

April 11, 2019, at 09:42 PM by Aaron Pouliot -
Changed line 12 from:
*This method will not work for OS 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.
to:
*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.
April 05, 2019, at 05:20 PM by Aaron Pouliot -
Changed line 12 from:
*If the forward lookup zone or DNS search suffix ends with ".local" this method will not work for iOS and macOS devices because of how Apple devices uniquely handle this top level domain name.
to:
*This method will not work for OS 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.
April 05, 2019, at 05:19 PM by Aaron Pouliot - Added mention about .local domains to method A
Added line 12:
*If the forward lookup zone or DNS search suffix ends with ".local" this method will not work for iOS and macOS devices because of how Apple devices uniquely handle this top level domain name.
October 18, 2018, at 06:48 PM by Aaron Pouliot - Added more information about DNS-SD
Added lines 60-66:

!!!More information about Subnets and DNS-SD
We sometimes hear the question ''"can I put in a really big subnet like 10.0.0.0/8 to encompass lots of smaller subnets?"'' or ''"what if I have a /23 subnet?"''.  The answer is that the subnets that you enter in the setup wizard must exactly match the subnets of the clients on the network. Putting in a subnet mask of 255.0.0.0 to encompass a larger range works when setting up rules on a firewall or router, but it may work a bit differently when it comes to DNS-SD and AirPlay.

For an example, assume there is an iPhone with an IP address of 10.10.16.15 and a Subnet Mask of 255.255.248.0. The actual subnet of this device would encompass this range of IP addresses: 10.10.16.1 - 10.10.23.254.When the iPhone queries the DNS server to look for the B and LB pointer records, the DNS server will check inside a reverse lookup zone for 10.10.16.0 (0.16.10.10.in-addr.arpa). This  reverse lookup zone must exists for the iPhone to discover the published printers. A reverse lookup zone of 10.0.0.0 (0.0.0.10.in-addr.arpa) would not match the iPhone's network and would therefore not work.

To get this working, the administrator would need to go back  go back to the DNS setup page on the Mobility Print server and enter in each exact subnet that will be used by the client, with the correct subnet mask. In this example it would be 10.10.16.1/255.255.248.0. Then the administrator would need to run those commands on the DNS server to create the correct records.
June 11, 2018, at 10:39 PM by Aaron Pouliot -
Changed line 9 from:
!!Method A (Delegated Subzone)
to:
!!Method A (All records go inside a Forward Lookup Zone)
Changed line 32 from:
!!Method B (Conditional Forwarder with Reverse Lookup Zones)
to:
!!Method B (Records go in Reverse Lookup Zones which point to a Conditional Forwarder)
May 03, 2018, at 07:03 PM by Aaron Pouliot -
Added lines 6-7:

\\
May 03, 2018, at 07:02 PM by Aaron Pouliot -
Changed line 8 from:
*These DNS records are used in most situations because they are the simplest to set up and troubleshoot.
to:
*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.
Changed lines 31-33 from:
*These records are needed if the forward lookup zone ends in ".local" because of the way Apple products handle this domain name.
to:
*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. and will be automatically generated by the Mobility Print server.
*These records are needed if the DNS Search Suffix ends in ".local" because of the way Apple products handle this domain name.
*This style of DNS-SD records do not need the DNS Search Suffix to be set on the client
.
Deleted lines 34-35:
*These records are also useful if you cannot specify the DNS Search Suffix on your DHCP Scope Options.
*These records are only generated when the admin specifies that the client has a  ".local" DNS Search Suffix or when the administrator enters a list of subnets.
May 03, 2018, at 06:58 PM by Aaron Pouliot -
Added lines 27-28:

\\
May 03, 2018, at 06:58 PM by Aaron Pouliot - Simplified headers
Changed lines 7-8 from:
!!Delegated Subzone Method
*This is
the simplest to set up and troubleshoot.
to:
!!Method A (Delegated Subzone)
*These DNS records are used in most situations because they are
the simplest to set up and troubleshoot.
Changed line 28 from:
!!Conditional Forwarder with Reverse Lookup Zones
to:
!!Method B (Conditional Forwarder with Reverse Lookup Zones)
April 30, 2018, at 05:53 PM by Aaron Pouliot - Added Category MobilityPrint
Added lines 60-61:
----
''Categories:'' [[Category.MobilityPrint|+]]
April 24, 2018, at 05:15 PM by Aaron Pouliot - Added note on subnets
Added line 33:
*The subnets that you enter here must exactly match the subnet of the device.  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.
March 05, 2018, at 07:46 PM by Aaron Pouliot -
Changed lines 3-5 from:
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 set up the records necessary for clients to discover printing services. (The exception to this is if you are intending to set up the DNS records for [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].)

However
, it's still useful to know exactly what DNS records are getting created and why. Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used.
to:
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.  (The one exception to this is if you are intending to set up the DNS records for [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]], which can get a bit tricky.)

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
. Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used.
March 01, 2018, at 07:07 AM by Aaron Pouliot - Edited for clarity.
Changed lines 3-6 from:
The Mobility Print DNS Configuration guide will generate the exact commands that will need to be run for nearly any situation. The exception to this is if you are intending to set up the DNS records for [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].

It
is also useful for troubleshooting to know exactly what DNS records pertain to Mobility Print. Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used.
to:
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 set up the records necessary for clients to discover printing services. (The exception to this is if you are intending to set up the DNS records for [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].)

However, it's still useful to know exactly what DNS records are getting created and why
. Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used.
Changed lines 8-13 from:
*The simplest to set up and troubleshoot.
*Requires that the clients have a DNS Search Suffix that exactly matches the Forward Lookup Zone where the records are created.

!!!What commands would be generated?

Below are sample DNSCMDs that would create DNS records for the domain [=papercutsoftware.com=] where the Mobility Print server has an IP address of 10.0.0.6.
to:
*This is the simplest to set up and troubleshoot.
*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.

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 [=papercutsoftware.com=].

!!!Example Commands
Changed line 21 from:
!!!What records would I see on my DNS server?
to:
!!!Example Screenshots
Changed lines 23-24 from:
Pictured above is the pc-printer-discovery Delegated Subzone. This is what Windows, Android, and Chrome clients will look for.  This  points towards an A record called "pc-mobility-print-host" which resolves to the IP address of the Mobility Print server.
to:
Pictured above is a Delegated Subzone called "pc-printer-discovery" . This is what Windows, Android, and Chrome clients will look for.  This  points towards an A record called "pc-mobility-print-host" which resolves to the IP address of the Mobility Print server.
Changed lines 26-27 from:
Pictured above are the B and LB records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Delegated Subzone.
to:
Pictured above are the B and LB pointer records which Apple devices will natively check for. These records steer [=MacOS=] and iOS clients towards the "pc-printer-discovery" Delegated Subzone.
Changed lines 34-36 from:
!!!What commands would be generated?
Below are sample DNSCMDs that would create DNS records for the subnets
10.0.0.0/24 and 10.0.1.0/24 where the Mobility server has an IP of 10.0.0.6.
to:
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.

!!!Example Commands
Changed line 49 from:
!!!What records would I see on my DNS server?
to:
!!!Example Screenshots
Changed lines 51-52 from:
Pictured above is the pc-printer-discovery Conditional Forwarder which points directly towards the IP address of the Mobility Print server. This is what Windows, Android, and Chrome clients will look for.
to:
Pictured above is the Conditional Forwarder called "pc-printer-discovery" which points directly towards the IP address of the Mobility Print server. This is what Windows, Android, and Chrome clients will look for.
Changed line 54 from:
Pictured above are the reverse lookup zones containing the B and LB pointer records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.  The reverse lookup zones used for the Mobility Print DNS records will always have 4 octets.
to:
Pictured above are the reverse lookup zones containing the B and LB pointer records. These records steer [=MacOS=] and iOS clients towards the "pc-printer-discovery" Conditional Forwarder.  The reverse lookup zones used for the Mobility Print DNS records will always have 4 octets.
March 01, 2018, at 12:45 AM by Aaron Pouliot -
Changed line 54 from:
Pictured above are the reverse lookup zones containing the B and LB pointer records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.
to:
Pictured above are the reverse lookup zones containing the B and LB pointer records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.  The reverse lookup zones used for the Mobility Print DNS records will always have 4 octets.
March 01, 2018, at 12:32 AM by Aaron Pouliot -
Changed lines 12-13 from:
Below are sample DNSCMDs that would create DNS records for the domain [=PaperCutSoftware.com=] where the Mobility Print server has an IP address of 10.0.0.6.
to:
Below are sample DNSCMDs that would create DNS records for the domain [=papercutsoftware.com=] where the Mobility Print server has an IP address of 10.0.0.6.
Changed lines 23-24 from:
The pc-printer-discovery Delegated Subzone, which points towards an A record for the Mobility Print server.
to:
Pictured above is the pc-printer-discovery Delegated Subzone. This is what Windows, Android, and Chrome clients will look for.  This  points towards an A record called "pc-mobility-print-host" which resolves to the IP address of the Mobility Print server.
Changed lines 26-27 from:
The B and LB records, which steer [=MacOS=] and iOS clients towards the pc-printer-discovery Delegated Subzone.
to:
Pictured above are the B and LB records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Delegated Subzone.
Added line 36:
Changed lines 51-52 from:
The pc-printer-discovery Conditional Forwarder, which points towards the IP address of the Mobility Print server.
to:
Pictured above is the pc-printer-discovery Conditional Forwarder which points directly towards the IP address of the Mobility Print server. This is what Windows, Android, and Chrome clients will look for.
Changed line 54 from:
The reverse lookup zones containing the B and LB records which steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.
to:
Pictured above are the reverse lookup zones containing the B and LB pointer records. These records steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.
February 28, 2018, at 11:53 PM by Aaron Pouliot -
Changed line 3 from:
The Mobility Print DNS Configuration guide will generate the exact commands that will need to be run for nearly any situation. The only exception [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].
to:
The Mobility Print DNS Configuration guide will generate the exact commands that will need to be run for nearly any situation. The exception to this is if you are intending to set up the DNS records for [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].
February 28, 2018, at 11:49 PM by Aaron Pouliot -
Added lines 54-56:

!!Still have questions?
Let us know! We're definitely happy to chat about how Mobility Print works. Feel free to leave a comment below if you have any questions at all. Also make sure that you check out our [[https://www.papercut.com/products/ng/mobility-print/manual/|Mobility Print Help Center]].
February 28, 2018, at 11:14 PM by Aaron Pouliot -
Changed lines 30-31 from:
*These records are also needed when it is necessary to [[https://www.papercut.com/products/ng/mobility-print/manual/how-to-setup/step-2-configuration/advanced-configuration/restrict-printer-access-per-subnet/|Restrict Printer Access per Subnet]] .
*These records are also useful if you cannot specify the DNS Search Suffix on your DHCP Scope Options
to:
*These records are also needed when it is necessary to [[https://www.papercut.com/products/ng/mobility-print/manual/how-to-setup/step-2-configuration/advanced-configuration/restrict-printer-access-per-subnet/|Restrict Printer Access per Subnet]].
*These records are also useful if you cannot specify the DNS Search Suffix on your DHCP Scope Options.
*These records are only generated when the admin specifies that the client has a  ".local" DNS Search Suffix or when the administrator enters a list of subnets.
February 28, 2018, at 11:07 PM by Aaron Pouliot -
Changed lines 8-9 from:
*Simplest to set up.
*Requires that customer sets DHCP Scope Option 119 "
DNS Search Domain"
to:
*The simplest to set up and troubleshoot.
*Requires that the clients have a
DNS Search Suffix that exactly matches the Forward Lookup Zone where the records are created.
February 28, 2018, at 11:05 PM by Aaron Pouliot -
Changed line 52 from:
The reverse lookup zones containing the B and LB records which steer MacOS and iOS clients towards the pc-printer-discovery Conditional Forwarder.
to:
The reverse lookup zones containing the B and LB records which steer [=MacOS=] and iOS clients towards the pc-printer-discovery Conditional Forwarder.
February 28, 2018, at 11:05 PM by Aaron Pouliot - Added screenshots.
Added lines 21-27:
!!!What records would I see on my DNS server?
https://www.papercut.com/kb/uploads/Main/Delegated%20Subzone.png
The pc-printer-discovery Delegated Subzone, which points towards an A record for the Mobility Print server.

https://www.papercut.com/kb/uploads/Main/B%20and%20LB%20Records.png
The B and LB records, which steer [=MacOS=] and iOS clients towards the pc-printer-discovery Delegated Subzone.

Added lines 47-52:
!!!What records would I see on my DNS server?
https://www.papercut.com/kb/uploads/Main/Conditional%20Forwarder.png
The pc-printer-discovery Conditional Forwarder, which points towards the IP address of the Mobility Print server.

https://www.papercut.com/kb/uploads/Main/PTR%20Records%20in%20Reverse%20Lookup%20Zone.png
The reverse lookup zones containing the B and LB records which steer MacOS and iOS clients towards the pc-printer-discovery Conditional Forwarder.
February 28, 2018, at 09:49 PM by Aaron Pouliot -
Added lines 1-42:
(:title Mobility Print DNS Record Examples:)

The Mobility Print DNS Configuration guide will generate the exact commands that will need to be run for nearly any situation. The only exception [[https://www.papercut.com/kb/Main/MultipleMobilityPrintServerswithWindowsDNS|Multiple Mobility Print Servers]].

It is also useful for troubleshooting to know exactly what DNS records pertain to Mobility Print. Below is a comparison of the two methods of setting up the records in Windows DNS, and when each would be used.

!!Delegated Subzone Method
*Simplest to set up.
*Requires that customer sets DHCP Scope Option 119 "DNS Search Domain"

!!!What commands would be generated?
Below are sample DNSCMDs that would create DNS records for the domain [=PaperCutSoftware.com=] where the Mobility Print server has an IP address of 10.0.0.6.

[@
dnscmd /RecordAdd papercutsoftware.com b._dns-sd._udp PTR pc-printer-discovery.papercutsoftware.com
dnscmd /RecordAdd papercutsoftware.com lb._dns-sd._udp PTR pc-printer-discovery.papercutsoftware.com
dnscmd /RecordAdd papercutsoftware.com pc-mobility-print-host A 10.0.0.6
dnscmd /RecordAdd papercutsoftware.com pc-printer-discovery NS pc-mobility-print-host.papercutsoftware.com
@]

!!Conditional Forwarder with Reverse Lookup Zones
*These records are needed if the forward lookup zone ends in ".local" because of the way Apple products handle this domain name.
*These records are also needed when it is necessary to [[https://www.papercut.com/products/ng/mobility-print/manual/how-to-setup/step-2-configuration/advanced-configuration/restrict-printer-access-per-subnet/|Restrict Printer Access per Subnet]] .
*These records are also useful if you cannot specify the DNS Search Suffix on your DHCP Scope Options

!!!What commands would be generated?
Below are sample DNSCMDs that would create DNS records for the subnets 10.0.0.0/24 and 10.0.1.0/24 where the Mobility server has an IP of 10.0.0.6.
[@
dnscmd /ZoneAdd pc-printer-discovery. /dsforwarder 10.0.0.6

dnscmd /ZoneAdd 0.0.0.10.in-addr.arpa. /dsprimary
dnscmd /RecordAdd 0.0.0.10.in-addr.arpa. b._dns-sd._udp PTR 0.0.0.10.pc-printer-discovery.
dnscmd /RecordAdd 0.0.0.10.in-addr.arpa. lb._dns-sd._udp PTR 0.0.0.10.pc-printer-discovery.

dnscmd /ZoneAdd 0.1.0.10.in-addr.arpa. /dsprimary
dnscmd /RecordAdd 0.1.0.10.in-addr.arpa. b._dns-sd._udp PTR 0.1.0.10.pc-printer-discovery.
dnscmd /RecordAdd 0.1.0.10.in-addr.arpa. lb._dns-sd._udp PTR 0.1.0.10.pc-printer-discovery.
@]


----
[-Keywords: Secret squirrel , Mobility Print, DNS Records, DNS-SD, Delegated Subzone, Conditional Forwarder -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on April 11, 2019, at 09:42 PM
Printable View   |   Article History   |   Edit Article