DNS_ERROR_DP_DOES_NOT_EXIST

KB Home   |   DNS_ERROR_DP_DOES_NOT_EXIST

“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.

  1. Before running the commands, copy them into a text editor like Notepad.
  2. Edit the commands and replace /dsforwarder with /forwarder
  3. Replace /dsprimary with /primary.
  4. 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.


Categories: Mobility Print


Keywords: PowerShell

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on December 12, 2018, at 06:45 PM
Printable View   |   Article History   |   Edit Article