Skip to content
  • Solutions
    By Role
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    By Infrastructure
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
  • Product
    • Plesk Features
    • Plesk Editions
    • What’s new
    • Pricing
    • Roadmap
    • Lifecycle Policy
    • Extensions Catalogue
  • Pricing
  • Extensions
    Featured Extensions
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    Bundles and packs:
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack

    See all Extensions

  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
Plesk 360 login
Free Trial

Knowledge Base

Unable to reload DNS service on Plesk server: invalid command from 127.0.0.1#41838: bad auth

 
chrootdnsdns statisticsdomain nameplesk for linux

Symptoms

  • Some DNS records are not propagated automatically. Manual DNS service restart resolves this issue.

  • Unable to reload the DNS service:

    # service bind9 reload

    Job for bind9.service failed because the control process exited with error code. See "systemctl status bind9.service" and "journalctl -xe" for details.

  • The next rows appear in the /var/log/syslog or /var/log/messages files in an attempt to reload the DNS service:

    systemd[1]: Reloading BIND Domain Name Server.
    named[24013]: invalid command from 127.0.0.1#41838: bad auth
    rndc[24290]: rndc: connection to remote host closed
    rndc[24290]: This may indicate that
    rndc[24290]: * the remote server is using an older version of the command protocol,
    rndc[24290]: * this host is not authorized to connect,
    rndc[24290]: * the clocks are not synchronized,
    rndc[24290]: * the key signing algorithm is incorrect, or
    rndc[24290]: * the key is invalid.
    systemd[1]: bind9.service: Control process exited, code=exited status=1
    systemd[1]: Reload failed for BIND Domain Name Server.

  • There are two different keys specified in the /etc/named.conf and /etc/bind/rndc.key (or /etc/rndc.key) files:

    # /etc/named.conf

    key "rndc-key" {
    algorithm hmac-md5;
    secret "CeMgS**********yv0x40Q==";
    };

    # cat /etc/bind/rndc.key

    key "rndc-key" {
    algorithm hmac-md5;
    secret "aff2YA**********FRkj/g==";
    };

Cause

Two different keys are in conflict with each other.

Resolution

Use the same key in both files:

  1. Connect to the server via SSH.

  2. Get the key from the /etc/bind/rndc.key (or /etc/rndc.key) file and copy it.

    # cat /etc/bind/rndc.key

    key "rndc-key" {
    algorithm hmac-md5;
    secret "aff2YA**********FRkj/g==";
    };

  3. Open the /etc/named.conf and/or /etc/bind/rndc.conf file via any text editor and modify change the key to the correct one received from the previous step:

    [BEFORE]

    key "rndc-key" {
    algorithm hmac-md5;
    secret "CeMgS**********yv0x40Q==";
    };

    [AFTER]

    key "rndc-key" {
    algorithm hmac-md5;
    secret "aff2YA**********FRkj/g==";
    };

  4. Restart the DNS service:

    # service bind9 restart

    OR

    # service named-chroot restart

Tweet
Share
Share
Email
0 Shares
Read the full article
Related Posts

DNS_PROBE_FINISHED_NXDOMAIN: What Is It And How To Fix The Problem

Read More »

Setting up Your Ideal Web Development Environment With Plesk Essentials

Read More »

How to configure external DNS with DigitalOcean DNS extension on Plesk

Read More »
Knowledge Base

Bind9 service is running on a Plesk server but does not serve DNS queries

Read More »

Unable to start DNS service on the Plesk server: missing semi-colon before dnssec-lookaside

Read More »

Unable to start BIND DNS server in Plesk for Debian 9/Ubuntu 18.04: named: extra command line arguments

Read More »

Unable to start BIND on a Plesk for Linux server: loading from master file failed: file not found / zone not loaded due to errors

Read More »

Hosting Wiki

  • Server Redundancy
  • AMP
  • Bare Metal Server
  • Oracle VM Server
  • Server Virtualization Software
  • Windows Server
  • Linux
  • Domain
  • Plesk
  • Web Server
  • Static DNS
  • DNS Server
  • DNS Forwarding
  • Reverse DNS
  • SSH
X-twitter Linkedin Youtube Reddit Github
  • Product
  • Login
  • Pricing
  • Editions
  • For Partners
  • Partner Program
  • Contributor Program
  • Affiliate Program
  • Plesk University
  • Company
  • Blog
  • Careers
  • Events
  • About Plesk
  • Our Brand
  • Resources
  • User and Admin guides
  • Help Center
  • Migrate to Plesk
  • Contact Us
  • Hosting Wiki
  • Forum
  • Legal
  • Legal
  • Privacy Policy
  • Imprint

© 2025 WebPros International GmbH

Part of the WebPros®  Family