On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at MyPlesk.com/Plesk360/Platform360 please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Plesk does not update BIND zones

Follow

Comments

4 comments

  • Avatar
    Jorge

    Hi!

    Same problem here, but no errors when doing "/opt/psa/admin/sbin/dnsmng --update example.com"

    rndc works with no error (rndc reload example.com"

    But bind does not read records files, and keep answering requests with old DNS info.

    Any suggestion please?

    Thanks,

    Jorge.

     

    0
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    Hello @Jorge,

    There might be many causes due to which Bind does not load zones.

    So to get the exact error it is required to perform following steps:
    1. Reload Bind service.
    If Debian/Ubuntu-based distributions are used, please use the following command:

    service bind9 reload

    If CentOS/RHEL-based distributions are used, please use the following one:

    service named-chroot reload

    2. Check which records appear in /var/log/messages or /var/log/syslog files after the service reloading.

    Once the exact error is gotten from the log file, I recommend you to search around our Knowledge base: Plesk Help Center

    In case if nothing useful is found, please create a request to Plesk Technical Support: How to submit a request to Plesk support?

    0
    Comment actions Permalink
  • Avatar
    Jorge (Edited )

    Hi @Daria!

    After a good time of researching, I realized that the problem was with the signing and the serial.

    The way I found to fix the problem was:

    # rndc sync -clear <domain>

    # rm -f /var/named/chroot/var/<domain>.*  (except the zone file, keep it safe!)

    # systemctl restart named-chroot

     

    I hope this can help others.

    By the way, I'm sorry I posted this issue twice :-)


    1
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    Hello @Jorge,

    Thank you for sharing the information!

    Glad to hear that the issue was figured out :)

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request