Hey, there, and thanks for reaching out! Infoblox DNS and BIND DNS share many elements under-the-hood, but Mobility record configuration is not one of them. Please continue reading to learn about setting up Mobility records for PaperCut State’s Infoblox DDI.
Everyone’s Infoblox DDI config looks different from the next. The names and addresses we use in this article won’t match yours, but that’s okay. Hopefully, you can make sense of our KB by understanding the assumptions we made:
|Our pretend element||The element’s value|
|Default search domain:||students.papercutstate.edu|
|Other search domains:||history.papercutstate.edu, engineering.papercutstate.edu, oit.papercutstate.edu|
|Mobility server’s FQDN:||pc-mobility-print.oit.papercutstate.edu|
|Apple device subnets:||10.1.0.0, 10.2.0.0|
Because these steps require putting a forwarding zone in your forward-mapping zones, these DNS zones must be part of your device’s DNS domain search list. In other words, we assume your Infoblox DHCP will set connected devices into their correct subdomains using options 15 or 119.
By default, this forwarding zone is all that Windows, Android, and Chrome devices need to discover the Mobility printer advertisements. Apple devices will need this zone along with a PTR record in the appropriate reverse mapping zone, but we’ll get to that part in a bit.
pc-printer-discovery.students.papercutstate.edu”. Infoblox automatically adds the trailing dot.
pc-mobility-print.oit.papercutstate.edu) and IP:
But what if my DHCP clients don’t all get the same DNS search list?
Well, fret not, dear Infoblox admin. The trick to supporting network clients that don’t get the
students.papercutstate.edu search domain is to add a
pc-printer-discovery forwarding zone for the related domains. In other words, please follow the steps in the “Creating the pc-printer-discovery Forwarding Zone” for each DNS zone that DHCP options 15 or 119 deliver as the domain name that clients should use when resolving hostnames via DNS. As an example, you might end up with NS RR data that looks like so:
pc-printer-discovery.students.papercutstate.edu NS pc-mobility-print.oit.papercutstate.edu pc-printer-discovery.history.papercutstate.edu NS pc-mobility-print.oit.papercutstate.edu pc-printer-discovery.engineering.papercutstate.edu NS pc-mobility-print.oit.papercutstate.edu pc-printer-discovery.oit.papercutstate.edu NS pc-mobility-print.oit.papercutstate.edu
Okay, let’s confirm we didn’t just waste several minutes
It wouldn’t help to have this shiny, new forwarding zone on your Infoblox DDI if it didn’t resolve to anything, so let’s make sure it works. Try running the following commands from a Terminal or command prompt window.
- In Windows:
- In fancyOS:
sudo killall -HUP mDNSResponder
- In Linux: Well, consult your distribution’s documentation since some implementations don’t even cache DNS by default.
nslookup -query=ptr _ipps._tcp.pc-printer-discovery.students.papercutstate.edu.
At this point, printer discovery should work from Windows, Android, and Chrome clients that get the
students.papercutstate.edu search domain, but not iOS and macOS. Try running the respective clients to confirm. And now, a question: do you - now, or will you at any point in the future - have a requirement to share printer advertisements with iOS devices like iPads or iPhones, or macOS devices like MacBooks, iMacs, Mac Minis, and Mac Pros? If you answered yes, congratulations! Please fast-forward to “Infoblox Mobility printer discovery for Apple devices.” However, if you answered, “No, I have no plans to support Mobility printer discovery for Apple devices now or at any point in the future,” then I congratulate you too because I just saved you several minutes, at least. You’re all done. Get a hot or cold beverage of your choice, because you deserve it.
macOS and iOS devices require an Apple-specific lb PTR record to find Mobility printer advertisements in the reverse-mapping zones correspondent to their current subnets. This section assumes that reverse-mapping zones for the
10.2.0.0 subnets already exist. Create these PTR records using the
nsupdate command-line utility. The tool is native to macOS and Linux. To install
nsupdate on Windows, see here: http://wiki.inisec.com/index.php/Nsupdate_for_windows.
nsupdatecommands, AKA source system.
FANCYOS:~ coolkid$ nsupdate -d > server 10.10.10.1 > add lb._dns-sd._udp.0.0.1.10.in-addr.arpa 14400 IN PTR 0.0.1.10.pc-printer-discovery.students.papercutstate.edu > send > server 10.10.10.1 > add lb._dns-sd._udp.0.0.2.10.in-addr.arpa 14400 IN PTR 0.0.2.10.pc-printer-discovery.students.papercutstate.edu > send
Note: To accommodate Apple devices with a different domain search list, supplement your
nsupdate command with the correct forwarding zone. For example:
> add lb._dns-sd._udp.0.0.1.10.in-addr.arpa 14400 IN PTR 0.0.1.10.pc-printer-discovery.history.papercutstate.edu
0.0.2.10.in-addr.arpa. Flush your DNS cache, and try the following
FANCYOS:~ coolkid$ nslookup -type=ptr lb._dns-sd._udp.0.0.1.10.in-addr.arpa && nslookup -type=ptr lb._dns-sd._udp.0.0.2.10.in-addr.arpa
Server: 10.10.10.1 Address: 10.10.10.1#53 lb._dns-sd._udp.0.0.1.10.in-addr.arpa name = 0.0.1.10.pc-printer-discovery.students.papercutstate.edu Server: 10.10.10.1 Address: 10.10.10.1#53 lb._dns-sd._udp.0.0.2.10.in-addr.arpa name = 0.0.2.10.pc-printer-discovery.students.papercutstate.edu
And that’s it. Now, Apple devices in the
10.2.0.0 subnets can use the lb PTR record, in conjunction with the
pc-printer-discovery forwarding zones, to discover Mobility printer advertisements.
- We set up
pc-printer-discoveryforwarding zones for each DNS zone corresponding to a domain name the client should use when resolving hostnames via DNS.
- Remember: This forwarding zone is all that Windows, Android, and Chrome devices need to discover the Mobility printer advertisements.
- We set up lb PTR records for the subnets hosting Apple devices.
- Remember: macOS and iOS require an Apple-specific lb PTR record in the reverse-mapping zones correspondent to their current subnets.
- We used a couple of NSLOOKUPS to check our work.
This article was a team effort, and being able to publish it sooner rather than later is due in large part to Rod Eldridge, Network Engineering Team, Iowa State University. His charitable behavior extends beyond helping the humble author of this article as he is also willing to offer limited help to other universities with their PaperCut Mobility Print implementation, with regards to DNS and DHCP, and as time permits. Reach him at firstname.lastname@example.org.
Let us know! We love chatting about DNS, Mobility, and what’s going on under the hood. Talk nerdy to us. Feel free to leave a comment below or visit our Support Portal for more help.
Keywords: Secret squirrel , Mobility Print, DNS Records, DNS-SD, Linux, BIND, NAMED, Cool Kids, Delegated Subzone, Conditional Forwarder, Infoblox