I'm transferring my service to Tiger Technologies. Can I update the DNS nameservers myself?
When you transfer your hosting service to Tiger Technologies, we normally handle the technical aspect of "updating the DNS nameservers" (doing so "points" the website and email service for 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 (you can choose this option on our order form).
- 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 email 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 email 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|
If they only ask for two nameservers, it's okay to just tell them the "primary" and "secondary".
Most visitors to your website and people sending you email will start reaching our servers as soon as you make this change, and everyone will be reaching our servers within 72 hours.
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 hosting companies handling millions of customers with nameservers that end in a single domain name, like “ns1.example.net” and “ns2.example.net”. A problem with “example.net” can cut off access to every 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, making “ns1.tigertech.net” stop working, our “ns2.tigertech.biz” and “ns3.tigertech.org” nameservers would continue to work, and your 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. If Microsoft did this, for example, it wouldn’t have caused an outage for millions of customers when they forgot to renew a domain name that Hotmail relies on. Twice.
By the way, we intentionally chose “.net”, “.biz” and “.org” because the central registries for each of those are run by three independent companies that are unlikely to have the same problem at the same time.
Can I use another company's nameservers and have my website with Tiger Technologies?
We don't officially support or recommend that configuration. If your site is using our Web servers, your domain name should also use our DNS nameservers.
That's because the IP address associated with your site can change without notice (it’s not a static IP address), which would eventually stop working if you enter it into another company’s nameservers. The IP address won't change often — it might be years from now — but it will almost certainly happen at some point as we add new servers and make other changes to our network.
The idea that we handle the DNS nameservers for websites we host is woven into our system (including our support Web pages) in other subtle ways, too.
In short: if you did this, your service with us would be unreliable and you'd probably have problems. We wouldn't buy service from anyone under those conditions, so we don't think we should sell it under those conditions, either.
This problem is not unique to our company, by the way. You’ll have the same problem if you hard-code any IP address that you don’t control into another company’s nameservers. We don’t know of any hosting company that guarantees the IP address that your site is on will never change; we just try to do a better job of warning customers of this problem up front.
If you're asking this question because you want to add custom DNS records (such as MX records or subdomains pointed at other servers), we include that feature at no extra charge. Our "DNS Editing" page has the details.