DNS domain expiration monitoring
-
@potemkin_ai : you have my sympathy, I agree it would be great to have something where stress and risk and outage avoidance can be minimised.
@scooke put together a system using Vikunja (app here on Cloudron) to handle it (https://forum.cloudron.io/post/36678)
May not be what you want but worth checking. -
@potemkin_ai sorry then, read that wrong
-
@potemkin_ai said in DNS domain expiration monitoring:
@nebulon I'm talking about the actual domain with the registrar
I guess we could implement this through a
whois
query. Not sure though if this is very useful, as the registrar itself should also warn you. But I understand that this email was overlooked in this case. -
I recommend looking into DomainMOD. I believe it would be a good solution to this problem.
Website: https://domainmod.org/
GitHub: https://github.com/domainmod/domainmodI'll add it to the App Wishlist!
-
Here is the link if you want to vote for it - https://forum.cloudron.io/topic/6428/domainmod-domain-management
-
@robi thanks, here are the arguments:
- you can't cover all registars and I don't have much DNS domains, so domainmod is not exactly a thing
- another e-mail from cloudron is something, I would treat completely different, as opposed to another possible advertising e-mail from registar
- if cloudron will display big red warning at the top of the admin, when domain is about to expire in, let's say less than a week, this would save as well.
I understand, it might be a rare event, but, considering that a complete DNS update takes like 72 hours, quite a nasty one.
-
@potemkin_ai I don't get how that could happen in the first place, aren't domain renewals usually default and you have to opt-out/cancel the renewal actively?
-
@msbt and on the client, holding DNS zone as well...
-
Out of curiosity, is this information even available? Is
whois
generally considered authoritative ? For display purposes, this seems like a good idea to me. Nice to have a summary of when domains are expiring, why not, if it's a whois call away. -
@girish the biggest problem will be the various tlds, because there is not one whois server which can do them all, you're looking at something like https://snippens.com/handbk/whois-servers or https://www.mobilefish.com/tutorials/whois_servers_list/whois_servers_list.html
-
WHOIS is not reliable on this at all ... I have seen several instances of whois saying a domain is about to expire when it has already been updated.
This feature would be cool, but I don't know of any way to implement this, short of having API access to various registrars.
-
it doesn't seem to be impossible thought (https://serverfault.com/questions/343941/how-can-i-find-the-whois-server-for-any-tld); and if the domain is not in whois database, you can display message, saying that your domain is not in our whois database - please, let us know what to query, if you would like us to keep you up to date with that - this way, if I'm using rare registar, who doesn't provide data to everyone, I can supply whoise server to query from this registar and be a happy user, knowing, that my Cloudron is also taking care about the DNS (without which it won't work like at all, btw).
-
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,