Setting up Mobility Print DNS with MacOS Server DNS

KB Home   |   Setting up Mobility Print DNS with MacOS Server DNS

Main.SettingupMobilityPrintwithmacOSServerDNS History

Hide minor edits - Show changes to output

October 25, 2018, at 11:52 PM by Mel Zouzoulas - Moved the note about MacOS support up to the top
Added lines 3-6:
!!!macOS Server support:
It’s worth noting that Apple has announced that DNS is amongst the services being deprecated from macOS Server, in Spring 2018. Take a look at this article from Apple for more information:
https://support.apple.com/en-us/HT208312

Deleted lines 57-61:

!!!Additional notes about macOS Server support:

It’s also worth noting that Apple has announced that DNS is amongst the services being deprecated from macOS Server, in Spring 2018. Take a look at this article from Apple for more information:
https://support.apple.com/en-us/HT208312
June 04, 2018, at 03:30 PM by Mel Zouzoulas - Added link to the Mobility Print help center = good SEO
Added lines 59-60:

For more information about Mobility Print, check out the [[https://www.papercut.com/products/ng/mobility-print/manual/| Mobility Print Help Center]].
April 30, 2018, at 08:50 PM by Aaron Pouliot -
Changed lines 6-8 from:
However, you cannot use one server as the Mobility Print server and DNS server.  These roles must be separated.  The reason for this is that the Mobility Print application and DNS will both try to listen and respond to DNS queries, with mixed results.  This means that you will need a separate server for DNS and for Mobility Print.

Also note that you’ll
need to perform the following tasks as root, or at least sudo to be able to complete these tasks.
to:
However, there are several things that you should know before beginning:
* These changes cannot be made in the GUI, and instead require editing BIND DNS configuration files to set up.
* You cannot use one server as the Mobility Print server and DNS server, these roles must be separated.  The reason for this is that the Mobility Print application and DNS will both try to listen and respond to DNS queries, with mixed results.  This means that you will need a separate server for DNS and for Mobility Print.
* You’ll
need to perform the following tasks as root, or at least sudo to be able to complete these tasks.
April 30, 2018, at 08:47 PM by Aaron Pouliot -
Changed line 3 from:
!!Is it possible to set up the Mobility Print DNS records on a MacOS server?
to:
!!Can you set up the Mobility Print DNS records on a [=MacOS=] server?
April 30, 2018, at 08:47 PM by Aaron Pouliot -
Changed lines 3-4 from:
!!Is it possible to set up the Mobility Print DNS records on a [=MacOS=] server?
Actually yes!  Under the hood, a MacOS Server uses BIND for its DNS service. To illustrate this point, on your macOS server, take a look in /Library/Server/named/ - and you’ll see several files relating to the zones that you’ve set up in the DNS service, through the server app.
to:
!!Is it possible to set up the Mobility Print DNS records on a MacOS server?
Actually yes!  Under the hood, a [=MacOS=] Server uses BIND for its DNS service. To illustrate this point, on your macOS server, take a look in /Library/Server/named/ - and you’ll see several files relating to the zones that you’ve set up in the DNS service, through the server app.
April 30, 2018, at 08:46 PM by Aaron Pouliot - Added intro
Changed lines 1-5 from:
(:Title Setting up Mobility Print DNS with macOS Server DNS :)

Under the covers, macOS Server is using BIND for its DNS service. On your macOS server, take a look in /Library/Server/named/ - you’ll see several files relating to the zones that you’ve set up in the DNS service, through the server app.

Note
that you’ll need to perform the following tasks as root, or at least sudo to be able to complete these tasks.
to:
(:Title Setting up Mobility Print DNS with MacOS Server DNS :)

!!Is it possible to set up the Mobility Print DNS records on a [=MacOS=] server?
Actually yes!  Under the hood, a MacOS Server uses BIND for its DNS service. To illustrate this point, on your macOS
server, take a look in /Library/Server/named/ - and you’ll see several files relating to the zones that you’ve set up in the DNS service, through the server app.

However, you cannot use one server as the Mobility Print server and DNS server.  These roles must be separated.  The reason for this is that the Mobility Print application and DNS will both try to listen and respond to DNS queries, with mixed results.  This means that you will need a separate server for DNS and for Mobility Print.

Also note
that you’ll need to perform the following tasks as root, or at least sudo to be able to complete these tasks.
April 30, 2018, at 05:58 PM by Aaron Pouliot - Added Category MobilityPrint
Changed lines 56-57 from:
to:
----
''Categories:'' [[Category.MobilityPrint|+]]
Changed line 1 from:
(:Title Setting up Mobility Print DNS with macOS Server DNS Title:)
to:
(:Title Setting up Mobility Print DNS with macOS Server DNS :)
Added lines 48-49:

Note that the testing above was done with a Mac running macOS High Sierra 10.13.3, and with Server App version 5.5.
March 03, 2018, at 12:10 AM by timg - Added screenshots
Added lines 16-19:
For example, below you can see the zone file for timtest.com:

Attach:macOSServer_zone_file.png

Added lines 33-36:
For example below you can see the pc-printer-discovery entry, and 10.1.9.83 is the address of the Mobility Server:

Attach:macOSServer_named.png

Added lines 41-44:
For example below the DNS server address is 10.1.8.78:

Attach:macOSServer_DNS.png

Changed lines 47-48 from:
From a test workstation, you should then be able to check the discovery of printers, through the pc-printer-discovery URLs… as per https://www.papercut.com/kb/Main/MobilityPrintersNotFound under the ‘Check the configuration from a particular subnet or device type’ section.
to:
From a test workstation, you should then be able to check the discovery of printers, through the pc-printer-discovery URLs on the [[https://www.papercut.com/kb/Main/MobilityPrintersNotFound|Troubleshooting Mobility Print page]] under the ‘Check the configuration from a particular subnet or device type’ section.
Changed lines 51-52 from:
It’s also worth noting that Apple has announced that DNS is amongst the services being deprecated from macOS Server, in Spring 2018. Take a look at this article from Apple for more information: https://support.apple.com/en-us/HT208312
to:
It’s also worth noting that Apple has announced that DNS is amongst the services being deprecated from macOS Server, in Spring 2018. Take a look at this article from Apple for more information:
https://support.apple.com/en-us/HT208312
March 02, 2018, at 11:54 PM by timg - macOS Server DNS Setup article
Added lines 1-43:
(:Title Setting up Mobility Print DNS with macOS Server DNS Title:)

Under the covers, macOS Server is using BIND for its DNS service. On your macOS server, take a look in /Library/Server/named/ - you’ll see several files relating to the zones that you’ve set up in the DNS service, through the server app.

Note that you’ll need to perform the following tasks as root, or at least sudo to be able to complete these tasks.

!!!Setting up the Zone file:

In the zone file for the domain you’re interested in (for example, I’m using timtest.com as my test domain - so I would then edit the file /Library/Server/named/db.timtest.com), paste in the following PTR records at the end of the file:

[@b._dns-sd._udp      IN PTR pc-printer-discovery.@] \\
[@lb._dns-sd._udp      IN PTR pc-printer-discovery.@]

Note the extra ‘.’ after the pc-printer-discovery entry. Also note that the other pc-printer-discovery and print-server-host records are not needed here.

!!!Setting up the named.conf file:

Next, in the same directory, edit your named.conf file to contain an extra zone entry at the end of the file (before the final closing “}” ):

        [@zone "pc-printer-discovery" {@]
                [@type forward;@]
                [@forwarders {@]
                      [@ x.x.x.x;@]
                [@};@]
        [@};@]

Where x.x.x.x is the IP address of your Mobility Server (note that you cannot run Mobility Print on the same server as your DNS service).

!!!Make the changes live:

Make sure the changes are saved to both files and then restart your DNS service (e.g. toggle the Service ‘ON’ button in newer versions of the macOS Server app).

!!!Testing:

From a test workstation, you should then be able to check the discovery of printers, through the pc-printer-discovery URLs… as per https://www.papercut.com/kb/Main/MobilityPrintersNotFound under the ‘Check the configuration from a particular subnet or device type’ section.

!!!Additional notes about macOS Server support:

It’s also worth noting that Apple has announced that DNS is amongst the services being deprecated from macOS Server, in Spring 2018. Take a look at this article from Apple for more information: https://support.apple.com/en-us/HT208312


----
[-Keywords: mobility print, macOS, server, BIND, dns-]

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 October 25, 2018, at 11:52 PM
Printable View   |   Article History   |   Edit Article