Papercut mobility server - DNS errors

[Sheridan]

I've added the Papercut Mobility server to allow our mobile devices to discover the print queues, which seems to be working fine.

 

However the DCs now all show a DNS error in dcdiag - relating to the Papercut DNS entries I created (using their auto generated script)

 

TEST: Delegations (Del) Error: DNS server: mobility-print-host.domain. IP:xx.xx.xx.x [broken delegated domain pc-printer-discovery.domain.]

 

Our DNS is working fine - if I deleted all the Papercut entries it gets rid of the error.

 

Have I missed something, or is this normal behaviour when using the DNS discovery method for papercut?

[MatthewL]

In the bit where it generates the script, did you select your domain and then how did you present your subnet, if I was at home mine would of been 192.168.20.1/255.255.255.0 but if I was at work I would have multiple /24's added.

 

You will find it is to do with how your IP info has been added in, I copy the script and then run command prompt on the DNS server as admin then paste it and check each line is successful in process and then you will see if there are any errors there.

[Sheridan]

I used their generated script and it seemed to work after I entered our domain name, server IP and subnets that the printers are on

 

It created:

 

An A record for mobility-print-host pointing to our Papercut server IP

An NS record for pc-printer-discovery with the name server entry of mobility-print-host.domain.org

 

Then in each of our subnets it created two PTR records in the reverse lookup zones:

i.e something like:

 

192.168.1.0._udp._dns-sd.b with an entry of 0.1.168.192.pc-printer-discovery.

192.168.1.0._udp._dns-sd.b with an entry of 0.1.168.192.pc-printer-discovery.

 

The only thing I can see that doesn't look 'right' to me is in the entries above, the FQDN is showing as ???.in-addr.arpa

 

The printing works OK - its just the DC's that generate the error

[MatthewL]

It's not the subnet your printers are on its the subnet that you client's are on that are going to be using it.

 

What are you clients you are using, Apple, Android, Windows, Chrome?

[Sheridan]

Yes - those subnets relate to the where the clients and printers are both located

 

We're using this for iOS devices (ipads) and they work - the Papercut printer appears and prints with authentication so its not like it doesn't work, just seems to be something off with the DNS config

[MatthewL]

If you disable the Mobility service do the printers not work on your iPad's?

 

If I remember this rightly from when I did my training for Apple devices it broadcasts using the mDNS protocol and Bonjour but the Android and Chromebooks need to do a lookup hence the DNS entries for it to work.

 

In the many installs I've done I've always had a mix of clients but running the script generated never had an issue other than DNS not updating quick enough to pass the tests when you complete.

[Sheridan]

When the mobility service is off or removed the ipads don't see the printer(s). I use the DNS method as mDNS only works across a single subnet - this is similar to the issues we have try to use airserver across subnets.

 

Like I say the printing side is working well - but it bugs me to see dcdiag errors even when I know they don't affect the network performance!

[MatthewL]

Can you post a copy of your script that PaperCut generates and a copy of your error logs on the DNS side?

[Sheridan]

This is the generated script - we have a core subnet (where the papercut server is) 8 other subnets where the clients are. It seems to work OK

papercutdns.txt

 

Running dcdiag on any DC shows this at the DNS stage

 

dnserror.txt

Edited May 22, 2020 by Sheridan

[MatthewL]

When your adding your IP addresses in what format are you putting them in?

 

For mine for example one would be 172.26.14.0/255.255.254.0 then another maybe 172.16.14.0/255.255.255.0

[Sheridan]

Yeah I put them in their script generator like that, 192.168.0.1/255.255.255.0 etc and so on

 

I’ve removed the NS record only and it cleared the Dcdiag error but I’ve yet to check if the mobility server is still working on the iPads

[MatthewL]

Try just adding one IP range in and see if you get the error. So what you could do is add a pause after each line on the script and run the dcdiag and see which gives you the error.

 

Are you using a 10, 172 or 192 range for your network?

[Sheridan]

It must the NS entry - I edited the file to exclude all of the subnets, so it only had the A and NS and PTR records for the server created - Running dcdiag shows the same error.

 

If I delete the NS entry for the zone it clears the error. I a bit baffled as it seems to be correct to me

Edited May 23, 2020 by Sheridan

[MatthewL]

If you add the entries manually do you get the error?

[Sheridan]

As soon as I add the delegation NS record the error appears, even thought the name server in the NS record resolves OK

 

Very odd. At the moment I’ve only got the A record and NS record and the dcdiag error appears.

[damichaud]

I am seeing this same issue on my end. From what I can tell, Windows DNS does not like having a DNS zone that is not a valid Kerberos identified member. Have you had any luck suppressing the error from DCDIAG without deleting the entries needed for printing ? Edited June 8, 2020 by damichaud

[Sheridan]

No I'm still seeing the error in dcdiag

 

I'm wondering whether to add the DNS service onto the Papercut server to see if it helps - we have multiple DNS servers so another won't hurt

[rebelldtu]

I'm experiencing the exact same issue. Printing works fine but get the same dcdiag error. The subnets also show up as not verified in the Papercut Verify DNS section but all works without issue. Its a strange one which I suspect is to do with the way Papercut Integrate their solution in complex environments. I would imagine an in house fix needs to come from their side. Edited December 19, 2020 by rebelldtu

[nicholab]

Have you thought about using universal print instead?