Best Performance Upgrade for your Computer

Ortial Drive

Over time your computer will start to run slower than it was when you first bought it. Most people put it down to the number of files that are on the Hard Drive, Yes that can slowHDD Platters down the search of the files due to file indexing, however the main cause of slow down is the Hard Drive itself.


Up until recently all computers had mechanical drives fitted inside them. These drives used multiple disk platters one above each other. Each platter is like a record on a record plater. These platters are  spun at speed with a head that reads the data from them at speed. The more data that is on the drive the more time it takes to search for the data unless it is put in some kind of order.


The more common reason is that the Hard Drive has errors on the disk platters very much like a scratched record on a record player. When the Hard Disk has errors on it, it takes the head longer to read the data which causes the slow down of the whole computer.


The best performance upgrade for your computer is to replace the hard drive with a SSD (Solid State Drive). These types of drives have no moving parts so no heads or platters to damage which makes them a lot more durable for use in laptops. The technology used is very similar to how usb drives work.



Hamblett Consultancy – Hard Drive to SSD Replacement Service


This service is available to both Businesses and Residential customers within the Yorkshire area and can also be done both onsite or offsite depending what you require. This service includes:


  • Back up your data from the faulty / slow drive
  • Replace the current hard drive to an Ortial SSD
  • Install Windows 10 including latest updates
  • Transfer all your data back to your computer

** Programs can not be backed up and you will need re-installing afterwards **




256GB SSD                          £120      – Comes with a 12 Months Warranty

512GB SSD                          £140       – Comes with a 12 Months Warranty

1TB SSD                               £180       – Comes with a 12 Months Warranty


To book this service or for more information please Contact Me.

Setting up GSuite GMail Custom Domains With AWS Route53


Do you want to send emails from your custom domain hosted on AWS? There’s a few pitfalls that aren’t well documented.

The free, official “Check MX” tool will help you debug these issues, and you should use it, but it doesn’t have Route53 specific instructions.

1. Log in to AWS and go to Route53

Log in to your AWS management console and find the “Route 53” (direct link) product, which is Amazon’s nonsense name for DNS management. Then click on hosted zones.


2. Create the MX records

If you don’t have a domain name here, then your DNS isn’t managed by AWS, and this article is not right for you!

First the easy part:

  • Click on your domain
  • Then click “Go to Record Sets”
  • Then click “Create Record Set”
  • Leave the name blank
  • Change the type to “MX – Mail Exchange”


Change the TTL field to 3600.

Then in the “value” field, paste in exactly (this is the same for everyone):


Note: these values come from the official documentation, formatted here for Route53’s syntax. If you want, you can verify the hosts. They aren’t likely to change.

3. You’re Done! Unless…

This is the basic setep you need to send emails with DNS in Route53. However, Google suggests you verify your domain with some more security steps. The previously mentioned “Check MX” tool will complain if you stop here. You should verify your bananas!

4. Add a “SPF” text entry

Create a new TXT entry with no name:

SPF Record

For the value, paste in exactly (with quotes):

"v=spf1 ~all"

Then click “Create”. I don’t know or care what this is, but it’s documented here if you’re curious.

If you already have a TXT record with no name and Route53 errors, then put the above line in the existing TXT record, with quotes, on a new line, and save it.

5. Create the “domain key” / DKIM record

Google’s tools and interface are often nightmarish and poorly documented, so I’m including some screenshots.

Log in to your Google Suite admin console using your Google Suite admin account:

Navigate the maze: Apps > G Suite > Gmail > Authenticate Email.

Google Authenticated Email

Now click “Generate new record”. Don’t click anything else yet.

Back in Route53, create a new, named TXT record. For the name, paste in the name from your generated record in GSuite. It’s probably “google._domainkey“. Change the type to “TXT – Text”:

Dkim Key

Now for the tricky part. Google tells you to paste in the whole TXT record value from GSuite admin, but if you do, you’ll get the error:

CharacterStringTooLong (Value is too long) encountered with '"v=DKIM1;...  

The solution to this is to chop up your value into multiple quoted strings (not new lines), with a maximum of 255 characters in each string, and a space between each chunk. It doesn’t have to be equal chopping.

For example, if your value looks something like:

"v=DKIM1; k=rsa; p=abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyza bcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabc"

You can chop it up at arbitrary places:

"v=DKIM1; k=rsa; p=abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz" "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzab" "cdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabc"

Note those are single spaces, not newlines, between each chunk!

Paste the chopped up value (including all quote marks on all lines) into the value and create your TXT record.

Then, when Google gets off its lazy behind and fetches your new DNS records, you can click the “START AUTHENTICATION” button on the GSuite admin page. It should be pretty fast, and you can tell it has started when you see:

Authenticated Email

Don’t worry if it complains about your DNS not updating, you can click “START AUTHENTICATION” as many times as you want!

7. Troubleshooting?

The Check MX tool usually gives good output and instructions. If you want to verify you set up your TXT and MX records correctly, you can try this from the command line.

Verify the domain SPF:

$ dig -t TXT

;            IN  TXT

;; ANSWER SECTION:        300 IN  TXT "v=spf1 ~all"

Verify the domain key (if you named it, replace _domainkey):

$ dig -t TXT

;            IN  TXT

;; ANSWER SECTION:    300 IN  TXT "v=DKIM1\; k=rsa\; p=...

8. That’s It!


Taken from