Skip to content

Renewal strategy: I calendar every expiration

General Discussion by kenji3 3 replies 273 views
#1

I may be wrong, but this has saved me twice. I maintain:

  • Domain renewals: 60 days, 30 days, 7 days, 1 day before
  • SSL certificates: 30 days, 14 days, 3 days
  • Server invoices: 7 days before due date
  • IRR object maintenance: annual reminder

All in one calendar, synced to phone and backup account. Asia-Pacific timezone for my HostHatch and RackNerd boxes, UTC for global coordination.

Paranoia? Perhaps. But I lost a domain in 2019 to a simple oversight. Never again.

What systems do others use?

conbini > datacenter snacks
#2

I use the calendar too but I put EVERYTHING in code block

$ cal -A 2
$ whois example.com | grep Expiry
$ echo "renew domain" | at now + 30 day

The reminder will send every morning I have two server at GreenCloudVPS XD

But I hear the calendar provider it go down last week my friend she miss the SSL renew the site it show red for 6 hour very bad

4 #3
techmei said:
The calendar provider it go down last week

The ticket said: "URGENT: customer claims calendar outage caused domain expiration, demands we restore deleted domain from backup."

Domain was with separate registrar. Customer had set one (1) reminder. In 2019.

I checked: domain now squatted by obvious phish. The ticket said: "your negligence caused reputational damage." Our SLA covers compute, not customer's choice of calendar provider.

Dry fact: we see 3-4 "calendar failure" expirations yearly. Always single point of failure. Always "but it worked before."

reported. resolved. repeat.
#4

---
- strategy: defense in depth
- primary: calendar reminder
- NOTE: single provider = single point of failure
- secondary: registrar auto-renew
- WARNING: requires funded account, card expiry tracked
- tertiary: WHOIS monitoring
- tool: custom script, cron, 6 hour check
- code:

Whois $DOMAIN | grep -I "expir" | mail -s "ALERT" admin

- my setup:
- RackNerd: auto-renew ON
- HostHatch: manual, calendar + script
- personal: calendar provider A + calendar provider B
- NOTE: not same backend
---
The outage: it happen to me
- provider: unnamed major service
- duration: 11 hour
- result: missed reminder
- saved by: secondary script
---
Recommendation: never trust one layer

indentation is not optional

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft