If you’re a small business owner who has only had one web site hosting company, chances are you don’t know the potential issues involved with making the switch. But everyone has moved from one residence to another at some point. When you look at switching web hosting packages through the familiar lens of moving from one apartment to another, making a hosting move is much easier to understand.

Browsing the Classifieds…Or Searching the Web

Whether you’re looking for a new place to live or a new place for your business to live online, you’ll want to do some shopping and research. Looking for a new apartment, you might browse classified ads or drive around the areas you want to live looking out for "For Lease" signs. You’ll also probably ask for advice on which areas are desired and which are best avoided. Do the same when looking for a web host: search online, read reviews, contact people you trust to see the hosting service they use. Don’t just blindly listen to a salesperson…that’s how you end up with leaky pipes or a not-so-secure web host.

Also, moving because your site takes up too much space for your current hosting package, is a lot like upgrading from an efficiency to a roomy two-bedroom. You’ll want to check for storage…or bandwidth. Avoid automatically opting for what’s cheapest…remember those leaky pipes?

Back Up Before You Pack Up

Before moving your website, be sure to back up the entirety of your website to guard against losing anything in transition. If you used movers to transport that antique dining room set, you’d get insurance, right?

Keep Your Info at Hand

Before making the move from one web site hosting provider to another, record security settings, email boxes, and software and configuration information. Think about it like labeling boxes filled with kitchen supplies, linens, or your prized collection of Frank Sinatra vinyl sides. It makes the unpacking much easier once the move is complete if everything is labeled and in the right place.

Remember Those Change of Address Forms

When you make a move, you fill out change of address information for all of your important bills (yeah, it’s tempting to leave those behind, but it’ll come back to bite you in the end), right? Likewise, when moving to new web hosting, you need to update your domain name information with the name server information used by your new web hosting company. Once a change has been initiated, it can take up to two days for DNS servers to learn that your website now lives on a different server-just like that birthday gift from Aunt Edna that went to your old address and took a while to show up at the new one.

Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility.

On Friday, the Internet’s addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16.

The move comes after years of technical testing and policy development, said the Internet Corporation for Assigned Names and Numbers (ICANN), which held a meeting in Seoul this week.

Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language. ccTLDs are those that have a two-letter country designation at the end of a domain name.

In reality, the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure. The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.

One of the primary concerns with implementing IDNs is the security and stability of the Domain Name System (DNS). That system enables the translation of domain names written with characters and digits into IP (Internet Protocol) addresses, which can then be queried by a Web browser.

ICANN said it would initially allow for a "limited" number of IDNs, which are subject to ICANN’s approval and stability testing. Still, there are likely to be hiccups, ICANN warned.

"The usability of IDNs may be limited, as not all application software is capable of working with IDNs," ICANN said in a59-page proposal dated Sept. 30 that describes the Fast Track process. "It is up to each application developer to decide whether or not they wish to support IDNs. This can include, for example, browsers, email clients, and sites where you sign up for a service or purchase a product and in that process need to enter an e-mail address."

ICANN has set some language restrictions for IDNs: they must be in an official language of a country or territory and have legal status or at minimum "serve as a language of administration."

According to the proposal, ICANN will charge registries US$26,000 for an evaluation processing fee, which can be paid in the local currency. ICANN would also like an annual contribution fee of 3 percent of a registries revenue, which can be as low as 1 percent for low-volume registries. For both fees, registries can request a fee waiver, ICANN said.

Dear Pelanggan,

Untuk memperlancar akses ke domain pelanggan, mulai pertanggal 18 Desember 2010, kami telah menambah satu dns tambahan. Hal tersebut akan sangat berguna apabila salah satu DNS mengalami gangguan baik dari sisi server maupun Network

Total DNS yang kami miliki saat ini ada 3 dengan lokasi / network berbeda yaitu :

domain01.anyoneserver.com (117.102.253.226), domain02.anyoneserver.com (119.110.82.162), domain03.anyoneserver.com (203.79.29.226).

Bagi pelanggan dan reseller yang memegang penuh atas domainnya, disarankan untuk mengupdate ip dari nameservernya.

Terima kasih

Q:
Saya tertarik dengan program combo reseller dan saya ingin bertanya lebih detil bagaimana nanti saya dapat mengelola semua account pada reseller saya.

A:
Caranya mudah, misal domain yang anda gunakan adalah website.com. Kami akan membuatkan account untuk domain website.com pada server reseller (yang khusus kami gunakan untuk domain reseller). Pada server ini anda hanya mendapatkan akses cPanel tanpa WHM.
Setelah itu kami akan membuatkan Anda account reseller pada 3 server kami, misal dengan menggunakan nama jakarta.website.com (untuk server Indonesia – IIX – OpenIXP) kemudian seattle.website.com (untuk server Internasional yang terletak di Seattle US) dan satu lagi dallas.website.com (untuk server Internasional yang terletak di Dallas US). pada jakarta, seattle dan dallas Anda hanya memiliki WHM untuk mengelola paket, dan pelanggan yang menggunakan jasa Anda.

Q:
Bagaimana dengan nameserver ? apakah setiap server memiliki nameserver tersendiri ?

A:
Kami menggunakan 3 server dns terpisah yang terletak di 3 benua berbeda yaitu Amerika, Eropa dan Asia. Dimanapun letak pelanggan Anda, Dns server yang digunakan tetap sama.

Incoming search terms:

If you’d like to setup your domain to accept anything.domain.com, you can do so with the following guide (Admin access required)
1) Setup the dns with a wildcard A record. Go to Dns Control, and add an "A" record:
* -> 1.2.3.4
where 1.2.3.4 is the IP of your domain.
This will allow anything.domain.com to resolve to your server. Apache does not yet know how to direct that name though.
2) To setup apache, go to:
Admin Level -> Custom Httpd configurations -> domain.com
In the top text area, add this *one* line:

ServerAlias *.|DOMAIN|

then click "Save".
That should be it. Wait a few minutes for everything (apache, named) to be restarted then test it out.
The wildcard subdomains will point to your main public_html directory for the domain.
If you want to change this, it’s probably best not to do step 2, and to setup your own custom virtualhost manually into the /etc/httpd/conf/httpd.conf (DA wont delete/overwrite it there) with the same ServerAlias directive as in step 2.
Other similar uses might be subdomain aliasing, where test.domain.com is the same as test.domain2.com.
You can accomplish this by following step 1) above, then insert the following instead of step 2) above:

|*if SUB|
    ServerAlias |SUB|.domain2.com
|*endif|

which will make any existing subdomain from domain2.com point to domain.com.

Incoming search terms: