Setting up Mobility DNS records for Infoblox DDI
on 10 August 2020 12:45 PM
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:
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.
1. Sign in to the Infoblox interface then navigate to Data Management > DNS > then Zones.
2. From there, click the + icon to add a Forward Zone.
3. Specify “Add a forward-mapping zone” and click Next.
4. Name the new Forward Zone “
5. Enter the Mobility server’s FQDN (
6. Choose which Grid Members have the responsibility to respond for the new Forward Zone and click next.
7. Save and close. Then, restart Infoblox when prompted for the new settings to apply.
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
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.
1. First, flush the DNS cache to make sure we’re using only the freshest DNS records:
2. Let’s do a query to find a printer list using the _ipps._tcp service type. You should recognize the printers in the name record data.
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
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
1. Navigate to Grid Manager > DNS > Services and check the box next to the Grid Master. Click the edit button and select Updates. From there, add the IP address of the system sending the
2. From the source system, enter the following commands to add the lb PTR record in the existing wireless subnet reverse mapping zone. This example assumes DHCP hands the Apple devices our default search domain,
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
> 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
3. Verify that the records show up in the zones
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
The results should look like so:
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
4. Ensure the records replicate across all DNS servers.
And that’s it. Now, Apple devices in the
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.