Month: August 2018 Archives

Home / Archives for August 2018

Cookie Notice

This site utilizes cookies to improve your browsing experience, analyze the type of traffic we receive, and serve up proper content for you. If you wish to continue browsing, you must agree to allow us to set these cookies. If not, please visit another website.

Whitelabel Nameservers on Route53

This is a quick(ish) how to that you can do to utilize one of your registered domains on Amazon’s Route53 service.

Required:

  • A registered Domain
  • An account with Amazon’s AWS, in particular, their Route53 service
  • An IAM account, with API access to allow the creation, reading, and updating Route53 Domain records
  • The AWS cli installed on a linux distro that you have shell access to
  • A bit of patience
  • Remembering what DNS propagation is like…

How to do it:

First things first, drop into shell on your linux machine and run the following command.  You will need to copy/paste it’s output, so have your favorite text editor handy.

aws route53 create-reusable-delegation-set --caller-reference $(date +%s%N)

The output of this command should look similar to the following:

{
 "Location": "https://route53.amazonaws.com/2013-04-01/delegationset/N244H6F5LUSLJ8",
 "DelegationSet": {
 "NameServers": [
 "ns-39.awsdns-04.com",
 "ns-523.awsdns-01.net",
 "ns-1129.awsdns-13.org",
 "ns-1612.awsdns-09.co.uk"
 ],
 "CallerReference": "1512169214076311809",
 "Id": "/delegationset/N244H6F5LUSLJ8"
 }
}

Once your delegation set is created you will need to run and capture a few more commands so we can get the IPv4 addresses, and the IPv6 addresses, so stay in shell for now.

From the output, copy and paste the “Id”, and the “Nameservers” to your text pad, and save it.

Now, in shell, run this for each of the nameservers in the “Nameservers” block, and copy and paste the output from each

host ns-39.awsdns-04.com

This will return you the IPv4 and IPv6 addresses, which we will need soon.

Now, you can create the hosted zone at Route53 by using the following command.  It will specify the delegation set that you retrieved the Id from above, so replace the appropriate placeholder with the Id you already copy and pasted, also replace your domain name.  If you already use Route53 for your domain, you will need to export your zone file, delete all records, and finally delete the name from it… importing the records back again after you run the following command… it only takes 15-20 seconds, and typically your TTL will be much greater than that.

aws route53 create-hosted-zone --caller-reference $(date +%s%N) --delegation-set-id /delegationset/THE_DELEGATION_ID --name YOURDOMAINNAME.EXT

You will need the returned ID… so copy and paste it somewhere…

Now, pop over to AWS Route53, we need to create some A and AAAA records for each of the nameservers you need for your whitelabel.  One for each record type, and you will use the appropriate IPv4 for the A record, and IPv6 for your AAAA record.   Do not forget to name them… typically, they are named ns# where # is a number.

Now, back to shell, here we’re going to force the domains nameservers and SOA records

# Force the Nameservers Upon Us
aws route53 change-resource-record-sets --hosted-zone-id /hostedzone/YOUR_HOSTED_ZONE_ID --change-batch '{
 "Changes": [{
 "Action": "UPSERT",
 "ResourceRecordSet": {
 "Name": "YOURDOMAINNAME.EXT",
 "Type": "NS",
 "ResourceRecords": [
 {"Value": "ns1.YOURDOMAINNAME.EXT."},
 {"Value": "ns2.YOURDOMAINNAME.EXT."},
 {"Value": "ns3.YOURDOMAINNAME.EXT."},
 {"Value": "ns4.YOURDOMAINNAME.EXT."}
 ],
 "TTL": 60
 }
 }]
}'

Make sure to change the ns1-4 to whatever it was you decided to use when you named them above.

