msgbartop
Gossimer’s Premier Web Hosting and Domain Registration Knowledgebase.
msgbarbottom

23 Jul 10 Restricting access of a MySQL Database User to allow connection from Specific Hosts only

As a security measure, you can restrict your Users’ access to your Databases such that they can only connect to them from particular hosts (computer networks). This would help you in preventing unauthorized access to your database.

Gossimer allows you to specify one of three levels of restriction upon database users:

  • Allow User to Connect from any Host: Selecting this option would allow unrestricted access to the Database for that User.
     
  • Allow User to Connect from this Server only: Selecting this option would mean that the User would have to connect to the Database from the system itself, and would be unable to use other Database applications from external hosts.
     
  • Specify Hosts: You can specify the hosts from which the Users can connect to the Database. Entering the allowed Hostnames or IP Addresses in a comma-separated format would prevent the User from accessing the database from any other location.

You can specify access restrictions for a database user on creation of the user account itself. Click here to read how to add a MySQL database user >>

However, if you had not done so and wish to do it now, or wish to modify the existing restrictions, follow the process mentioned below:

1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package. Click here to read how >>

2. In the search results view, click on the domain name. This will take you to the order details view.

3. Click on Manage Web Hosting Service in the lower toolbar.

4. In the Website Management interface pop-up that follows, go to Manage Website -> Database Manager -> List Databases.

5. The following page would contain a list of Databases associated with your website, with complete details for each Database such as the Database name, space utilization and the Users associated with it. Here, click on the User whose access you wish to restrict.

6. In the User details view that follows, click on Modify.

7. Now, select the radio-button adjacent to the restriction you wish to impose upon the user.

8. Click on Submit to effect the changes.
 

IMPORTANT

If you have installed a Power Tool in your Web Hosting Package, then you need to ensure that you do not perform any of the following actions:

  1. Modification/Deletion of the Database, that you selected during installation of the Power Tool
  2. Modification/Deletion of the Database User, that you selected during installation of the Power Tool

 

Tags: , , , , , , , , , , , , , , , , , , , , ,

22 Jul 10 Connecting Remotely to your database

In order to connect remotely to your database, you can use any third party tools available on the Internet. However, you need to set certain specifications from within your Control Panel to allow remote connections to your database.

Follow the process below to do so: 

     

  1. Login to your Control Panel, search for the domain name for which you have purchased this hosting package and proceed to the Order Details view. Click here to read how >>
  2. Click Manage Web Hosting Service in the lower toolbar.
  3. In the Website Management interface pop-up that follows, go to Manage Website -> Database Manager -> List Databases.
  4. Click the database user for which you want to allow remote connections.
  5. Click Modify.
  6. Under the Hostname Details section, select either Allow User to Connect from any Host or Specify Hosts (Comma Separated) if you would like to specify any specific computers that you are going to connect from (you need to know the IP addresses of these computers for this purpose).
  7. Click Submit.
  8.  

Tags: , , , , , , , , , , , , , ,

22 Jul 10 Transferring your .EU Domain Name

Before proceeding with the Transfer you are advised to first go check if your Domain Name can be Transferred. Click here to check if your domain name can be transferred >>
 

IMPORTANT

In case of a .EU Domain Name Transfer, the Expiry date is updated to 1 year from the date of Transfer and not to 1 year from the date the domain name was set to expire prior to Transfer.

For example, if a Domain Name has the Expiry date as 24 Oct, 2007 and it gets Transferred to another Registrar on 2 Sep, 2007. The new Expiry date will be 2 Sep, 2008 and not 24 Oct, 2008.
 


If you wish to Transfer a .EU Domain Name to Gossimer, then you need to follow the steps mentioned below:

Transfer Process for Customers

1. Login to your Control Panel from http://manage.gossimer.biz/customer.

2. In the Control Panel go to Domains -> Domain Registration -> Transfer. There, enter the Domain Name you wish to Transfer.

3. Select the Registrant Contact for this Domain Name. You may select from the available list of contacts or Add a New Contact.

It is compulsory for you to agree to the associated Product Agreement(s) by selecting the Check Box.

4. In order to avoid any downtime for the website/emails associated with your .EU domain name during the Transfer, it is necessary to mention the Name Servers already in use by your .EU domain name. You may also provide any new Name Servers that you would like to associate your .EU domain name with. Here, it is obvious that all the necessary DNS records are already created on the new Name Servers for the website/emails to be functional.

