When I create an account, I grab the domain expiration date from WHOIS
then and stick it in my database. If you did that then you could check
for it and delete old domains after the domain redemption period.
I think a slicker way for you to do it would be to actually check how
the domain resolves. If it stops resolving or starts resolving
elsewhere you know to stop service. This will catch if they move the
domain to other providers.
If you are hosting DNS for them also, make sure you are resolving to
upstream DNS servers and not yours.
Bryan Britt
Beltane Web Services
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ICQ: 53037451 Bryan L. Britt 501-327-8558 Beltane Web Services, Conway, AR http://www.beltane.com ~~~~~~~~~~Support Private Communications on the Internet~~~~~~~~~~----------------------- Original Message ----------------------- On Wed, 05 Jan 2005 05:37:59 -0500, Faeren <faeren@gospel.com> wrote:
> Hi Everyone, > > I do a fair amount of shared hosting on my web servers. There are now a > couple of thousand domains, and my clients are notorious for just > letting their domains expire when they no longer need them. > > What kinds of mechanisms are there available for determining such > domains periodically and removing them from my web, email and LDAP, and > DNS server configs? > > The only thing I could think of was grab the entire list and setup a > cron job to do a whois once a month and see what ones return > nothing--but this seemed kinda cumbersome. Can anyone think of other > ideas, or things they might currently be using that work? > > Thanks. > > > Faeren.
This archive was generated by hypermail 2.1.3 : Mon Jan 31 2005 - 23:00:01 EST