One place for hosting & domains


      How to Transfer Your Domain Registration to DreamHost (4 Steps)

      So you’ve got a website. Or maybe you juggle multiple websites and domain names. Perhaps you’re unsatisfied with your current registrar, or you’ve found you’re managing too many different things in too many different places.

      If so, it might be time to consider transferring your domain registration. And you might want to consider transferring it to DreamHost.

      Wondering How to Move a Domain Name to a New Host?

      We can help! Subscribe to our monthly newsletter and get domain insights directly in your inbox.

      Why You Should Consider Transferring Your Domain to DreamHost

      1. You Want to Manage Everything in One Place 

      A while back, we surveyed some of our customers, and they told us the No. 1 benefit of using DreamHost was that it gave them the ability to manage as much as possible in one place. 

      More specifically, 60% of customers we asked said the main benefit of using DreamHost was the ability to manage several websites and domains from a single location

      So if you are running several websites under several different registrars, moving them all to one place would make life a whole lot easier.

      2. You’re Being Charged Too Much for Renewals 

      Like any service, prices vary, and those costs can increase when it’s time to renew. If you feel you’re being charged too much for domain registration renewals, the obvious solution is to change registrars.

      3. Support is Lacking 

      As with price, the support offered by different service providers varies a lot. If you’re not getting the help you need from your current registrar, it may be worth moving to one that can fill the gap (like DreamHost). 

      4. You’d Like to Move a Domain from One DreamHost Account to Another

      If you run many websites, there’s always a chance you’re going to be taking over a domain owned by someone using DreamHost. Should this happen, we allow you to transfer domain ownership from one person to another quickly and with minimal effort. 

      In this situation, the easiest solution is just to continue using DreamHost (and potentially move your other domains over too).

      Need-to-Knows When Transferring a Domain

      Understanding what is and isn’t possible when transferring domains can save you tons of time further down the line and help ensure a smooth and pain-free domain transfer. 

      With that in mind, here are a few things you need to know before you start the process of transferring a domain registration.

      1. Only Certain TLDs Are Allowed

      At DreamHost, we support certain TLDs for transfer. However, it’s actually only a handful of TLDs that cannot be transferred. These are: .AM, .AT, .BZ, .FM, .JP, .NET.NZ, .ORG.NZ, .NGO, .ONG, .OOO, and .WS. 

      For more information, you can check out DreamHost’s TLD page for a current list of domain extensions with pricing.

      Additionally, there are also some New TLDs and ccTLDs which are considered premium domains — for example, .LIVE, .ME, and others. DreamHost cannot accept transferring premium domains due to the pricing structures that vary from one registrar to another. 

      If you’d like to use a premium domain for your website, you’ll need to register it directly with Enom or another registrar that sells premium domains. Then you can host the site on your DreamHost account like any other domain. 

      2. Beware of the ICANN 60-day Transfer Lock

      Did you know you can’t transfer your domain during the first 60 days of registration? You need to wait until day 61.

      It’s also worth remembering that you cannot transfer a domain if your last transfer took place within the previous 60 days.

      And remember, transferring a registration only moves your domain. If you’d like to transfer your web hosting service to DreamHost, we can help with that too.

      3. Downtime Can Happen If You Don’t Get Your Nameservers Sorted First

      It’s important to know that if you decide to change your nameservers to DreamHost after completing a transfer, you may experience some downtime. Changes to the nameservers cannot be made while the domain is pending transfer. 

      We recommend that you start the transfer at least a month in advance — this will make sure your domain registration does not expire during the transfer. 

      What Should You Do Before You Request a Domain Transfer?

      We recommend completing three super simple steps before you make your transfer request. This is because of ICANN’s Transfer Policy, which means that following a transfer, changes made to the registrant’s name, organization, or email address will be put on a 60-day lock

      1. Unlock the domain registration. This is done with your current registrar.
      2. Obtain the auth code, also known as the EPP. You can get this from your current registrar.
      3. Remove WHOIS privacy. This is done through your current registrar. This allows your new registrar to recognize the new owner.

      Now you’ve completed all the preparation, it’s time to transfer your domain to DreamHost. The whole process is pretty simple, but just to be sure, here’s what you need to do. 

      How to Transfer Your Domain to DreamHost in 4 Steps

      Four steps — it’s that easy! Let’s walk you through the process of transferring your domain to DreamHost.

      1. Request the Transfer-In With Dreamhost

      Start by logging in to your DreamHost account. You can do that here. If you don’t have an account yet, you can create one here

      From there, you are going to need to navigate to the Reg Transfer page. There you will find a button labeled Start Transfer to DreamHost — click that. 

      DreamHost’s list of info for what you need to know before starting a domain transfer.

      Have you done that? Cool. You should now see this:

      Requesting a domain transfer in the DreamHost panel. 

      In this section, all you need to do is add the domain(s) you would like to transfer to DreamHost and click Request Transfer

      2. Enter your Auth Code, WHOIS Info, and Nameservers

      Now you need to fill in details to show you are the owner of that domain(s). If you want your contact details to stay hidden, just tick the I want all my contact information private button.

      This is free, by the way. We don’t like unnecessary charges!

      Checkbox for making WHOIS contact info private

      You should now see a section asking you to enter all your WHOIS information. As you might suspect, you need to make sure all your details are valid and correct and that you have followed the ICANN policy we mentioned earlier.

      The WHOIS section looks like this:

      Empty WHOIS information fields to be filled out.

      See that little checkbox at the top? If you click that, it will use these details to automatically fill in the four contact fields on the domain registration’s internal ownership details. These are:

      • Admin
      • Billing
      • Registrant
      • Technical details

      The following section is the Auth Code field.

      Your current registrar should have provided you with either an Auth Code or EPP code. Make sure you fill in the fields with the code exactly as provided to you.

      Once that’s done, you should see the following:

      Filling out nameserver information with the “Use another host’s nameservers” option clicked.

      Choose either Use DreamHost’s nameservers (this automatically sets DreamHost’s nameservers for you) or Use another host’s nameservers (you should choose this if you’d like to enter outside name servers manually). 

      Make sure you have read the Registration’s Terms, and click Continue

      You now need to pay for the transfer. 

      3. Pay for Your Domain Transfer

      If you have a free domain registration with your current registrar, you won’t be charged by DreamHost. If you don’t have a free domain registration, you will need to pay for it here. 

      To complete this step, you first need to review your order. 

      Reviewing order total for ‘Transfer + 1 year registration’

      If you need to pay for the transfer, you will know because the fee will appear in the Order Summary. 

      Click the Proceed to Payment Entry button. You then need to confirm the payment, so press the Submit Transfer Request button. 

      Notification showing ‘Transfer Initiated’ submitted and next steps. 

      On the next screen, you simply need to enter your payment details and click the confirmation button. You should now see that the transfer has been initiated.

      Notification showing ‘Transfer Initiated’ submitted and next steps.

      Navigate to the Reg Transfer page, and if all is well, you will be able to see confirmation that the transfer is pending. 

      Example of a pending transfer in the DreamHost panel. 

      When the transfer has completed, payment will be taken from your bank account. 

      Let’s move on to the last step. 

      4. Check That the Domain Status and EPP Code Are Verified, and Transfer Request Is Submitted to the Current Registrar

      Once the transfer is completed, the authorization code and EPP are verified with your current registrar. 

      The registrar then has five days to release the domain to DreamHost, and the transfer will complete within the seven days after. 

      You can confirm the status by running a quick WHOIS check. If the transfer fails, you can get more help by contacting our support team

      There you go — four simple steps as promised!

      That said, there are little things that can go wrong. Let’s discuss some of the most common domain transfer problems our team here at DreamHost comes across and how they can be fixed without needing to contact support. 

      Ready to Switch Your Domain Registrar?

      Search DreamHost’s 400+ TLDs to find the perfect URL for your website.

      3 Common Domain Transfer Issues

      While the steps involved in transferring a domain are simple, that doesn’t guarantee everything will run without a hitch. There are several factors involved, and if you have issues, it could be for one of the following reasons. 

      1. Some domains update their auth code internally. For example, the .org registry has many security measures and can often change EPP codes automatically. If you see this happening, you need to contact your current registrar. You’ll then need to reset the auth code and resubmit the domain transfer request. 
      2. Some domains are transfer locked. You can establish whether this is an issue by looking at the WHOIS information and checking for the following: Domain Status: clientTransferProhibited. If you see this, you’ll have to contact your current registrar to have it unlocked. Once that’s done, you then need to resubmit the domain transfer in DreamHost.
      3. Intermittent issues with the DNS. After a transfer, you may see this issue. This is usually down to domains having previously used DNSSEC. Find out how to fix it in this article. 

      Still running into issues? Check our Knowledge Base or contact support.

      Master Your Domain at DreamHost

      It’s not uncommon for website owners to start with one domain registrar and later move to another. Over time many of us realize we rushed the initial registration process, didn’t do due research, and wound up being charged too much for too little.

      If this includes you, moving your domain registration — to DreamHost or any other registrar — is much simpler than you might at first think.

      In short, you simply need to:

      1. Request the Transfer-In with DreamHost (or your chosen registrar)
      2. Enter the auth code, WHOIS, and nameservers 
      3. Pay for your transfer 
      4. Wait for your domain status and EPP code to be verified and for your transfer request to be submitted to your current 

      If you’d like to register a new domain, we can help with that too! DreamHost .COM domains cost $7.99 a year and come with free, private registration, while other domains start from less than $1/year. Find out more here.

      Source link

      How To Transfer DigitalOcean Spaces Between Regions Using Rclone


      DigitalOcean Spaces is an object storage service designed to make it easy and cost effective to store and serve large amounts of data.

      In this guide, we will cover how to migrate data between Spaces regions, by using Rclone to transfer data between two Spaces. We will demonstrate how to install Rclone, the configuration settings needed to access multiple regions, and the commands that you can use to synchronize your files between regions and verify their integrity.

      Creating API Keys and Finding Spaces Endpoint Information

      Before we begin installing and configuring Rclone to copy our objects between Spaces, we will need some information about our DigitalOcean Spaces account. We will need a Spaces API key, and we will need to know the regions and names of our source and destination Spaces.

      Generating a DigitalOcean Spaces API Key

      To create a DigitalOcean Spaces API key, follow the “Creating an Access Key” section of our How To Create a DigitalOcean Space API Key documentation.

      Save the access key ID and the secret key. We will use them later to configure Rclone to access our account.

      Finding the Spaces S3-Compatible Endpoint

      Next, we need to find the endpoint for each Space. You can view the Space’s endpoint within the DigitalOcean Control Panel by selecting the Space and viewing the Settings tab:

      DigitalOcean Spaces endpoint

      The endpoint will always be the region you created the Space in, followed by Make note of the endpoint for both of your Spaces. Will we use this information when creating our rclone configuration.

      Installing Rclone

      You’re now ready to install Rclone. You can do this on your local machine, or – if you are bandwidth limited – you may want to install Rclone on a Droplet located in the source or destination Spaces region.

      Visit the Downloads section of the project’s website to find binaries of the utility compiled for different platforms. Download the zipped binary that matches your computer’s operating system to get started.

      Once you have the Rclone zip file downloaded to your computer, follow the section below that matches your platform.


      Before we can extract the archive, we will need to ensure that the unzip utility is available.

      If you are running Ubuntu or Debian, you can update the local package index and install unzip by typing:

      • sudo apt update
      • sudo apt install unzip

      If you are running CentOS or Fedora, you can install unzip by typing:

      With unzip installed, navigate to the directory where you downloaded the rclone zip file:

      Next, unzip the archive and move into the newly created directory:

      • unzip rclone*
      • cd rclone-v*

      From here, we can copy the binary to the /usr/local/bin directory so that it is available system-wide:

      • sudo cp rclone /usr/local/bin

      Next, we add the manual page to our system, so that we can easily get help on the command syntax and available options. Make sure that the local manual directory is available and then copy the rclone.1 file:

      • sudo mkdir -p /usr/local/share/man/man1
      • sudo cp rclone.1 /usr/local/share/man/man1

      Then update the man database to add the new manual page to the system:

      Finally, we can create the Rclone configuration directory and open up a configuration file:

      • mkdir -p ~/.config/rclone
      • nano ~/.config/rclone/rclone.conf

      This will open your text editor with a new blank file. Skip ahead to the section on Configuring Rclone to continue.


      If you are running macOS, begin by navigating in the terminal to the directory where you downloaded the rclone zip file:

      Next, unzip the file and move into the newly created directory:

      • unzip -a rclone*
      • cd rclone-v*

      Next, make sure the /usr/local/bin directory is available and then copy the rclone binary to it:

      • sudo mkdir -p /usr/local/bin
      • sudo cp rclone /usr/local/bin

      Finally, we can create the configuration directory and open up a configuration file:

      • mkdir -p ~/.config/rclone
      • nano ~/.config/rclone/rclone.conf

      This will open up your text editor with a new blank file. Skip ahead to the section on Configuring Rclone to continue.


      If you are running Windows, begin by navigating to the Downloads directory in the Windows File Explorer. Select the rclone zip file and right-click. In the context menu that appears, click Extract All…:

      Windows extract rclone zip file

      Follow the prompts to extract the files from the zip archive.

      The rclone.exe utility must be run from the command line. Open a new Command Prompt (the cmd.exe program) window by clicking the Windows button in the lower-left corner, typing cmd, and selecting Command Prompt.

      Inside, navigate to the rclone path you extracted by typing:

      • cd "%HOMEPATH%Downloadsrclone*rclone*"

      List the directory contents to verify that you are in the correct location:


      10/23/2017 01:02 PM <DIR> . 10/23/2017 01:02 PM <DIR> .. 10/23/2017 01:02 PM 17 git-log.txt 10/23/2017 01:02 PM 296,086 rclone.1 10/23/2017 01:02 PM 16,840,192 rclone.exe 10/23/2017 01:02 PM 315,539 README.html 10/23/2017 01:02 PM 261,497 README.txt 5 File(s) 17,713,331 bytes 2 Dir(s) 183,296,266,240 bytes free

      You will need to be in this directory whenever you want to use the rclone.exe command.

      Note: On macOS and Linux, we run the tool by typing rclone, but on Windows, the command is called rclone.exe. Throughout the rest of this guide, we will be providing commands as rclone, so be sure to substitute rclone.exe each time when running on Windows.

      Next, we can create the configuration directory and open up a configuration file to define our S3 and Spaces credentials:

      • mkdir "%HOMEPATH%.configrclone"
      • notepad "%HOMEPATH%.configrclonerclone.conf"

      This will open up your text editor with a new blank file. Continue ahead to learn how to define your Spaces regions in the configuration file.

      Configuring Rclone

      We will configure our two DigitalOcean Spaces regions as Rclone “remotes” in the Rclone configuration file. Paste the following section in the configuration file to define the first region:


      type = s3
      env_auth = false
      access_key_id = your_spaces_access_key
      secret_access_key = your_spaces_secret_key
      endpoint =
      acl = private

      Here, we define a new rclone “remote” named spaces-sfo2. Change the region name to match the Spaces region you are configuring.

      We set the type to s3 so that rclone knows the appropriate way to interact with and manage the remote storage resource. We will define the Spaces access credentials in this configuration file, so we can set env_auth to false.

      Next, we set the access_key_id and secret_access_key variables to our Spaces access key and secret key, respectively. Be sure to change the values to the credentials associated with your account.

      We set the endpoint to the Spaces endpoint we looked up earlier.

      Finally, we set the acl to private to protect our assets until we want to share them.

      Next, make a duplicate of the configuration block you just created, then update the name and endpoint region to reflect your second region:


      . . .
      type = s3
      env_auth = false
      access_key_id = your_spaces_access_key
      secret_access_key = your_spaces_secret_key
      endpoint =
      acl = private

      The rest of the configuration should remain the same as for the first region. Save and close the file when you are finished.

      On macOS and Linux, be sure to lock down the permissions of the configuration file since our credentials are inside:

      • chmod 600 ~/.config/rclone/rclone.conf

      On Windows, permissions are denied to non-administrative users unless explicitly granted, so we shouldn’t need to adjust access manually.

      Next, we’ll use rclone to explore our Spaces and sync data between them.

      Copying Objects from S3 to Spaces

      Now that our configuration is complete, we are ready to transfer our files.

      Begin by checking the rclone configured remotes:


      spaces-nyc3: spaces-sfo2:

      Both of the regions we defined are displayed.

      We can view the available Spaces by asking rclone to list the “directories” associated with the remotes (make sure to add the colon to the end of the remote name):


      -1 2019-09-23 13:07:54 -1 source-space

      The above output indicates that one Space, called source-space was found in the sfo2 region.

      You can repeat the procedure to view the other region:


      -1 2019-09-23 13:08:28 -1 destination-space

      To view the contents of a Space, you can use the tree command. Pass in the remote name, followed by a colon and the name of the “directory” you wish to list (the Space name):

      • rclone tree spaces-sfo2:source-space


      / ├── Photos │ ├── 2019.01.24-23.10.27.png │ ├── 2019.01.24-23.11.39.png │ ├── 2019.01.24-23.18.00.png │ ├── 2019.01.24-23.18.18.png │ ├── 2019.01.24-23.18.30.png │ ├── 2019.01.24-23.19.32.png │ ├── 2019.01.24-23.23.06.png │ ├── 2019.01.24-23.23.53.png │ ├── 2019.01.24-23.25.14.png │ ├── 2019.01.24-23.26.22.png │ ├── 2019.01.25-12.43.35.png │ ├── 2019.03.13-14.35.34.png │ └── 2019.03.13-14.40.52.png └── 1 directories, 14 files

      When you are ready, you can copy the files between Spaces by typing:

      • rclone sync spaces-sfo2:source-space spaces-nyc3:destination-space

      Assuming everything went well, rclone will begin copying objects between the two Spaces.

      Note: If you hadn’t previously created the destination Space in the specified region, rclone will attempt to create one for you with the given name. This will fail if the name provided is already being used by another account or if the name doesn’t meet the naming requirements for DigitalOcean Spaces (lowercase letters, numbers, and dashes only).

      When the transfer is complete, you can check that the objects have transferred by viewing them with the tree subcommand:

      • rclone tree spaces-nyc3:destination-space


      / ├── Photos │ ├── 2019.01.24-23.10.27.png │ ├── 2019.01.24-23.11.39.png │ ├── 2019.01.24-23.18.00.png │ ├── 2019.01.24-23.18.18.png │ ├── 2019.01.24-23.18.30.png │ ├── 2019.01.24-23.19.32.png │ ├── 2019.01.24-23.23.06.png │ ├── 2019.01.24-23.23.53.png │ ├── 2019.01.24-23.25.14.png │ ├── 2019.01.24-23.26.22.png │ ├── 2019.01.25-12.43.35.png │ ├── 2019.03.13-14.35.34.png │ └── 2019.03.13-14.40.52.png └── 1 directories, 14 files

      For more robust verification, use the check subcommand to compare the objects in both regions:

      • rclone check spaces-sfo2:source-space spaces-nyc3:destination-space


      2019/09/23 14:29:11 NOTICE: S3 bucket destination-space: 0 differences found 2019/09/23 14:29:11 NOTICE: S3 bucket destination-space: 14 matching files

      This will compare the hash values of each object in both remotes. You may receive a message indicating that some hashes could not be compared. In that case, you can rerun the command with the --size-only flag (which just compares based on file size) or the --download flag (which downloads each object from both remotes to compare locally) to verify the transfer integrity.


      In this guide, we’ve covered how to transfer objects between two DigitalOcean Spaces regions. We gathered API credentials and endpoint information from the Spaces service, installed and configured the rclone utility on our local computer, and then copied all objects from a source Space to a destination Space.

      The rclone client can be used for many other object storage management tasks including uploading or downloading files, mounting Spaces on the local filesystem, and creating or deleting additional Spaces. Check out the man page to learn more about the functionality the tool provides.

      Source link

      Network Transfer Quota

      Updated by Linode

      Contributed by


      Use promo code DOCS10 for $10 credit on a new account.

      Your network transfer quota represents the total monthly amount of traffic your services can use as part of your Linode plans’ basic pricing. Each Linode plan includes a specified amount of transfer. Transfer amounts are listed for each plan on the Linode pricing page.

      Network Transfer Pool

      Your monthly network transfer quota for your services is for your entire account, not for any individual Linode. The transfer amounts provided by all of your Linodes’ plans are added together, and your account’s monthly quota is equal to the total. This is also referred to as your network transfer pool. Each of your Linodes is able to use bandwidth from this pool.

      If an individual Linode’s traffic exceeds the network transfer amount specified by its plan, but the total transfer used between all of your Linodes is still less than your pool total, then you will not be charged overages.

      Linodes from different data centers all use the same transfer pool.

      Network Transfer Pool Example

      If you have two Linodes:

      • Linode A, which comes with 1TB transfer
      • Linode B, which comes with 2TB transfer

      Your monthly pool total, or your account’s quota, would be 3TB. If Linode A uses 1.5TB of traffic during the month, and Linode B uses 1TB of traffic, then the total used between them is 2.5TB. The 1.5TB used by Linode A is greater than the 1TB of transfer specified by its plan, but the 2.5TB total is less than the account quota, so no overages are billed.

      Which Traffic Applies to the Transfer Quota

      The transfer quota only considers traffic on your Linodes’ public addresses. Traffic over the private network does not count against your monthly quota.

      All inbound traffic to your Linodes is free and will not count against your quota–only traffic that your Linodes emit on their public addresses is counted.

      Transfer Resets, Proration, and Overages

      Your transfer quota is reset at the beginning of each month.

      Why is My Linode’s Network Transfer less than My Plan’s Transfer?

      Your account’s transfer quota is prorated based on your Linodes’ creation and deletion dates.

      A Linode you create mid-month will include a lower transfer amount than what’s listed on the pricing page, depending on how much time remains in the month.

      For example, if you create a Linode half-way through the month, it will come with half of the transfer listed for your Linode’s plan. Because your transfer quota is reset at the beginning of the next month, and you will see the full transfer amount at that time.

      If you remove a Linode before the end of the month, then the transfer it contributes to your pool will also be reduced according to the date the Linode was deleted.

      For example, if you create a Linode on the first of the month, then your pool will initially include the full transfer amount for that Linode’s plan. If you remove that Linode half-way through the month, then your pool total will be updated and reduced by half the Linode plan’s transfer.

      How Overages Work

      If you use all available bandwidth in your network transfer pool, you can continue to use your Linodes normally, but you will be charged $0.02 for each additional GB at the end of your billing cycle.

      How to Mitigate Overages

      If you have gone over your quota, or you think you may before the end of the month, you can consider one of the following options to raise your pool total and avoid overages:

      1. Increase the size of an existing Linode to access more monthly transfer bandwidth.

      2. Purchase (an) additional Linode(s) with the specific purpose of increasing your pool total. You may want to delete any Linodes created for this purpose at the end of the month if you don’t anticipate needing a higher pool total in the future.

      When taking one of these actions, keep in mind that the quota amount that will be added is prorated according to the current date.

      View Network Pool Usage

      Linode recommends that you monitor your network pool usage throughout the month. You can check your network usage for your current billing cycle via the Linode Manager or the Linode CLI.

      Linode Manager

      1. Log in to the Linode Manager and view your Linode Dashboard.

      2. Under the This Month’s Network Transfer Pool heading, a graphic displays (in GB) the transfer used, the unused pool amount remaining, and your account’s quota for the month.

      Linode CLI

      • To view your network utilization (in GB) for the current month, issue the following command:

        linode-cli account transfer


        You will need to generate a Personal Access Token and install the Linode CLI before being able to use the CLI. See the Linode CLI guide for more information.

      More Information

      Read the Billing and Payments guide for an overview of Linode billing.

      Join our Community

      Find answers, ask questions, and help others.

      This guide is published under a CC BY-ND 4.0 license.

      Source link