5. You need to mention any existing Child Name Servers for your .EU domain name alongwith their respective IP Addresses. This is necessary to avoid any downtime for the website/emails associated with any domain name using these Child Name Servers as their Name Servers. If you wish to Register any new Child Name Servers, you may also mention the same alongwith the respective IP Addresses. These new Child Name Servers will be Registered once the domain name is Transferred successfully.

Child Name Servers can also be Registered separately. Click here to know how >>

6. Finally, proceed with the Payment of the Invoice. Click here to read more details on Payment >>.

Now that you have placed the Transfer Order, the Registrant Contact for the Domain Name will receive an e-mail from the Registry for the Transfer Authorization process, which needs to be approved within 7 days. The Registry provides an additional grace period of 7 days for approval, in case the Transfer was not approved within the initial 7 day period. The authorization can also be provided through a fax to the Registry from the Registrant Contact. Template of the confirmation fax is provided below:

Transfer confirmation fax >>

The request is processed once the Registry receives approval from the Registrant.

Transfer Process for Resellers

1. Login to your Control Panel from http://manage.gossimer.biz/reseller.

2. In the Control Panel go to Products -> Domain Registration -> Transfer. There you would have to enter the Domain Name you wish to Transfer.

IMPORTANT

Transfer request for .EU Domain Names cannot be placed from the Storefront/within the Control Panel. Hence, it is advised that you re-direct all purchase related links from within your, your company user’s and your Customer’s Control Panel to your SuperSite URL or your Custom URL (if you have integrated with our platform using our API).

Reference:
Click here to know what is SuperSite >>
Click here to read about API Integration >>
Click here to read how to integrate your Website and Shopping Cart with your Customer Control Panel >>

 

3. Enter the Username (Email Address) of the Customer, on whose behalf you wish to buy this Service. If the Customer is new, you can Add the Customer, by filling the form given there.

4. Select the Registrant Contact for this Domain Name. You may select from the available list of contacts or Add a New Contact.

It is compulsory for you to agree to the associated Product Agreement(s) by selecting the Check Box.

5. In order to avoid any downtime for the website/emails associated with your .EU domain name during the Transfer, it is necessary to mention the Name Servers already in use by your .EU domain name. You may also provide any new Name Servers that you would like to associate your .EU domain name with. Here, it is obvious that all the necessary DNS records are already created on the new Name Servers for the website/emails to be functional.

6. You need to mention any existing Child Name Servers for your .EU domain name alongwith their respective IP Addresses. This is necessary to avoid any downtime for the website/emails associated with any domain name using these Child Name Servers as their Name Servers. If you wish to Register any new Child Name Servers, you may also mention the same alongwith the respective IP Addresses. These new Child Name Servers will be Registered once the domain name is Transferred successfully.

Child Name Servers can also be Registered separately. Click here to know how >>

7. Finally, proceed with the Payment of the Invoice. Click here to read more details on Payment >>.

Now that you have placed the Transfer Order, the Registrant Contact for the Domain Name will receive an e-mail from the Registry for the Transfer Authorization process, which needs to be approved within 7 days. The Registry provides an additional grace period of 7 days for approval, in case the Transfer was not approved within the initial 7 day period. The authorization can also be provided through a fax to the Registry from the Registrant Contact. Template of the confirmation fax is provided below:

Transfer confirmation fax >>

The request is processed once the Registry receives approval from the Registrant.

 

Tags: , , , , , , , , , , , , , , , , , , , ,

15 Jul 10 What is Free DNS? Which types of Resource Records does ResellerClub allow?

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.

Most Web Hosting companies do not provide you with an interface to manage your own DNS Records and/or the ability to select multiple providers for various Services like Web Hosting, Mail Hosting, etc..

Gossimer, LLC gives you complete control over the following Resource Records by using our Free 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 user@xyz.com, 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. Authoritative Name Server
[NS] Record

NS Records identify DNS servers responsible (authoritative) for a Zone. A Zone should contain one NS Record for each of its own DNS servers (primary and secondaries). This mostly is used for Zone Transfer purposes (notify). These NS Records have the same name as the Zone in which they are located.

But the most important function of the NS Record is Delegation. Delegation means that part of a domain is delegated to other DNS servers.

You can also delegate sub-domains of your own domain name (such as subdomain.yourname.com) to other DNS servers. An NS Record identifies the name of a DNS server, not the IP Address. Because of this, it is important that an A Record for the referenced DNS server exists, otherwise there may not be any way to find that DNS server and communicate with it.

