<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HostEase Hosting Blog &#187; ns</title>
	<atom:link href="http://blog.hostease.com/tag/ns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hostease.com</link>
	<description>Ease your web hosting with HostEase</description>
	<lastBuildDate>Sat, 07 Jan 2012 07:59:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Why Should We Use HostEase&#8217;s ns</title>
		<link>http://blog.hostease.com/241/</link>
		<comments>http://blog.hostease.com/241/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 14:48:56 +0000</pubDate>
		<dc:creator>Joey Leblanc</dc:creator>
				<category><![CDATA[About HostEase]]></category>
		<category><![CDATA[hostease]]></category>
		<category><![CDATA[ns]]></category>

		<guid isPermaLink="false">http://blog.hostease.com/?p=241</guid>
		<description><![CDATA[Recently, some customers ask if they can use their former nameservers instead of changing the nameservers to HostEase’s. Here I’ll give some explanation on it. It’s known that a domain name will be managed by at least two nameservers (ex&#62; ns1.hostease.com &#38; ns2.hostease.com) after being registered. Usually, these two nameservers belong to the domain registrar [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, some customers ask if they can use their former nameservers instead of changing the nameservers to HostEase’s. Here I’ll give some explanation on it.</p>
<p>It’s known that a domain name will be managed by at least two nameservers (ex&gt; ns1.hostease.com &amp; ns2.hostease.com) after being registered. Usually, these two nameservers belong to the domain registrar where you register your domain name. For example, if you registered a domain name at Godaddy.com, your default ns will be Godaddy’s. Once you heard that <a href="http://www.hostease.com">HostEase</a>’s web hosting is good and reliable, you plan to purchase <a href="http://www.hostease.com">HostEase</a>’s web hosting. After paying for the order you have placed, the new account information will be sent to you. And you will see one sentence as followed: If you are using an existing domain with your new hosting account, you will need to update the nameservers to point to the nameservers listed below.</p>
<p>Nameserver 1: ns1.hostease.com (174.37.94.191)<br />
Nameserver 2: ns2.hostease.com (67.228.202.115)</p>
<p>Why? Some people may be a little puzzled. Well, in fact, you can use your former ns, but sometimes it may bring some inconvenience to you. For example, if you purchase basic hosting package from <a href="http://www.hostease.com">HostEase.com</a> and you will enjoy unlimited addon domain feature. But you will find that it’s not possible for you to add a domain in your cPanel if you don’t change your ns to <a href="http://www.hostease.com">HostEase</a>’s. And also if you plan to add a subdomain, you have to add a A record in you domain control panel. Every time you should make corresponding domain record in you former domain control panel after operating in Domains of your cPanel. But if you have changed your ns to <a href="http://www.hostease.com">HostEase</a>’s, it will help you add corresponding domain record when you add a subdomain or change the MX record and etc…. I believe you have already understood why you should use <a href="http://www.hostease.com">HostEase</a>’s ns when using its hosting.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hostease.com/241/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

