Add PTR and NS Records to DNS Resolver possible?

mobility_dev · Oct 10, 2017, 1:40 PM

Thanks johnpoz for your input.
Mobility Print supports many client device types: Android, Chromebook, Windows, iOS and macOS.
If the customer need to:

Support Android and Chromebook, then you are right. They only need to put the rpc.pc-printer-discovery.domain.tld using host override feature of Unbound as you said and it should work.
Additionally support Windows, then they need to add another host override ipp.pc-printer-discovery.domain.tld to Unbound
To support iOS and macOS, our server need to implement the DNS-SD RFC (http://www.dns-sd.org/) because iOS and macOS using DNS-SD to discovery printers. So the two records b._dns-sd._udp.domain.tld PTR pc-printer-discovery.domain.tld and lb._dns-sd._udp.domain.tld PTR pc-printer-discovery.domain.tld are required.
Here is a the DNS conversation of the iOS device with the DNS server (in this case Unbound) when it join a subnet with the search domain domain.tld and try to find the printers:
iOS devices: hey, in this search domain domain.tld, where should I browse for available services so that I can use?
(then it sends the query b._dns-sd._udp.domain.tld PTR to Unbound)
Unbound: I don't know, but you can ask pc-printer-discovery.domain.tld
(in this case we want Unbound to return the pc-printer-discovery.domain.tld as the data in the answer)
Next, because the iOS device want to find printing services, which is defined as _ipps._tcp in DNS-SD RFC
The iOS device will ask: Can you give me a list of printers so that I can print to?
(then it sends the query _ipps._tcp.pc-printer-discovery.domain.tld PTR TO Unbound and we expect Unbound forward this query to Mobility Print server. Mobility Print server will generate the answers returning to Unbound then Unbound returns the answers to the iOS device)

This is how it works in the case of BIND and Windows DNS server.

So it's just the matter to replicate this conversation by configuring Unbound.
Input from Unbound expert is appricated!

For more information about DNS-SD: http://www.dns-sd.org/

johnpoz · Oct 10, 2017, 12:45 PM

That is great info thank you - how come that info is not listed on your site when looking to implement dns for your product? Or is it and just didn't find that document? If so could you provide link?

kolpinkb · Oct 10, 2017, 2:51 PM

Just tried the host override in the web GUI. Unbound doesn't seem to like the "dot" after the "rpc". It returns an error in the staying "A valid hostname is specified, but the domain part should be omitted.

johnpoz · Oct 10, 2017, 6:58 PM

you wouldn't put in a dot after

The host would be rpc

The domain would be pc-printer-discovery.domain.tld

In your host override section.

kolpinkb · Oct 10, 2017, 7:15 PM

Thanks for the clarification johnpoz. Rookie mistake on my part. I have all the records required for Android and two green check marks but I still can't seem to get the mobility app to find my printers.

johnpoz · Oct 10, 2017, 7:25 PM

I have gotten a bit side tracked.. I will try and find some time here tmrw morning to bring up the mobility on box on one of my wifi segments with printer and papercut ng on different segment to get this working.. And will turn off the functionality on the printer directly, etc.

Per this
"Support Android and Chromebook, then you are right. They only need to put the rpc.pc-printer-discovery.domain.tld using host override feature of Unbound as you said and it should work."

All you should need is the override pointing to the IP of your box running the mobility.. As long as the mobility has your printer(s) setup, etc.

kolpinkb · Oct 11, 2017, 1:20 AM

I did exactly that.

However, I'm not sure if the following makes a difference.

-papercut and mobility print are on the same machine
-printrr is on same subnet as above
-android phone is on a different subnet

mobility_dev · Oct 11, 2017, 2:23 AM

Hi thehammer86,
Can you access the URL http://rpc.pc-printer-discovery:9163/printers from a browser on your Android device?
It should return to you some JSON if you have some printers on your Mobility Print server.

kolpinkb · Oct 11, 2017, 2:25 AM

It returns JSON if I add .example.com.

I must be missing something in my unbound config?

mobility_dev · Oct 11, 2017, 2:32 AM

What is the search domain (DNS suffix) on your Android device?

kolpinkb · Oct 11, 2017, 2:38 AM

I don't seem to have that option available in my wifi. Running Android 6.0.1.

I have my search domain set in my DHCP server on pfSense.

I've also manually added it to my windows PCs. For the windows PCs I know the search domain is working because I don't have to add the example.xom part when I do an NS lookup.

Selo · Jan 16, 2018, 2:07 PM

Hello everybody,

I was wondering: was this issue solved in the end?
We are facing the same problem configuring Resolver with the Mobility records.
Checking the records using the Mobility application, we keep getting errors on the PTR records (the other 2 are working fine).
Screenshot of working DNS entries would be really great!

kolpinkb · Jan 16, 2018, 3:11 PM

Not yet with the Unbound resolver. I ended up setting up a separate sever just for bind9. I have everything working with that setup.

Selo · Jan 16, 2018, 3:10 PM

Is it possible to post the actual records you used (as an example/syntax)?
Screenshot of dns settings?
thanks!

johnpoz · Jan 16, 2018, 3:31 PM

And what did you setup exactly – that has been the whole question... See you can for sure setup PTR records on unbound...

The person from Mobility print was suppose to be answering those questions.. Which I do not recall ever got answered.

Selo · Jan 16, 2018, 5:22 PM

I can tell this:

we are working on this issue with 2 experienced engineers. We have setup the 4 records as requested by the mobility print software.
nslookup confirms the 4 records are active and correct. After checking the records with the mobility software, we keep getting an error on the PTR records.
Fortunately we have an active Papercut license (it is a new install with 150 users), we created a support ticket…hope to get quick response.
If anyone has fixed this PTR issue, I would really like to see the DNS entries...
We also suggested a change to the mobility print client: a possibility to enter an ip-address instead of using the autodiscover option...

kolpinkb · Jan 16, 2018, 5:28 PM

Posting my named.conf file shortly for bind. Just obfuscating the IPs and domains.

Also, tech support was kind enough a few weeks ago to spend 2-3 hours on the phone with me to try an figure out the problem with unbound. I found something in Mobility Print's log files that may be of use.

Hold tight.

johnpoz · Jan 16, 2018, 5:33 PM

From what I recall the client was not looking for what they said to create on their website.. But I can till you for fact is that unbound can create PTR records…

Here is simple PTR query for IP on unbound... Answers just fine...


> dig -x 192.168.9.8

; <<>> DiG 9.11.2 <<>> -x 192.168.9.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37198
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;8.9.168.192.in-addr.arpa.      IN      PTR

;; ANSWER SECTION:
8.9.168.192.in-addr.arpa. 1635  IN      PTR     Storage.local.lan.

;; Query time: 9 msec
;; SERVER: 192.168.3.10#53(192.168.3.10)
;; WHEN: Tue Jan 16 11:31:45 Central Standard Time 2018
;; MSG SIZE  rcvd: 84

What exactly is going to be queried and what should be the answer and we can validate whatever that something is can be entered into unbound. But 100% for sure unbound can answer for a PTR query.

Selo · Jan 17, 2018, 1:25 PM

OK, let´s wait for the named.conf file thehammer86 was going to post…
Also curious about this: "I found something in Mobility Print's log files that may be of use."

johnpoz · Jan 17, 2018, 1:29 PM

I played with this for a bit - I could never get the client to actually do a ptr query like they said it should.. Their docs from what I remember are not very clear. My trial ran out and attempted to run the mobility client on the same box the server was run on.

I could try to setup it up again on some other machines - But once we know what actual query be it PTR or some other we can work out how to setup (if possible) for unbound to respond. What I can tell you for 100% fact is the unbound can respond with a PTR… And NS records, so there is something missing in the puzzle here.