# Force the SOA Upon Us
aws route53 change-resource-record-sets --hosted-zone-id /hostedzone/YOUR_HOSTED_ZONE_ID --change-batch '{
 "Changes": [{
 "Action": "UPSERT",
 "ResourceRecordSet": {
 "Name": "YOURDOMAINNAME.EXT",
 "Type": "SOA",
 "ResourceRecords": [
 {"Value": "ns1.YOURDOMAINNAME.EXT. hostmaster.YOURDOMAINNAME.EXT. 1 7200 900 1209600 60"}
 ],
 "TTL": 60
 }
 }]
}'

Change that ns1 above to whatever you decided to use for your “primary” nameserver record.

Now you need to “glue” it all together 😉

Run this command, replacing your domain, and the IP’s you got and set above

aws route53domains --region us-east-1 update-domain-nameservers --domain-name YOURDOMAINNAME.EXT --nameservers Name=ns1.YOURDOMAINNAME.EXT,GlueIps=THE_IPV4,THE_IPV6 Name=ns2.YOURDOMAINNAME.EXT,GlueIps=THE_IPV4,THE_IPV6 Name=ns3.YOURDOMAINNAME.EXT,GlueIps=THE_IPV4,THE_IPV6 Name=ns4.YOURDOMAINNAME.EXT,GlueIps=THE_IPV4,THE_IPV6

Congratulations, you have now whitelabeled your nameservers to a domain of your chosing.  You can move forward with updating the rest of your domains nameservers if you wish to utilize these new nameservers.  If they are managed at Route53, you can use the following to utilize the delegation set you created earlier.

# Force the nameservers upon us
aws route53 change-resource-record-sets --hosted-zone-id /hostedzone/YOUR_HOSTED_ZONE_ID --change-batch '{
 "Changes": [{
 "Action": "UPSERT",
 "ResourceRecordSet": {
 "Name": "YOUR_OTHER_DOMAINNAME.EXT",
 "Type": "NS",
 "ResourceRecords": [
 {"Value": "ns1.YOURDOMAINNAME.EXT."},
 {"Value": "ns2.YOURDOMAINNAME.EXT."},
 {"Value": "ns3.YOURDOMAINNAME.EXT."},
 {"Value": "ns4.YOURDOMAINNAME.EXT."}
 ],
 "TTL": 7200
 }
 }]
}'

# Force the SOA upon us
aws route53 change-resource-record-sets --hosted-zone-id /hostedzone/YOUR_HOSTED_ZONE_ID --change-batch '{
 "Changes": [{
 "Action": "UPSERT",
 "ResourceRecordSet": {
 "Name": "YOUR_OTHER_DOMAINNAME.EXT",
 "Type": "SOA",
 "ResourceRecords": [
 {"Value": "ns1.YOURDOMAINNAME.EXT. hostmaster.YOURDOMAINNAME.EXT. 2018080301 7200 900 1209600 8600"}
 ],
 "TTL": 7200
 }
 }]
}'

# Set the "no glue needed" nameserver records
aws route53domains --region us-east-1 update-domain-nameservers --domain-name YOUR_OTHER_DOMAINNAME.EXT --nameservers Name=ns1.YOURDOMAINNAME.EXT Name=ns2.YOURDOMAINNAME.EXT Name=ns3.YOURDOMAINNAME.EXTName=ns4.YOURDOMAINNAME.EXT

Our Privacy Policy

Last Updated: June 18th, 2025

Introduction

Western Mass Hosting (“we,” “our,” or “us”) respects the privacy of all individuals and organizations that interact with our services. This Privacy Policy establishes our practices regarding the collection, use, disclosure, and protection of personal information for visitors to our website and clients utilizing our managed hosting and WordPress services. By accessing our website or engaging our services, you acknowledge that you have read and understood this policy in its entirety.

Scope and Applicability

This Privacy Policy governs our handling of information collected through our corporate website and in the course of providing managed hosting, WordPress maintenance, and development services. In accordance with global privacy regulations, we serve as a Data Controller for information related to our business operations and client relationships. When processing data on behalf of our clients through hosted services, we act as a Data Processor under applicable data protection laws.

