27f0f1c0ac
* fix: correct DNS sync results and configuration retention Keep address families independent, reject failed update responses, preserve complete IPv6 addresses, and retain Studio drafts and effective extra settings. Add offline regressions and wire Studio tests into documentation builds. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * test(provider): make disk cache regressions deterministic Align the cache fixture wall clock and file mtime so Windows Python 3.12 clock granularity cannot turn a freshly saved cache into a future-dated file. Keep real disk reads, all cache assertions, production expiry policy and CI matrices unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: NewFuture <6290356+NewFuture@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2.0 KiB
title, description, layout, editLink, lastUpdated, aside, sidebar
| title | description | layout | editLink | lastUpdated | aside | sidebar |
|---|---|---|---|---|---|---|
| DDNS Configuration Builder and Validator | Build and import DDNS Schema v4.1 configurations in your browser, with static checks for structure and runtime requirements. Supports multiple providers, IPv4/IPv6, proxies, cache, and logging. | page | false | false | false | false |
::: details Imports, drafts, and custom fields For configurations created, pasted, or edited on this page, Load into builder does not count as an export. When temporary browser storage is available, complete unexported drafts (including credentials) are saved in the current tab and can be restored after a refresh; copying or downloading marks them as exported. An unchanged file import still uses the original file as its saved baseline. Older drafts without file-origin information are conservatively retained as unexported.
Leave provider custom fields blank to inherit the global JSON extra; enter {} for an explicit empty override, which does not clear custom fields supplied by environment variables. Imports resolve flat fields, extra_ aliases, and nested extra in runtime precedence order. To preserve effective values, inherited fields are expanded into explicit provider custom fields when needed; those explicit values subsequently override global settings.
:::