If a NS Record delegates a sub-domain (subdomain.yourname.com) to a DNS Server with a name in that sub-domain (ns1.subdomain.yourname.com), an A Record for that server (ns1.subdomain.yourname.com) must exist in the Parent Zone (yourname.com). This A Record is referred to as a Glue Record, because it doesn’t really belong in the Parent Zone, but is necessary to locate the DNS Server for the delegated sub-domain.


V. Text [TXT] RecordA 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 -

i. 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

ii. 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.

Click here to find more information on SPF and how you may use it to authenticate mails being sent from your domain name >>

DomainKeys

DomainKeys is an e-mail authentication system (developed at Yahoo!) designed to verify the authenticity of the E-mail sender and the message integrity (i.e,. the message was not altered during transit). The DomainKeys specification has adopted aspects of Identified Internet Mail to create an enhanced protocol called DomainKeys Identified Mail (DKIM).

Click here to find more information about DomainKeys and how you can prove and protect an Email Sender’s identity >>
 

VI. Start of Authority [SOA] Parameters Each Zone contains one SOA Record, which holds the following parameters for the Zone -

Name of Primary DNS Server - The domain name of the Primary DNS Server for the Zone. The Zone should contain a matching NS Record.

Mailbox of the Responsible Person – The email address of the person responsible for maintenance of the Zone.

Serial Number - Used by Secondary DNS Servers to check if the Zone has changed. If the Serial Number is higher than what the Secondary Server has, a Zone Transfer will be initiated. This number is automatically increased by our Servers when changes to the Zone or its Records are made.

Refresh Interval - How often Secondary DNS Servers should check if changes are made to the zone.

Retry Interval - How often Secondary DNS Server should retry checking, if changes are made – if the first refresh fails.

Expire Interval - How long the Zone will be valid after a refresh. Secondary Servers will discard the Zone if no refresh could be made within this interval.

Minimum (Default) TTL - Used as the default TTL for new records created within the zone. Also used by other DNS Server to cache negative responses (such as record does not exist, etc.).

Tags: , , , , , , , , , , , , , , , , , , , ,

09 Jul 10 Using the IP Deny Manager to manage access to your website

 

By default, your website becomes visible to all people browsing the Internet. Typically, large websites running forums, blogs, ecommerce activities, etc. are prone to abuse from spammers, people posting malicious content, etc., causing disruption of website services. The most effective method of dealing with such nuisance is to deny access to your website from such mischief mongers.

Using Gossimer’s IP Deny Manager tool within your Web Hosting Control Panel, you can easily control access to your website based on the visitor’s IP Address. Moreover, you may deny access from all IP Addresses of a particular block of IP Addresses, if you are receiving constant abuse from the entire range of IP Addresses.

Follow the process listed below to block/allow access to your website based on IP Addresses:

     

  1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package. Click here to know how >>
     
  2. In the search results view, click on the domain name. This will take you to the Order Details View.
     
  3. Click on Manage Web Hosting Service in the lower toolbar.
     
  4. In the Website Management interface pop-up that follows,

    go to Manage Website -> IP Deny Manager, if you have a Windows web hosting package

    or

    go to Manage Website -> Web Server Manager -> IP Deny Manager, if you have a Linux web hosting package
     

  5. From this interface, you may either restrict access to your website or allow previously blocked IP Addresses to access your website. a. Restricting Access to your website – You may mention either one or more individual IP Addresses, or entire Blocks of IP Addresses on  individual lines.

    Examples

    i. If you wish to block a single IP Address, simply input the same in the textbox as

     1.1.1.1

    ii. If you wish to block multiple individual IP Addresses, then you may mention them on separate lines

     2.2.2.2
     3.3.3.3

    iii. If you wish to block an entire range of IP Addresses, then you may mention them as

     4.4.4.*
     5.5.*.*
     6.*.*.*

    IMPORTANT  

    1. Use extreme caution when deciding to deny access to entire range of IP Addresses, as you might end up denying access to your genuine visitors.

    2. IP Address of the type *.*.*.* is not allowed.
     

    b. Allowing Access to your website - If you wish to enable access to a previously blocked IP Address, then you need to simply select that IP Address in the textbox and press the Delete key on your computer’s keyboard.
     

  6. Clicking on the Submit button would save all your settings.
  7.  

 

IMPORTANT 

In order to complete the action in case of Linux Hosting, the Web Server needs to be restarted. Random restarts affect other services running on the Server. In order to avoid this, the Server has been scheduled to restart at intervals of 20 minutes. Hence, the changes might take upto 20 minutes to be effective.

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , ,