Information We Collect

We collect various categories of information necessary to provide and improve our services. This includes personal contact and payment details provided during account registration, technical information such as IP addresses and device characteristics for security purposes, and records of communications through support channels. For clients utilizing our hosting services, we may process end-user data stored within client websites, though we do not control or monitor the collection practices of such data.

Purpose and Legal Basis for Processing

We process personal information only when we have proper justification under applicable laws. The primary legal bases for our processing activities include the necessity to fulfill contractual obligations to our clients, our legitimate business interests in maintaining and improving our services, and in limited cases, explicit consent for specific marketing communications. We maintain detailed records of processing activities to demonstrate compliance with legal requirements.

Use of Collected Information

The information we collect serves multiple business purposes. Primarily, we use this data to deliver and maintain reliable hosting services, including server provisioning, performance monitoring, and technical support. We also utilize information for business operations such as billing, customer relationship management, and service improvement initiatives. Security represents another critical use case, where we analyze data to detect and prevent fraudulent activity or unauthorized access to our systems.

Data Sharing and Third-Party Disclosures

We engage with carefully selected third-party service providers to support our operations, including cloud infrastructure providers, payment processors, and customer support platforms. These relationships are governed by strict contractual agreements that mandate appropriate data protection measures. We may disclose information when legally required to comply with court orders, government requests, or to protect our legal rights and the security of our services.

International Data Transfers

As a global service provider, we may transfer and process data in various locations worldwide. When transferring personal data originating from the European Economic Area or other regulated jurisdictions, we implement appropriate safeguards such as Standard Contractual Clauses and rely on adequacy decisions where applicable. Our subprocessors, including AWS Lightsail, maintain robust compliance certifications to ensure the protection of transferred data.

Data Retention Practices

We retain personal information only for as long as necessary to fulfill the purposes outlined in this policy. Client account information is typically maintained for five years following service termination to comply with legal and financial reporting obligations. Backup data associated with hosting services is automatically purged after thirty days, as specified in our Terms of Service. For data processed on behalf of clients, retention periods are determined by the respective client’s policies and instructions.

Security Measures

We implement comprehensive technical and organizational security measures to protect personal information against unauthorized access, alteration, or destruction. Our security program includes network encryption protocols, regular vulnerability assessments, strict access controls, and employee training on data protection best practices. We maintain incident response procedures to address potential security breaches and will notify affected parties where required by law.

Individual Rights

Individuals whose personal data we process may exercise certain rights under applicable privacy laws. These rights may include requesting access to their information, seeking correction of inaccurate data, requesting deletion under specific circumstances, and objecting to particular processing activities. We have established procedures to handle such requests in accordance with legal requirements, typically responding within thirty days of receipt. Requests should be submitted to our designated Data Protection Officer through the contact information provided in this policy.

Cookies and Tracking Technologies

Our website employs various technologies to enhance user experience and analyze site performance. Essential cookies are used for basic functionality and security purposes, while analytics cookies help us understand how visitors interact with our site. Marketing cookies are only deployed with explicit user consent. Visitors can manage cookie preferences through their browser settings or our cookie consent tool.

Policy Updates and Notifications

We periodically review and update this Privacy Policy to reflect changes in our practices or legal obligations. Material changes will be communicated to affected clients through email notifications at least thirty days prior to implementation. Continued use of our services following such notifications constitutes acceptance of the revised policy.

Contact Information

For questions or concerns regarding this Privacy Policy or our privacy practices, please contact our Data Protection Officer at info@westernmasshosting.com or by mail at:

Western Mass Hosting
22 Orlando. St.,
Feeding Hills, MA 01030.

We take all privacy-related inquiries seriously and will respond promptly to legitimate requests. For clients with specific data processing agreements, please reference your contract for any additional terms that may apply to our handling of your data.