Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion -
Inviting everyone to the UX test of a new security feature in the WP Toolkit
For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.
Question Adding PTR record
- Thread starter ITTECH
- Start date
Unfortunately, Plesk doesn't support this behavior, because creating reverse zones for subnets smaller than 255 addresses is a problematic issue that can be solved in compliance with RFC2317.
Network /32 is merely a special case.
That is, the zone /32 also requires the creation of reverse zone according to RFC2317, because when you create a zone in the usual case, you have to create the zone:
123.123.123.123.in-addr.arpa
but there is still need to add a PTR record descriptions to describe the reverse resolving:
123 IN PTR test.plesk.com.
But it must match the address 123.123.123.123.x (123.123.123.123.123) that is no longer IPv4 address.
Network /32 is merely a special case.
That is, the zone /32 also requires the creation of reverse zone according to RFC2317, because when you create a zone in the usual case, you have to create the zone:
123.123.123.123.in-addr.arpa
but there is still need to add a PTR record descriptions to describe the reverse resolving:
123 IN PTR test.plesk.com.
But it must match the address 123.123.123.123.x (123.123.123.123.123) that is no longer IPv4 address.
Similar threads
