Check TTL in Plesk’s own DNS settings before relying on a change entered through PD Plesk DNS. This module does not send an individual TTL with its record writes; a number displayed in its record list can be a fallback rather than Plesk’s actual value.

Separate record values from cache lifetime

1. Open the intended zone and confirm the record’s full name, type and value.
2. Compare its TTL with the native Plesk DNS view or authoritative answer.
3. Review any previous TTL that may still govern cached answers.
4. Plan the intended DNS move before changing service destinations.

Saving a record value is not evidence that the TTL typed in the shared editor was applied. The same limit matters for imports, templates, automation and snapshot recovery.

Change native TTL policy deliberately

Use the permitted Plesk DNS controls with the responsible administrator. Plesk’s primary DNS guide describes native DNS management. Review the relevant record TTL and zone default separately; do not assume every modern Plesk server supports only a single zone-wide value.

Check the resulting authoritative TTL after the approved native change. Reducing a TTL now does not shorten the lifetime of an answer already cached under its earlier value.

Investigate an unchanged display

Do not repeatedly save an unchanged record to force its TTL. Module default TTLs and per-type package defaults do not bypass this provider limitation.

For an edit, inspect the full current record set as well: a failed old-record removal can leave both values. Retain the requested change, native result and original action time while your hosting team checks the actual values. Use the troubleshooting guide for a refused write.

Check the TTL actually served

Your hosting team should compare the requested editor value with native Plesk DNS settings and authoritative answers; a TTL displayed in the module can be a fallback rather than the actual server value. Module record writes omit the individual TTL, so repeatedly saving the same record does not apply it. Review the permitted native record and zone-default controls with your Plesk administrator, and plan cache transitions using actual served and previously cached values. Inspect the full record set after an uncertain edit because old and new values can coexist.

See the PD Plesk DNS WHMCS guide for related tasks, or explore the module.