DNS domain expiration monitoring
-
Looks like the whois list is available as json here - https://github.com/FurqanSoftware/node-whois/blob/master/servers.json and another here - https://github.com/weppos/whois/blob/main/data/tld.json . @potemkin_ai great link! didn't know the ways to discover whois servers.
-
@mehdi said in DNS domain expiration monitoring:
This feature would be cool, but I don't know of any way to implement this, short of having API access to various registrars.
Yeah.. same, I suspect if we add this, it will be more informational than authoritative. whois is often outdated/lags. So maybe we even let the admin set the expiry date for domains with missing/wrong whois records.
-
@potemkin_ai said in DNS domain expiration monitoring:
it doesn't seem to be impossible thought (https://serverfault.com/questions/343941/how-can-i-find-the-whois-server-for-any-tld);
You misunderstand my point : the problem is not finding the correct whois server. That is trivial. The problem is that the information in whois responses about domain registration expiration dates is, more often than not,
-
@mehdi even if, it’s better than nothing
-
This addresses both of your concerns:
-
Checked when the domain is added to cloudron, that's fairly reliable as the pattern is new domains get added, plenty of time. 1yr+
-
Close to that expiration date for the domain from 1. , it can warn and be checked until a renewal is detected or marked renewed. Better than 72hrs.
@girish Cloudron can keep track of this in the DB and warn/update accordingly. Easy-peasy.
-
-
@potemkin_ai said in DNS domain expiration monitoring:
@mehdi even if, it’s better than nothing
I honestly don't believe so : a check that has more false-positives than true positives is not very useful... It would worry people about nothing all the time.
-
@mehdi we definitely have a different perspective here.
I believe, that giving me a chance to prevent service shutdown for 72 hours for the outside world is a very valuable thing.
I also like the idea of fetching fresh data from whois on expiration data and letting me to correct whois server or the expiration data itself.
There is little I can do to turn you into my faith, I'm just saying what I see and experience.
-
@potemkin_ai I'd be in favour of Cloudron adding in some nice-to-have like a domain expiry notification if it has that access but also only if it's feasible to include in the first place. I wouldn't want that taking away hours from the Cloudron team.
Ultimately though as I see it, the trigger for this feature request seems like more of an issue with notifications from the registrar which is well outside of Cloudron's scope.
Additionally the result of losing a domain can easily be avoided by enabling auto-renew. I recognize Auto-Renew isn't for everyone (some people don't like having credit cards on file for instance) but it's used by the vast majority and is quite literally designed to avoid this very issue. If the risk of losing a domain is too high, then auto-renew should be used.
Also, a simple Calendar entry can help. I have my Calendar with entries with 2-week reminders for all my domains just in case so I can double-check that it has auto-renew enabled and if not then I can set it correctly or renew it manually right then and there.
We have to take responsibility with ownership of domains and ensure these things don't happen and there many ways to do that ourselves (two most common mentioned above). I don't believe Cloudron should be the vessel for that task personally, but hey if it's an easy add then totally cool to see.
-
If this is such a big issue and you can't pay attention to the emails from your registrar to renew your domain then transfer it to a registrar that will auto-renew the domain for you.
-
@colonelpanic thank you for the advice; it's just that I didn't look for one, sorry.
But, to recap: as I mentioned earlier, when you start managing your client's domains and earn money with Cloudron, things get complicated.
-
@potemkin_ai said in DNS domain expiration monitoring:
when you start managing your client's domains and earn money with Cloudron, things get complicated.
That is exactly what I do though (and I suspect many others in here), and have never had a problem with domain expirations in about 12 years of managing them for a couple dozen customers. It makes me wonder if the issue for you comes down to the registrar you're using or your own administration techniques that may need to change or be tweaked to improve managing domains for customers. I don't find it complicated at all, personally, but maybe that's just down to what I do.
What I do that may help you:
- Generally aim to use one domain registrar if possible, or at least as few as possible to allow support for them to be easier to use and some registrars even give small discounts after 10 domains are registered with them for example
- Setup all domains for auto-renewal enabled
- I bill customers annually for hosting which includes their domain name and it's always for the next calendar year. So I'll bill in late November 2022 for the service calendar year of 2023 for example, meaning that if they choose not to renew services then I simply disable the auto-renew feature on their domain so it doesn't accidentally charge my card when it's due in 2023 (and if I forget, I'm only out about $20 CAD which is really just a cost of doing business as it would be my own fault if I forgot to disable auto-renew)
- I add domain expiry reminders to my calendar with an alert 2 weeks in advance for me to double-check everything ahead of time (once it's all set though it's basically set-and-forget, but nice to have the time to double-check if needed)
- I remind my customers periodically (about once or twice a year) to ensure they want the same domain name going forward and if they want a different one (or even just a different TLD for example) so that I can plan accordingly if they desire any changes to be made for the next year ahead
I'd still enjoy seeing Cloudron assist if possible (after all, technology is meant to help us not harm us), but I also recognize that's really outside of their scope of work at least IMO when domains are all registered and renewed and generally managed outside of Cloudron, and would hate to see hours wasted on it when so many other things are very highly requested and more inside the scope of what Cloudron is meant to be responsible for. If it's an easy thing to add though, then cool. Hopefully the advice above helps you out in the meantime though.
-
@potemkin_ai Why at cloudron?
my setup :
I get my domain renewal notices from my registrar but for this to work flawlessly,
you can't use a cloudron email to get the alerts, it needs to be an out of cloudron context email (gmail etc..)
in my case it's dedicated to this & billing of domain/vps's, so I know every time there is an email there it's important and need to be taken care of.When everything is smooth, I usually auto-forward these type of emails to my associates, so I'm not the only one getting it or not and since the mailbox getting them is outside cloudron it's very rare to miss something.
On top of that, at my registrar, I set auto-renewal for all my domains, why set manual if you know in advance you need that domain Up for the foreseeable future ?
When the domains is owned by the client, I request a technical access to their registrar and configure auto-renewal and their payment with them so that it's out of the way, if the client insist on doing it on it's own, it's their responsibility to renew and face downtime because of domain expiration.
-
@rmdes because when app hosted on cloudron stops working, cloudron is the first thing I check.
I don't believe e-mail notifications is good, but a kind of red line at the top of the cloudron if domain is about to expire seems like a good thing to do.
Especially, if domain is handled by a customer (like it should) and cloudron and linux stuff is outsourced.
-
@potemkin_ai I understand your point, maybe a temporary fix would be to use something like this https://github.com/nixcraft/domain-check-2 (but you don't want email notif)
I wish I could have something similar but able to send a webhook where I want (N8) -
@rmdes thank you; my ideal case would be for cloudron to monitor this, giving a fix for malformed whois queries - we even made a simple algorithm for that somewhere at the top of the topic.
webhooks (to n8n / integromat / etc) would be just fantastic, indeed!
-
@potemkin_ai in my use case, webhook only would be even better, since I have space tuned in my Matrix server where other alerts end up
might be a cool fork to do on this
https://github.com/nixcraft/domain-check-2 and since it's bash, adding a webhook here would be trivial, maybe a fun exercise for next weekend for me -
@rmdes that's exactly my thought as well - webhooks are really nice, as they let every user to set up things and notifications the way they want and I do use work chat as well (just self-hosted Mattermost), so it would be really convenient.
For the script - I don't like (and don't have now) bare Linux servers running, so script could be Ok, but I would rather use an n8n node for that - easier to configure, update and get notifications from, if that can't be done out of the box on Cloudron - which is always the best thing, as it helps me to keep things on radars without thinking about them.
