Atjaunot domēnu pirms tā termiņa beigām

Kad izmantot

A company-held domain has an expiry approaching, or the weekly sweep found one. Not for a domain held at another registrar that the company wants to consolidate — use tech.move-domain-to-bc first, then this playbook covers it. Not for a domain the company does not yet hold — use tech.register-domain. The recurring watch over *all* contract deadlines is ops.contract-renewal-watch; this playbook is the domain-specific one the watch points at.

Pirms sāc

• The domain list is current: holder, registrar, expiry, auto-renew state for each domain.
• The billing contact is a role address (domains@company), not a person's mailbox.
• The keep/drop rule is known — default: keep anything that resolves, has mail on it, or is defensive for a live brand.

Ko izpilde pieprasa1

Ceļš8 soļi

1. S1

   Sweep the listaģents

   Read every domain's expiry and auto-renew state from the registrar (or bc domains onboard <domain> --tenant <slug> in dry-run for a read-only view of delegation state).

   Izdarīts, kad each domain is marked: ok (>90 days) · renew soon (≤90 days) · urgent (≤30 days) · dropped-on-purpose.

2. S2

   Check the holder and the contactsaģents

   For each domain due, confirm the holder is the company and the registrant e-mail is a role address that is actually read.

   Izdarīts, kad any domain held in a person's name or pointing at a dead mailbox is flagged in the report.

   ⛔ A domain renewed under a departed employee's name stays un-renewable by the company when that person's account is closed.

3. S3

   Check each domain is still wantedaģents

   For each urgent domain, look up what uses it: website, mail, redirects, DNS records beyond a placeholder.

   Izdarīts, kad each domain has keep / drop / ask-owner, with the evidence ("MX records live for 12 mailboxes" or "no records, no site, last seen in 2023 campaign").

4. S4

   Decide and approveīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S4 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Present the renew-soon and urgent list with price per year per domain and the S3 recommendation.

   Izdarīts, kad the owner has marked each domain renew or drop, and approved the total spend.

   ⛔ The agent never pays the renewal invoice without this approval — a renewal is a payment to a third party.

5. S5

   Renewaģents

   Pay the approved renewals from the company's payment method, for the term the owner chose (default 1 year).

   Izdarīts, kad the registrar shows the new expiry date for each renewed domain.

6. S6

   Fix what S2 flaggedaģents

   For domains with a wrong holder or dead contact: update the registrant data to the company and the role address. For .lv this runs through the NIC.lv account; if the holder change needs NIC.lv approval, open the task and track it.

   Izdarīts, kad the registrar shows the company as holder, or a dated task exists for the pending change.

7. S7

   Confirm auto-renew and the watchaģents

   Turn auto-renew ON for every kept domain (where the owner has not said otherwise) and confirm the expiry sits in the renewal watch.

   Izdarīts, kad the domain list shows auto-renew = on and the next sweep date for each domain.

8. S8

   Record and hand backaģents

   Log each renewal (domain, amount, term, new expiry, payment reference) and send the owner a three-line summary: renewed, dropped, flagged.

   Izdarīts, kad the summary is sent and the log row exists.

Pārbaudes — kā zinām, ka izdevās

• New expiry dates read back from the registrar match the log (not from the payment receipt alone).
• Holder = the company's registration number on every kept domain.
• Auto-renew = on and the billing contact is a live role address.
• For one sampled renewed domain: the zone still answers and the site still opens over HTTPS.

Ja noiet greizi

Ko atstāj katrs solis

1. S1each domain is marked: ok (>90 days) · renew soon (≤90 days) · urgent (≤30 days) · dropped-on-purpose.
2. S2any domain held in a person's name or pointing at a dead mailbox is flagged in the report.
3. S3each domain has keep / drop / ask-owner, with the evidence ("MX records live for 12 mailboxes" or "no records, no site, last seen in 2023 campaign").
4. S4the owner has marked each domain renew or drop, and approved the total spend.
5. S5the registrar shows the new expiry date for each renewed domain.
6. S6the registrar shows the company as holder, or a dated task exists for the pending change.
7. S7the domain list shows auto-renew = on and the next sweep date for each domain.
8. S8the summary is sent and the log row exists.

Ko saglabāt

Per domain: expiry before and after · payment reference and amount · holder as shown by the registrar · auto-renew state · the owner's renew/drop decisions in S4 (who, when) · any task opened in S6 with its date.

Kā šī procedūra uzlabojas

After every 10 sweeps ask: did any renewal happen inside 30 days, and why did the earlier reminder not land? Did any drop decision later cause a re-registration or lost mail? Did any domain still sit in a person's name? A new version changes the sweep or the reminder that failed, and says so in its change note.