Check the actual server TTL before relying on a change made through PD DirectAdmin DNS. The released module reads TTL information but does not include a requested individual TTL in its record-write request.

Separate the editor from the provider result

The shared record editor and DNS package defaults can display or pre-fill a TTL. That does not mean this released DirectAdmin write applies it. Saving another record value is not proof that its requested TTL changed too.

Check the actual setting

1. Open the intended zone and note the current record and server-reported TTL.
2. Review the requested change and any result from the module.
3. Read the record back and compare authoritative DNS.
4. Check the native DirectAdmin TTL policy with the responsible administrator.
5. Retain the actual before/after result while your hosting team checks the server’s served value.

DirectAdmin’s own DNS Management can offer Override TTL value where the server allows it. Its TTL configuration reference describes that domain-level override. Use the permitted native control with the administrator; do not edit server configuration or repeatedly write an unchanged record to force a TTL.

Plan changes using observed TTLs

For a website or mail cutover, base the cache-transition plan on the TTL actually being served. Earlier cached answers can remain until their previous TTL expires.

The same write limitation applies to imports, templates, automation and snapshot recovery when they use this module. A snapshot is not a promise of restoring an earlier TTL exactly. Keep TTL expectations separate from whether the intended names and values were added or removed correctly.

Check the TTL actually served

Your hosting team should compare the requested editor value, server-reported TTL and authoritative answer without treating another successful record change as proof that TTL changed. This released write path omits the individual TTL; repeating the same module edit will not supply it. Review any permitted native domain-level TTL override with your DirectAdmin administrator, and base a cache-transition plan on the value actually served. Inspect the full record set after an uncertain edit because old and new values can coexist.

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