Jase Posted April 2, 2008 Share Posted April 2, 2008 Currently no expiry date is given to transfered domains. The expiry date must be added manually in WHMCS. I beleive the most simple way to automate this is as follows: Using a cron job, have WHMCS do a whois, extract the expiry date and add it. It may not be the cleanest way, however it is better then having a human perform the same process. Until a cleaner way can be found, I beleive this would do for now. 0 Quote Link to comment Share on other sites More sharing options...
nielsenj Posted April 2, 2008 Share Posted April 2, 2008 Domain syncing is on the roadmap for 3.6.1 (http://dev.whmcs.com/ 271) I believe it's for DirectI as well so that should take care of this issue plus a bunch of others to do with domain management, yays! 0 Quote Link to comment Share on other sites More sharing options...
dsaunier Posted April 2, 2008 Share Posted April 2, 2008 If you have a reseller account, extracting the expiry date by API could be more reliable as Whois tend to have many layouts and not be clearly formatted, but you're both right it is a feature I've been waiting for, as many others it seems. 0 Quote Link to comment Share on other sites More sharing options...
Lucas Posted April 2, 2008 Share Posted April 2, 2008 Domain syncing is on the roadmap for 3.6.1 (http://dev.whmcs.com/ 271) I believe it's for DirectI as well so that should take care of this issue plus a bunch of others to do with domain management, yays! Hopefully because it only mentions Enom. We are looking for this aswell. 0 Quote Link to comment Share on other sites More sharing options...
Jase Posted April 2, 2008 Author Share Posted April 2, 2008 One issue is: WHMCS may not know when the domain has completed the transfer process. This could be resolved as follows: 1. When the transfer is initiated, WHMCS checks whois details and adds an entry into a text file. 2. A cron job checks the text file, then does a whois once each day, and when the details change, updates the expiry date and removes the entry from the text file. 0 Quote Link to comment Share on other sites More sharing options...
dsaunier Posted April 3, 2008 Share Posted April 3, 2008 As a precaution it could be useful to have a "dates sync" cronjob run say once a week, that would compare the expiry date of domains in WHMCS against a whois server, and alert us in case of discrepancies, so that we can manually upate the correct dates from the admin. Something else I'd be interested in, would be a cronjob checking domains in the system against a Whois, to get rid of domains that were transfered out by changing their status. Not sure what others think but I may add this as a suggested feature ? 0 Quote Link to comment Share on other sites More sharing options...
chickendippers Posted April 3, 2008 Share Posted April 3, 2008 There is the risk that if you make too many whois queries you'll get yourself blocked by the whois server. 0 Quote Link to comment Share on other sites More sharing options...
Ben-iNetFx Posted April 4, 2008 Share Posted April 4, 2008 As a precaution it could be useful to have a "dates sync" cronjob run say once a week, that would compare the expiry date of domains in WHMCS against a whois server, and alert us in case of discrepancies, so that we can manually upate the correct dates from the admin. Something else I'd be interested in, would be a cronjob checking domains in the system against a Whois, to get rid of domains that were transfered out by changing their status. Not sure what others think but I may add this as a suggested feature ? Modernbill used to do this if you used Enom - you'd run a cron every X days which just checked your account and syncronised the dates. This could be what Matt already added to 3.6.1 though? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.