Baza wiedzy
Create a DigitalOcean personal access token with read and write access and connect it, so your domains' DNS is served from your own DigitalOcean account.
Connecting your own DigitalOcean account lets a domain's DNS be served from your account instead of ours. You keep the zone, the bill and the vendor dashboard; we create and update the records your sites and mailboxes need, so you do not copy them by hand.
A DigitalOcean account with your domains added under Networking → Domains, or ready to add them.
In the DigitalOcean Control Panel, open API, then the Tokens tab, and in Personal access tokens choose Generate New Token. Name it, choose an expiry, and give it Full Access — or, with Custom Scopes, read and write access to domains. Press Generate Token and copy it; DigitalOcean shows it once.
Open Integrations in your dashboard and choose Connect an account. Pick Your own DNS as the group and DigitalOcean DNS as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
DNS is served from. We create the zone there if it does not exist and write the records the domain's sites and mail need.
add a mailbox — we update the record on your account.
registered with us, or at a registrar you have connected, we set them for you; otherwise the domain's page shows the nameservers to set.
The checklist beside the connection shows which of those we could confirm.
It connects, then the first record change fails. The token is Read Only. A read-only token connects successfully, because listing works; generate one with write access.
It stopped working. The token reached the expiry you chose. Generate a new one.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
Ten artykuł nie został jeszcze przetłumaczony na Twój język, dlatego czytasz wersję angielską.
O czym piszemy w kwestii hostingu, pozycjonowania i prowadzenia stron na dużą skalę.
Jak hosting wpływa na indeksowanie i autorytet linków w 2026 roku: utrzymanie stron w indeksie, weryfikacja leciwych domen przed ich użyciem, pozyskiwanie linków bez pozostawiania śladu oraz szczere spojrzenie na to, co infrastruktura może, a czego nie może zrobić dla SEO.
Przeczytaj post →Praktyczna lista kontrolna dla szybkiego i bezpiecznego WordPress: buforowanie na poziomie serwera, pamięć podręczna obiektu dla każdej witryny, garść wtyczek, które warto uruchomić, utrzymywanie stosu w aktualnym stanie oraz strony WooCommerce, których nigdy nie wolno buforować.
Przeczytaj post →Co tak naprawdę odróżnia dobry hosting zarządzany od taniego konta z panelem sterowania – migracje, kopie zapasowe, izolacja, prawdziwe cachowanie i uczciwa skalowalność – oraz jak to ocenić, zanim podejmiesz decyzję.
Przeczytaj post →Pomoc jest wliczona w każdy plan, dział wsparcia jest czynny przez 24 godzin na dobę i możesz pisać do nas w dowolnym z naszych 58 języków – odpowiadamy w Twoim.
Kontakt z pomocą techniczną → Wszystkie artykuły →