Add PTR and NS Records to DNS Resolver possible?

posto587

Hi Guys,

we would like to install the papercut mobiity printing on our network with lots of vlan interfaces.
To get the printer discovery work across all subnets we have to add the following records to the DNS system:

;–-------------- Mobility Print records --------------

b._dns-sd._udp IN PTR pc-printer-discovery
lb._dns-sd._udp IN PTR pc-printer-discovery
pc-printer-discovery IN NS print-server-host
print-server-host IN A XXX.XXX.XXX.XXX

;--------------- End of Mobility Print records ---------

Is it possible to add these entrys to the DNS Resolver?
Or do I need to install BIND and configure the records there?

If possible I'd prefer to go with the Resolver since I haven't worked with BIND before.

Thanks,
John

johnpoz

Sure you can add whatever records you want in the custom box..

https://doc.pfsense.org/index.php/Unbound_DNS_Resolver

unboundrecords.png_thumb

posto587

Thank you John for your answer, that helped a lot.
Now the basic delegation is working but the printer discovery is still not.

After lots of mails with the papercut support all DNS tests are passed but not this one:

nslookup -query=ptr _ipps._tcp.pc-printer-discovery.XXX.com.

I think because of the result (Non-existent domain) the discovery is not working.

Do you have an idea where this issue is coming from?
pfsense DNS server is only itself (127.0.0.1)

When I'm using a Windows DNS server the test is OK and printers can be discovered over all subnets.
But it would be great to get this working with the pfSense DNS Resolver.

johnpoz

if your doing to do a PTR then you have to setup the ptr.. you do not have that in your example you posted.

Unbound is not going to be able to respond with info if the info is not there..

posto587

Hmm that's strange.
In the instructions on
https://www.papercut.com/products/ng/mobility-print/manual/dns-service-discovery-setup/#set-up-dns-discovery-for-a-zone-ending-in-local
they are saying, adding these four records as described in the first post are enough.

Which more records would I need to add?
Sorry for bothering you again. :-[

johnpoz

if your saying this is failing

"nslookup -query=ptr _ipps._tcp.pc-printer-discovery.XXX.com."

I would agree since its not in the instructions so how would it magically be resolvable?

posto587

Ok I'm sorry, I did forget to mention an important thing:

The print-server-host (Papercut Mobility Print Server) where I'm pointing the DNS records to, is a DNS server itself.

So what papercut says is basically:
Configure the four DNS records on your local DNS Server to point to the Mobility Print Server.
The Mobility Print Server will then make the printers discoverable over all subnets, via Airprint etc…

johnpoz

"pc-printer-discovery IN NS print-server-host"

That is the NS you point to for that domain..

But your PTR query is for this domain
"pc-printer-discovery**.XXX.com.**"

That is not the same, so that NS record does not point you to the printserverhost..

Dude its very difficult to work with out the actual FQDN.. If you want more help from me your going to need to actual post what your putting in, not the template..

posto587

The DNS suffix from pfSense is: lew.wohnheim

The FQDN from pfSense is: gate.lew.wohnheim

The papercut support says, I need to add these DNS delegations:

An A record pointing to your server running Mobility Print my-print-server IN A 10.1.1.4
A delegated subzone for pc-printer-discovery that points to the A record pc-printer-discovery IN NS my-print-server
Two Pointer (PTR) records in root DNS that connect the server to the subzone b._dns-sd._udp IN PTR pc-printer-discovery
lb._dns-sd._udp IN PTR pc-printer-discovery

So when adding the entries:

b._dns-sd._udp IN PTR pc-printer-discovery
lb._dns-sd._udp IN PTR pc-printer-discovery
pc-printer-discovery IN NS mobility
mobility IN A 10.100.15.34

the following lookup isn't working:

nslookup -query=ptr _ipps._tcp.pc-printer-discovery.lew.wohnheim.

Even when I'm adding these entries:

b._dns-sd._udp.lew.wohnheim IN PTR pc-printer-discovery
lb._dns-sd._udp.lew.wohnheim IN PTR pc-printer-discovery
pc-printer-discovery.lew.wohnheim IN NS mobility
mobility.lew.wohnheim IN A 10.100.15.34

the lookup isn't working.

Is this the right syntax for unbound? How do I add a delegated subzone?

johnpoz

that is the correct syntax I showed doing a query for those entries..

"pc-printer-discovery.lew.wohnheim IN NS mobility"

This is not VALID… mobility is not a valid FQDN.. What is suppose to be the NS? 10.100.15.34? For what domain?

"pc-printer-discovery IN NS print-server-host"

Then it would be

pc-printer-discovery IN NS mobility.lew.wohnheim
mobility.lew.wohnheim IN A 10.100.15.34

kolpinkb

So, I was interested in the product too. I have it half working, meaning that two of the DNS requirements are met and only the PTR records remain to be configured. However, apparently those are only needed for iOS and MacOS and not Android. Yet, when I tried to discover the printer on Android nothing shows up. The following entries I added to Unbound Resolver's custom options field:

server:
local-zone: "example.com." transparent
local-data: "mobility-print-host.example.com. A 192.168.71.3"
local-data: "pc-printer-discovery.example.com. NS mobility-print-host."

I'm not sure how important the periods are at the end of each subdomain. Whether its "mobility-print-host." or "mobility-print-host" seems to work just fine in Mobility Print's eyes.

Working on the PTR records now and will update if I get anywhere.

![papercut ng mobility print dns.png](/public/imported_attachments/1/papercut ng mobility print dns.png)
![papercut ng mobility print dns.png_thumb](/public/imported_attachments/1/papercut ng mobility print dns.png_thumb)

trentuk

Hi all,

I'm trying to get Mobility Print working with DNS Resolver too but without success, here are my custom options, all seem to be correct & present when doing a lookup from a client but I still can't see any printers in the Mobility Print app on Android or from any Apple iOS/OSX devices.

–-------------------------------------------------------------------------------------
server:
local-data: "b._dns-sd._udp IN PTR pc-printer-discovery"
local-data: "lb._dns-sd._udp IN PTR pc-printer-discovery"
local-data: "_ipps._tcp IN PTR pc-printer-discovery"
local-data: "pc-printer-discovery IN NS lipa-printers.mydomain.removed"
local-data: "lipa-printers.mydomain.removed IN A 10.2.1.5"

Just to be clear, I've removed my actual domain and replaced with 'mydomain.removed'

Any thoughts, suggestions, offers of moral support gratefully received! ;)