06 Jul 10 Web Statistics Management Settings

Gossimer gives you the ability to comprehensively customise your Web Statistics reports, to obtain accurate and more pertinent details about your Website. You can customise your reports from your Control Panel itself; follow the process mentioned below to do so:

1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package. Click here to read how >>

2. In the search results view, click on the domain name. This will take you to the order details view.

3. Click on Manage Web Hosting Service in the lower toolbar.

4. In the Website Management interface pop-up that follows, go to Manage Website -> Web Statistics Manager -> Settings.

5. This page allows you to specify the following options, configure them as per your requirement:

  • Generate Web Stats: Select YES if you wish to obtain statistics for your website. The statistics are generated on a daily basis.
     
  • Keep Backup of Historic Files: Whenever your web statistics are to be updated, the system overwrites the old (historic) files with the new data. However, if an error is encountered (e.g. if your site runs out of allowed disk space), the file may get corrupt, causing you to lose all old data as well. Selecting this option would keep a copy of the old file for your referral.
     
  • Purge Log File: Your raw log files would be deleted after the statistics are generated, if you choose YES. This would prevent logs from taking up web space.
     
  • Skip Hosts: Choose this option to avoid recording statistics from specific hosts. For example, you might wish not to record statistics for all hits/visits from your own home/office. Specify such hosts or IP addresses here.
     
  • Skip Files: Use this option to avoid recording data for particular URLs. Using this, you can make sure that statistics pertaining to unimportant pages are not recorded.
     
  • Only Files: This is the exact opposite of the previous option. Using this, you can choose to record data only pertaining to specific/important pages.
     
  • Not Page List: Enter a list of file extensions that would be considered only a Hit, and not a Page View.
     
  • Protect Webstats: Password protection for web statistics can be enabled/disabled using this option. This option is available only in case of Windows hosting. Click here to read how to enable password protection for web statistics in case of Linux hosting >>
IMPORTANT

In order to complete the action in case of Linux Hosting, the Web Server needs to be restarted. Random restarts affect other services running on the Server. In order to avoid this, the Server has been scheduled to restart at intervals of 20 minutes. Hence, the changes might take upto 20 minutes to be effective.

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , ,

01 Jul 10 Registering and Managing Child Name Servers

Child Name Servers are Name Servers which are registered with the Registry under your domain name. You have to register Name servers with the Registry, before you can use them as Name Servers for registering domain names. Child Name Servers can be registered only by the owner of the domain name under which they are registered. For instance, a Child Name Server ns2.xyz.com can only be registered by the Owner of xyz.com.

Managing Child Name Servers

  1. Login to your Control Panel, search for the domain name and proceed to the Order Details view. Click here to read how >>
     
  2. Click on the Manage Child Name Server button.

Here, you can:

Add a Child Name Server

Enter the Host Name of the Child Name Server you wish to add in the Host Name box, key in its IP Address and click on Submit.

For example, for yourdomainname.com, you may use the Host Name as “ns1″ and IP Address as “111.222.333.444″.
 

