Add PTR and NS Records to DNS Resolver possible?
-
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?!
-
Exactly!!!
-
@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" -
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..
-
AFAICT this shit wants/needs mDNS/Zeroconf and messing with Unbound will do zero useful work there. Perhaps look at Avahi instead.
Junk.
-
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.
-
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.XXXMany thanks in advance …
-
I think OP really wants to configure SRV records for that, not PTR records.
I would say the confusion knob is turned up to 11.
-
I have downloaded the software, and yeah something is not right that is for sure with their instructions.
Sorry to say I will most likely not get back this for a few days.. I got new internet at home 500/50 and it consuming my interest ;)
What I noticed was didn't even see the client doing a dns query for the PTR.. I think the current mdns that was on the segment was confusing it, etc. I will have to turn off the mdns on the printer, etc. And need to run the mobility client on different machine than the papercut ng, etc.
-
Hello Derelict,
I think OP really wants to configure SRV records for that, not PTR records.
I would say the confusion knob is turned up to 11.
The software vendor specify a requirement for the following records:
;–-------------- 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 ---------
Which is possibly the cause of the confusion knob being turned past its recommended level ;)
-
Hello johnpoz,
No problem, glad I'm not the only one struggling with this ???
Enjoy the new connection, hopefully see you back here once you've downloaded the entire internet at blisteringly fast speeds ;)
-
Thanks again johnpoz,
This configuration has many of us perplexed.
Have fun with the new 500/50 connection. I'm sure the increased upload is the best part.
-
The software vendor specify a requirement for the following records:
;–-------------- 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 ---------
The software vendor's confusion knob is turned up to at least 12. That makes no sense at all. PTR records do not have names on both sides. They are used to lookup a name when all you have is an address, like 198.51.100.101.
-
They look like SRV records…. at least the left-hand side.... maybe you can "sniff" the correct format from a working setup using some form of dns-sd -Z
-
I think the software is looking to be a delegation server for a specific subdomain.
Base domain: example.com
Delegation server: mobility-print-host.example.com
subdomains to delegate: xxxxprinter.b._dns-sd._udp.pc-printer-discovery.???
-
Unless the LHS of those PTR records is supposed to be replaced with at least part of an IP address, to be completed with .in-addr.arpa., they are nonsense.
Or we're going to need a lot more information about what it is they are trying to do.
-
The configuration example on their website (that we've all shared here) is specifically for BIND. Not sure if it translates 1:1 for Unbound.
-
DNS is DNS is DNS. I have not looked at the document there.
-
I get that. But something with the way PTR records are handled internally in the software (BIND vs Unbound) must be different.
-
No it doesn't translate 1:1 for Unbound, plus, instead of copy-paste of nonsensical instructions they are providing, it'd be way more useful to explain what they are trying to implement. Is that shitty product trying to delegate some subdomain to their own nameserver/printserver, or what?