johnpoz

"'mydomain.removed' "

What is the domain.. Did you set this zone as transparent? Can not help you people your going to obfuscate and ask why it doesn't work.. My guess is the domain actually resolve on public and its looking for something you didn't put in so it gets back NX..

If all the stuff you put responds when you query unbound.. How is unbound not doing what you told it to do?

b._dns-sd._udp IN PTR pc-printer-discovery
lb._dns-sd._udp IN PTR pc-printer-discovery
pc-printer-discovery IN NS print-server-host
print-server-host IN A XXX.XXX.XXX.XXX

I don't see any . periods on the end of your entries..

What I would suggest is connect them for the setting up in unbound. Keep in mind unbound is not really meant to be an authoritative dns..

This is suppose to be a delegated domain.. So what domain are you using local? yourdomain.com? what??

Says right on their site
"The name of the search domain(s) for your devices (eg. Android phone, Chromebook)"

So what FQDN are you using for pc-printer-discovery ??? Its suppose to be pc-printer-discovery.yourdomain.tld and your client is suppose to be using a search suffix to find that record!!!

delegatedzone.png_thumb

fqdn.png_thumb

doktornotor


local-data: "b._dns-sd._udp IN PTR pc-printer-discovery"
local-data: "lb._dns-sd._udp IN PTR pc-printer-discovery"
local-data: "_ipps._tcp IN PTR pc-printer-discovery"

Dafuq?!

johnpoz

Exactly!!!

doktornotor

@OP: Here's some valid example of PTR:


local-data-ptr: "192.0.2.1 foo.example.com"
local-data-ptr: "2001:db8:a:b:c::1 foo.example.com"

johnpoz

Nope they want PTR setup for b._dns-sd._udp

I have downloaded the damn product they have a 40 day trial… I have to go out for my morning walk.. And then work.. But will try and get it setup today so I can screen shot exactly how to get it working with the domain your using as your search domain.. And that their papercut ng interface shows it all green, etc. And you can print from some mobile client..

doktornotor

AFAICT this shit wants/needs mDNS/Zeroconf and messing with Unbound will do zero useful work there. Perhaps look at Avahi instead.

Junk.

kolpinkb

You can do either DNS records or mDNS. I tried the mDNS discovery option in PaperCut NG Mobility print and my printer does show up in their Android app but I can an internal server error. Also, I found the avahi daemon to crash intermittently with default settings.

Would much prefer to get the DNS PTR records working.

trentuk

Thanks for offering to have a look at this johnpoz, very much appreciated!

This site is using split DNS, by this I mean they're using the same domain internally as externally, thus you're probably correct that something is missing from the DNS config in pfSense and the Mobility Print client is then looking at the public DNS to find it and then receives NX.

I've asked the IT Director if I can post the domain name here but they would prefer not to, therefore could we use 'yourdomain.ltd' whilst discussing the configuration?

pfSense version: 2.3.4-RELEASE-p1

System - General Setup - Domain: yourdomain.ltd

DNS Resolver - System Domain Local Zone Type: Transparent

Client DNS Suffix is: yourdomain.ltd

Given the above information, would you suggest something along the following lines in DNS Resolver - Custom Options:

b._dns-sd._udp.yourdomain.ltd. IN PTR pc-printer-discovery.yourdomain.ltd.
lb._dns-sd._udp.yourdomain.ltd. IN PTR pc-printer-discovery.yourdomain.ltd.
pc-printer-discovery.yourdomain.ltd. IN NS print-server-host.yourdomain.ltd.
print-server-host.yourdomain.ltd. IN A XXX.XXX.XXX.XXX

Many thanks in advance …