Typically the transfer should be completed within about 48 to 72 hours. You may want to check with your registrar to see exactly how long it should take to complete the transfer.

Back to top

If you want to transfer your registration from your current registrar to Iboza.com, you can request a transfer of your domain name using our domain checker on our website.

If you are leaving your registration with your current registrar but want to move your domain to Iboza.com and use our webhosting services, you will need to change your current nameserver information to our information. Log in to your registrar's site using the user name and password they provided you and change your current nameserver information to our nameserver information. The costs for a dns entry are $19.95/year.

Back to top

Once you have decided on a domain name and have checked that it is available, we can register your new domain name for you. You can register a domain name through our website. The domain name propagation process normally requires 48 to 72 hours.

Of course, you can always take care of the registration process yourself by working directly with an another domain name registrar and then transferring the domain name to Iboza.com.

Back to top

You have a number of different options. If you think you may want to get your site up and running in the near future, you can go ahead and register your name and sign up for a hosting plan now. You will receive a parking page that all your site's visitors will see until you are ready to publish your site. If you think it may be a while before you are ready to publish your site, or if you want to reserve your name "just in case," you can select a plan that offers only domain name registration. With this plan, your domain is registered so that no one else can use it, but you do not have to pay for a complete Web hosting plan. This is sometimes referred to as "parking" your domain. You can also select a domain name registration plan that provides you with several email accounts. If you decide you want to go ahead and publish a Web site later, you can quickly upgrade your plan.

Back to top

You can have as many domain names as you like. You can have each domain name point to a different site, or you can have multiple domain names point to the same web site. Many companies register several domain names and have them all point to the same central web site. This is known as a “domain alias.”

Registering multiple domain names for the same site not only brings the largest draw to your site but it also can prevent competitors from poaching your potential customers. When picking multiple domain names for the same site, consider variations of your name such as common misspellings as well as both singular and plural versions of the name.

Back to top

The Domain Name System [DNS] is a distributed database, arranged hierarchically, containing records for domain names. The DNS system's main aim is to match a domain name to an IP Address. In order to fulfill this role, the DNS Server contains Records [called Resource Records] in a Zone File, which contains the domain name and IP address mappings for computers contained within that Zone. All Resource Records have a TTL [Time To Live], specifying the number of seconds other DNS servers and applications are allowed to cache the record.

Colocation customers can manage DNS services through your control panel. It will allow for management of the following Resource Records by using Plesk's Managed DNS Service:

I. Address Record [A Record]

The A Record is the most basic and the most important DNS record type. They are used to translate human friendly domain names such as "www.domain.com" into IP-addresses such as 1.2.3.4 (machine friendly numbers).

When you wish to host your domain name, you will be provided with an IP address that needs to be set as an A Record for that particular domain name.

II. Mail Exchanger [MX] Record

A MX Record identifies the mail server(s) responsible for a domain name. When sending an e-mail to This e-mail address is being protected from spambots. You need JavaScript enabled to view it , your mail server must first look up the MX Record for xyz.com to see which mail server actually handles mail for xyz.com (this could be mail.xyz.com - or someone else's mail server like mail.isp.com). Then it looks up the A Record for the mail server to connect to its IP-address.

A MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.

III. Canonical Name [Alias / CNAME] Record

CNAME Records are domain name aliases. Often computers on the Internet have multiple functions such as Web Server, FTP Server, Chat Server, etc. To mask this, CNAME Records can be used, to give a single computer multiple names (aliases).

Sometimes companies register their multiple domain names for their brand-names but still wish to maintain a single website. In such cases, a CNAME Record maybe used to forward traffic to their actual website. For example, www.abc.in could be CNAMEd to www.abc.com.

The most popular use of the CNAME Record type, is to provide access to a web server using both the standard www.domain.com and domain.com (without the www). This is usually done by adding a CNAME-record for the www name pointing to the short name [while creating an A Record for the short name (without www)].

CNAME Records can also be used when a computer or service needs to be renamed, to temporarily allow access through both the old and new name.

IV. Text [TXT] Record
A Text Record provides the ability to associate some text with a domain or a subdomain. This text is meant to strictly provide information and has no functionality as such. A TXT Record can store upto 255 characters of free form text. This record is generally used to convey information about the zone. Multiple TXT records are permitted but their order is not necessarily retained.

For example, you may add a TXT Record for yourname.com with the value as "This is my mail server". Here if anybody was checking ALL or TXT records of yourname.com, they would notice the above text appearing in the TXT record.

TXT Record is also used to implement the Sender Policy Framework (SPF) and DomainKeys specifications.

Sender Policy Framework (SPF)

Sender Policy Framework is an extension to the Simple Mail Transfer Protocol (SMTP). SPF allows software to identify and reject forged addresses in the SMTP MAIL FROM (Return-Path), a typical nuisance in e-mail spam.

SPF allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain. The technology requires two sides to work in tandem -

1. the domain owner publishes this information in an TXT Record in the domain's DNS zone, and when someone else's mail server receives a message claiming to come from that domain, then

2 the receiving server can check whether the message complies with the domain's stated policy. If, for example, the message comes from an unknown server, it can be considered a fake.

Back to top

A domain transfer itself will not cost you anything. We will only charge the yearly fee. If you have trouble managing the transfer and require assistance a fee for utilizing tech support time may apply.

Back to top

You can initiate a domain transfer on www.iboza.com

Back to top

When visitors type your domain name into their Web browsers, their request is referred to a nameserver that indicates the physical location (the IP address) of your domain on the Internet. When your site location changes to a new IP address, or when you deploy a new site with a new domain name, nameservers around the world must be notified of the change. This process of notification is referred to as propagation.

Propagation typically takes 48 to 72 hours. During this time, if you are transferring your domain, some nameservers will still refer to your site’s old location while nameservers that have already been notified of the change will refer to the new location. As a result, visitors accessing your site may be directed to either the old or new location, depending upon which nameserver they connect to.

If some visitors are still being directed to your old site location after 72 hours have elapsed, you should contact your previous Internet Presence Provider and request that they update their DNS and delete your domain from their servers. Once this has been done, and this change has been completely propagated, the transfer to your new location will be complete.
If your site is new, your site may not be recognised by all nameservers until the propagation period has completed.

Back to top