• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Named fails to start...

R

RingofFire

Guest
I have tried reinstalling and it still doesn't help. After about an hour or two of setting up a couple domains in plesk, named crashes and fails to start with this error:

[root@svr ~]# /etc/rc.d/init.d/named start
Starting named:
Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
77.210.207.in-addr.arpa:12: unknown RR type '65.2'
zone 77.210.207.in-addr.arpa/IN: loading master file 77.210.207.in-addr.arpa: unknown class/type
_default/77.210.207.in-addr.arpa/IN: unknown class/type
zone test.appalhost.info/IN: loaded serial 1171170219
zone appalhost.info/IN: loaded serial 1171170219
53.254.65.in-addr.arpa:12: unknown RR type '65.2'
zone 53.254.65.in-addr.arpa/IN: loading master file 53.254.65.in-addr.arpa: unknown class/type
_default/53.254.65.in-addr.arpa/IN: unknown class/type
[FAILED]





I have no clue why this is happening. Fedora Core 5 64bit with Plesk 8.1.0, fresh install and up to date.
 
well, I deleted the bad PTR record in the file.

But plesk keeps generating it again every time a new domain is added.
 
Its the hostname PTR record, not from one of the domain names.

I changed the hostname earlier but it is still putting the incorrect record in the file every time a new domain is added.
 
Back
Top