Identify the exact hostname and record type you need to change. Keep a copy of the current record and its TTL. Confirm access to the registrar and the DNS provider, which may be different organizations.

1. Check the domain nameserver delegation using a DNS lookup or the registrar account. Determine which nameservers are authoritative for the zone.
2. Open the domain Hosting & DNS > DNS page in Plesk and review whether its DNS service is active and how it is configured.
3. If public authority is external, make the public change at that provider. Maintain the Plesk copy only where local services or your operational process require it.
4. If Plesk is authoritative, edit the exact record and apply the pending zone changes. Preserve unrelated MX, TXT, verification and certificate-validation records.
5. Query an authoritative nameserver directly, then compare normal recursive lookups. Record both the new answer and any remaining cache lifetime.

Confirm the expected authoritative answer and test the actual service, such as HTTPS or incoming mail. Check both IPv4 and IPv6 records when present. A correct A record with a stale AAAA record can produce inconsistent results.

If results remain different, investigate delegation, secondary synchronization and caches. Do not switch nameservers merely to make one record edit appear; that can move the entire zone and disrupt unrelated services. For DNSSEC-enabled domains, a broken delegation or stale DS record requires coordinated correction before ordinary records will validate.

• Updating a Plesk server DNS template without surprising customers
• Enabling DNSSEC for a Plesk-managed zone
• Adding another website domain in Plesk
• Adding supported Apache and nginx directives in Plesk

• Plesk: Plesk As The Primary DNS Server