IMPORTANT

  1. A domain name can have any* number of Child Name Servers associated with it.
     
  2. Each Child Name Server (except for .EU and .UK domain names) can have upto 13 unique IP Addresses associated with it. For example, you can Registrar a Child Name Server with the Host Name “ns1″ and associate upto 13 unique IP Addresses with this Host Name.In case of .EU domain names, each Child Name Server can have upto 9 unique IP Addresses associated with it. For example, you can Registrar a Child Name Server with the Host Name “ns1″ for yourdomainname.eu and associate upto 9 unique IP Addresses with this Host Name.

    In case of .UK domain names, each Child Name Server can have only a single unique IP Address associated with it. For example, you can Registrar a Child Name Server with the Host Name “ns1″ for yourdomainname.uk and associate only a single unique IP Address with this Host Name.
     

  3. Registering a Child Name Server as mentioned above is just the first step. The Child Name Server needs to be registered at the Registry to only serve as a non-authoritative Record should your Child Name Server not be resolvable in some extreme condition.This Name Server would start working only after you have added an Address (A) Record or Canonical (CNAME) Record for this Name Server within the Zone for the domain name (of this Child Name Server) at your own DNS Server, thus binding the NS to the IP Address.

    Examples

    i. If you are running your own DNS Servers, then you would need to add a Zone for the domain name yourdomainname.com and create an A Record like

    ns1.yourdomainname.com. 38400 IN A 111.222.333.444

    ii. If you wish to simply point your Name Servers to another Name Servers, then you may do so either way -

    1. you may either add a CNAME Record to your Service Provider’s Name Server, after buying Managed DNS service through them - 

      ns1.yourdomainname.com. 38400 IN CNAME ns1.serviceprovider.com,

      or
       

    2. you may add an Address Record to your Service Provider’s Name Server IP Address, after buying Managed DNS service through them -ns1.yourdomainname.com. 38400 IN A 777.888.999.000
  4. *In case of .EU domain names, all Child Name Servers that you create/add, are automatically associated with that .EU domain name as a Name Server. Due to this limitation, you will only be able to add upto 9 Child Name Servers for .EU domain names (Note: The maximum number of Name Servers that can be associated with any .EU domain name is 9). If you have already added other Name Servers (not Child Name Servers of this .EU domain name), then the number of Child Name Servers that you can create would reduce by that many. Click here to know more about Name Servers >>Example

    i. yourdomainname.eu

    Child Name Servers created – ns1.yourdomainname.eu and ns2.yourdomainname.eu
    Thus, Name Servers automatically added for this domain name – ns1.yourdomainname.eu and ns2.yourdomainname.eu

    ii. yourotherdomainname.eu

    Name Servers used – ns1.hostingprovider.com, ns2.hostingprovider.com
    Child Name Servers created – ns1.yourotherdomainname.eu, ns2.yourotherdomainname.eu
    Thus, Name Servers automatically added for this domain name – ns1.yourotherdomainname.eu, ns2.yourotherdomainname.eu

    So in all 4 Name Servers will be associated with yourotherdomainname.eu – ns1.hostingprovider.com, ns2.hostingprovider.com, ns1.yourotherdomainname.eu, ns2.yourotherdomainname.eu

    This means that now for the domain name yourotherdomainname.eu, you can only add upto 5 other Child Name Servers or Name Servers since every time you create a Child Name Server, it gets automatically associated with the .EU domain name as a Name Server.
     

  5. *In case of .UK domain names, all Child Name Servers that you create/add, are automatically associated with that .UK domain name as a Name Server. Due to this limitation, you will only be able to add upto 10 Child Name Servers for .UK domain names (Note: The maximum number of Name Servers that can be associated with any .UK domain name is 10). If you have already added other Name Servers (not Child Name Servers of this .UK domain name), then the number of Child Name Servers that you can create would reduce by that many. Click here to know more about Name Servers >> 

    Example

    i. yourdomainname.uk

    Child Name Servers created – ns1.yourdomainname.uk and ns2.yourdomainname.uk
    Thus, Name Servers automatically added for this domain name – ns1.yourdomainname.uk and ns2.yourdomainname.uk

    ii. yourotherdomainname.uk

    Name Servers used – ns1.hostingprovider.com, ns2.hostingprovider.com
    Child Name Servers created – ns1.yourotherdomainname.uk, ns2.yourotherdomainname.uk
    Thus, Name Servers automatically added for this domain name – ns1.yourotherdomainname.uk, ns2.yourotherdomainname.uk

    So in all 4 Name Servers will be associated with yourotherdomainname.uk – ns1.hostingprovider.com, ns2.hostingprovider.com, ns1.yourotherdomainname.uk, ns2.yourotherdomainname.uk

    This means that now for the domain name yourotherdomainname.uk, you can only add upto 6 other Child Name Servers or Name Servers since every time you create a Child Name Server, it gets automatically associated with the .UK domain name as a Name Server.

  6.  

Modifying a Child Name Server

Modifying the Hostname – Make the modifications in the Host Name textbox and click on the Modify Host Name button.
Modifying the IP Address – Make the modifications in the IP Address textbox and click on the Modify IP Address button.

Deleting a Child Name Server

Click on the Red Cross button.

IMPORTANT

You may get an error while Deleting a Child Name Server if this is being used by another domain name of the same extension as a Name Server.

For Example,

If the Child Name Server ns1.yourdomainname.com is being used by xyz.com as its Name Server, then you will not be able to delete ns1.yourdomainname.com until xyz.com modifies its Name Server (to some other Name Server).

However, if xyz.info was using ns1.yourdomainname.com as its Name Server, then you would not face any issue while deleting your Child Name Server - ns1.yourdomainname.com.

Tags: , , , , , , , , , , , , , , , , , , , ,