“Help! I’m trying to run the DNSCMDs to set up the DNS records for Mobility Print, but I’m seeing an error “Command Failed: DNS_ERROR_DP_DOES_NOT_EXIST”. What does this mean and how do I set up the records?”
You will see this error appear if your DNS server is not part of an Active Directory domain. When the Mobility Print server generates the DNSCMDs to create the DNS records for Mobility Print, we assume that you want these records to replicate to the other servers in your Active Directory Domain so we use the switch /dsforwarder and /dsprimary.
However, if your DNS server is not part of an Active Directory domain then you will run into this error. The easy fix is to edit the script to remove “ds” wherever you find it, and run the revised commands.
Before running the commands, copy them into a text editor like Notepad. Edit the commands and replace /dsforwarder with /forwarder Replace /dsprimary with /primary. Then try running the commands again. Still have questions? Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our Support Portal for further assistance.
Articles in this section
- Users receive "Need admin approval" error with Scan to OneDrive for Business
- Resolving PaperCut NG/MF performance issues by maintaining its internal database
- Preserving print script discounts when changing print jobs attributes at the device
- Load Balancing Concepts for PaperCut Environments
- PaperCut MF 24.1.8 - Document Processing information and FAQs
- Manually Generating and Installing iOS AirPrint Profiles for Mobility Print (When Auto Setup Fails)
- Common Xerox Issues and how to fix them
- PaperCut NG/MF Security Bulletin (May 2025)
- How to permit users to cancel print jobs at HP MFD
- How to remove a print job from the queue
Comments
0 comments
Please sign in to leave a comment.