[FIXED BUG] NS records created in Plesk transferred to DigitalOcean incorrectly

Follow

Comments

5 comments

  • Avatar
    Gerinho Troenokarso

    Was just about to report this issue to Plesk support but then luckily found this article!

    I found out about this because I'm using vanity nameservers at DO while using the DO DNS Extension for Plesk, so my custom nameservers are indeed constantly being reset to the default three [ns1,ns2,ns3].digitalocean.com after a sync or alteration is triggered from Plesk.

    It occurs for example when Let's Encrypt is automatically updating SSL certificates, as it has to update the zonefile in Plesk for validation - hence triggers a sync to DO DNS and 'resets' the NS records back to the default 3 DigitalOcean NS records. Also it deletes any additional NS record (e.g. ns4.mydomain.tld) in DO.

    Question about the workaround: currently the version of the DO DNS extension used in Plesk is 1.1.5-51. To use the workaround I need to manually install the older extension version 1.1.4-45, is that correct?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Gerinho Troenokarso

    Thank you for the feedback.

    Yes, currently, only the version from this article contains a fix.

    Please, subscribe to this article to receive a notification in case the article gets updates.

    0
    Comment actions Permalink
  • Avatar
    Scott Berry (Edited )

    This was a fix for me as well, thank you! 

    I am getting an error when clicking on a domain in the DigitalOcean plugin listing of domains. 

    Any help?

    A potentially dangerous Request.Path value was detected from the client (:).
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (:).

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:


    [HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (:).]
    System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +11981636
    System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +52
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Scott Berry

    This behavior isn't typical for the extension.

    Does the issue persist after extension reinstall?

    Consider submitting a request for Plesk Support.

    0
    Comment actions Permalink
  • Avatar
    Gerinho Troenokarso

    A little tip for anyone with the workaround by using version 1.1.4-45 of the plugin instead of the latest version;

     

    Turn off the Auto-update toggle in Extensions:

     

     

    This will prevent the DO DNS Extension from automatically being updated to the latest version. I just found out it did that with me and couldn't automatically reissue SSL certificates for the domains on the server.

    As a downside, you'll have to update the extensions manually though, so keep that in mind with your server maintenance.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request