0721GMT
LogicBoxes have just reported that their DNS service is “having issues”.
This affects all services, logging in, adding funds etc.
We will update this entry with more information as soon as we have more news!
0725GMT (from LB tweet)
MA:Our DNS is under attack due to which you will face problems with accessing Obox or hosting packages. Admin team would be fixing it ASAP
LogicBoxes have added a new set of IP addresses for outgoing mail services where the platform sends mail of your behalf.
Please find enclosed SPF information :
“v=spf1 ip4:67.15.47.0/24 ip4:67.15.35.0/24
ip4:67.15.254.0/24 ip4:67.15.253.0/24 ip4:67.15.246.0/24 ip4:67.15.238.0/24
ip4:67.15.184.0/24 67.15.98.0/24 mx ?all”
Emergency downtime scheduled by DC on the July 28th 2011
Based on an emergency maintenance required by our Datacenter, a brief downtime may be experienced on the 28th of July 2011. Please find the details of the same below:
Reason:
The Network Engineers at our DC have identified a faulty supervisor module in the router. After consulting with the vendor, they have determined that the standby supervisor needs to be replaced in order to prevent any unexpected service disruptions.
Maintenance Notice
Maintenance has thus been scheduled for some of our servers as these hardware upgrades need to be made.
Maintenance Window:
Date: Thursday July 28, 2011
Duration: 4 hours
Start Time: 05:00:00 GMT
Affected Services:
While these are hot pluggable modules, a reload of the active supervisor maybe required for it to properly recognize the new standby module. If at all the reboot is required, a service disruption of no more than 20 minutes can be expected.
While the engineers at our Datacenter will work to minimize the impact, customers may experience downtime on the above mentioned services.
Currently at 1705 GMT on 8th June 2011, Lb are experiencing a DDoS attack.
We will update this blog with more information as soon as we get it.
Update: 1718 GMT
We are seeing that some domains are now resolving, mostly control panel logins.
Logicboxes had a DNS attack this monring starting circa 06:30 – 06:40GMT, although the main netearthone.com domain functioned and the reseller panel showed, when logging in, as foundationapi.com is used within the signin process, this stopped resellers from logging into the cp.
The DNS issue was resolved around 07:34GMT and domains are reolving, thus login is working too.
We will post further updtes when we have more.
| Dear Reseller,
As part of LB’s efforts to cut down unsolicited email from their system and the problems created due to it, they’re introducing certain measures to mitigate such activities. The idea behind these measures is to ensure that our email system is not viewed suspiciously by other service providers, which would lead to email originating from our servers to be deferred or rejected. A lot of spam email that gets caught in LB’s anti-spam filters, and is reported to us by the feedback loop with other email service providers, shows a high correlation with spoofed envelope from addresses. For example, when a user a@domain.com authenticates with smtp.domain.com in order to send a mail from our outbound servers, he can currently set whatever he wants as his “from” address, including email addresses that don’t actually exist. This is a widely used method for email spoofing. In order to avoid such instances, users will now be asked to register a set of identities from their webmail interface for email addresses that need be used to send email. Every identity must have a valid email address, which must be authorized before it can be used to send email. The process to do so is fairly straight forward – 1. The user must log on to Webmail as a@domain.com, and add the necessary identities, say sales@domain.com and x@gmail.com. 2. The system will send verification emails to sales@domain.com and x@gmail.com, asking them: “a@domain.com is trying to use x@gmail.com to send email, do you want to allow this?“ 3. Upon confirmation, the user will be able to send email as x@gmail.com or sales@domain.com from their account. 4. A list of user accounts are allowed to use sales@domain.com as their from address will be stored by the system (since there may be more than one user who may want to use the same from address). To know more about setting identities, you may refer to this article: http://support.mailhostbox.com/email-users-guide/sender-identities LB are monitoring email logs to identify accounts that are sending email in this fashion. They shall pro-actively add identities for these accounts, and send out alerts to clients using a different ‘from’ address than the authenticated one. However, they might not be able to determine all users who need this feature. Thus, we recommend that you inform all your clients about this policy change, and ask them to add sender identities if required. The identities must be created and verified before the 24th of March, after which any unauthorized ‘from’ address will not be allowed to send email. |
Dear Reseller,
We’d like to draw your attention to the upcoming pricing changes for .BIZ and .ORG domain names. Please note that this pricing only applies to resellers reselling .BIZ and .ORG through NetEarth One:
New .BIZ Prices
To accommodate the Registry Price Hike announced by the .BIZ Registry, we will be increasing the Prices for .BIZ Domains from the 30st of March, 2011 at 12:30 UTC.
Following the hike, the Prices for .BIZ will be as follows:
Tier 1 : $9.90
Tier 2 : $9.40
Tier 3 : $9.10
Tier 4 : $8.99
Tier 5 : $8.79
NEW .ORG Prices
To accommodate the Registry Price Hike announced by the .ORG Registry, we will be increasing the Prices for .ORG Domains from the 30st of March, 2011 at 12:30 UTC.
Following the hike, the Prices for .ORG will be as follows:
Tier 1 : $9.90
Tier 2 : $9.40
Tier 3 : $9.10
Tier 4 : $8.99
Tier 5 : $8.79
As part of LB’s ongoing campaign against abuse and to ensure the security of our users’ email services, LB are planning to impose a stricter password policy for email accounts hosted with us. As a result of this change, the system will no longer allow passwords of the type that could be deemed vulnerable to sabotage attempts. Email account passwords must fulfill the following criteria henceforth –
1. The password must contain at least 8 characters (and can be up to 32 characters long).
2. The password can not contain the email prefix in its exact form. For instance, if your email address were john@yourdomain.com, then your password can not contain the word john.
3. The password must contain at least one alphabet (a-z in upper or lowercase), and at least one numeral (0-9).
To make communication with the end user easier for you, LB will shortly send a white-labeled advisory to all email users whose passwords do not satisfy these criteria, alerting them to update their password on or before March 20th, 2011. This email will be sent from do_not_reply@domainame.tld, For example if the domain name is xyz.com then the mail will be sent from do_not_reply@xyz.com and will include the new password criteria. It will not include any links.
If the users do not change their password then the password will be reset and a new password will be sent to the alternate email address of the end user.
LB will be displaying appropriate banners in the control panel and webmail of the end user as well.
We recommend that you contact your customers and inform them about this policy change. If you have any questions about this process, please contact our support team and we’d be happy to answer your queries.
Dear Reseller,
On the 8th of March a number of updates will be happening to the platform API which may affect both API users and module users (WHMCS, AWBS, etc).
The first change is applicable to the SOAP API only. It will now have IP restrictions, the same as the HTTP API.
If you use the API or a module then please do the following:
1. Login to the NetEarth One control panel.
2. Settings -> API -> HTTP
3. Enter your server’s IP (the server running the module or connecting to the API).
4. Hit submit to save the changes.
If you are already using the most recent version of the WHMCS module then you may have already added your IP for using the DNS functionality.
Please note the HTTP IP restrictions applies to BOTH the HTTP and the SOAP APIs.
The second change is also applicable to only the SOAP API. The URLs for using the API have now changed.
The new end point URLs are as follows:
https://soapapi.com/anacreon/servlet/APIv3
http://soapapi.com/anacreon/servlet/APIv3
SOAP users need to update their URL to one of the above. Please note the WSDL files have NOT changed and thus all that is required is the URL change.
If you are using the most recent version of WHMCS you will not need to update as the newest version of WHMCS has the updated URLs. Those using older versions of WHMCS please update your copy to receive the updated module.
If you are using AWBS then please update the URL in your settings for the NetEarth One module.
Any other billing platforms please update the URL where applicable or contact the billing platform support for assistance.
We will be launching a new independent module for WHMCS within the next few weeks which will offer new functionality and support direct from ourselves. The new module will also feature SSLReseller (http://www.sslreseller.com) integration.
If you have any questions then please contact us and we’ll be happy to assist.