Following notification from VeriSign, on January 15th 2012 the price for COM and NET is again increasing.
VeriSign is increasing its pricing to ALL registrars as per their notice to us and ICANN.
.COM will increase by 51 cents USD
.NET will increase by 46 cents USD
This will be across all tiers and is the EXACT amount that VeriSign are increasing by.
We will update the pricing on the platform as of January 14th 23:55 GMT/UTC
LogicBoxes have been busy upgrading/improving the DNS infrastructure, this blog contains important information about changes you and your resellers must make for your branded nameservers (if using the FreeDNS service); please read through it in detail.
The importance of a stable and robust DNS service for any domain name or website can not be underestimated. In light of recent events that affected the DNS service, LB have been working towards enhancing our DNS infrastructure. The changes LB are about to implement will considerably improve DNS capability, which will ensure better reliability for all dependent services.
Salient features
The infrastructure setup for these servers is complete; your branded nameservers must now be updated to bring the changes into effect.
For partially branded nameservers
If you’re using only the partially branded nameservers, such as <some_prefix>.mercury.orderbox-dns.com, you do not have to do anything – LB shall make all the necessary changes.
For fully branded nameservers
If you’re using fully branded nameservers of the type ns1.domain.com, the IP addresses for these must be updated for the changes to take effect. Please do the following
|
Nameserver |
Partially Branded |
Current IP |
New IP |
|
ns1.domain.com |
.mercury. |
67.15.47.189 |
50.23.136.173 |
|
ns2.domain.com |
.venus. |
74.54.56.227 |
50.23.75.96 |
|
ns3.domain.com |
.earth. |
67.15.47.188 |
67.15.47.188 |
|
ns4.domain.com |
.mars. |
74.52.140.82 |
184.173.150.57 |
(Note: The old IP addresses marked in red will no longer be used)
How soon must you do this?
The new IP addresses are already functional, so you can make the changes immediately. The old IP addresses will be decommissioned after 07/11/2011 (7th November, 2011), so the changes must be completed before this date. This is extremely important, because after 07/11/2011, requests to the old IP addresses may not be answered, which would adversely impact domain names using your branded nameservers.
Please forward the information in this email to your resellers, so they may make the necessary changes to their branded nameservers as well.
We have just been informed that the OB has been placed under emergency maintenance.
We will update this post as soon as we know more.
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. |