I'm transferring my Web hosting service to Tiger Technologies. Can I update the DNS nameservers myself?

When you transfer your Web hosting service to Tiger Technologies, we normally handle the technical aspect of "updating the DNS nameservers" (doing so "points" your domain name at our servers). You won't usually need to do this yourself.

However, we can only make that change after the domain name has been transferred to our company. In some cases, you may want to update the DNS nameservers yourself:

  • If you prefer that we don't transfer the domain name to Tiger Technologies.
  • If your domain name has been registered for less than 60 days and can't yet be transferred.
  • If your domain name isn't one of the normal types we can transfer.
  • If you're a technically advanced user who wants to speed up the Web hosting and e-mail transfer process.

If so, you can update the DNS nameservers at the old domain name registration company (don't do this until after you have signed up with us, published your files to our Web servers, and set up any e-mail accounts you want to use).

Just use these settings:

  • Primary DNS Server: ns1.tigertech.net
  • Secondary DNS Server: ns2.tigertech.biz
  • Third DNS Server: ns3.tigertech.org

Most visitors to your Web site (and people sending you e-mail) will start reaching our servers as soon as you make this change, and everyone will be reaching our servers within 72 hours.

Need help?

If you aren't sure how to make these changes at your old domain name registration company, but you're willing to tell us your username and password at that company, we'll be glad to make these changes for you. Just contact us and let us know the details.

Why do the nameservers end in .net, .biz and .org?

Technically advanced users occasionally ask why our nameservers use three different "top level domain names". There's a simple reason: it increases reliability by eliminating a single point of failure.

We're surprised to see other Web hosting companies handling many thousands of customers with nameservers that end in a single domain name (such as ns1.example.net and ns2.example.net). A problem with that domain name can cut off access to every Web site that uses it for DNS service.

Using different domain names prevents this problem. For example, even if the central registry accidentally deleted "tigertech.net" from the Internet, the ns2.tigertech.biz and ns3.tigertech.org nameservers would continue to work, and your Web site would continue to be available.

It's admittedly unlikely that something like that will ever happen, but avoiding the risk by using different domain names is so easy that it clearly makes sense to do it.

By the way, we intentionally chose ".net", ".biz" and ".org" because the central registries for each of those are run by three independent companies.