If you have a domain name registered with us and it is using our default name servers, login to Domain cPanel to Manage DNS records (A, TXT, CNAME, etc) on DIY basis.

Visit https://www.indiahosting.org > My Domains > Login with your email > Or use forgot password > Click My Account > Manage Orders > List/Search Orders > Click Domain > Scroll Down to DNS Management > Click Manage DNS > DNS Service interface > Edit, Remove records

[[File:Locate DNS.png|thumb|alt=Manage DNS|Manage DNS]]

Once DNS changes are saved, it may take upto 48 hours for propagation. If you need faster and more secure DNS services, migrate to our [https://www.indiahosting.org/product/business-host/ cloud hosting] with free Premium DNS.

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 Resource Records (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 Time To Live TTL (TTL), specifying the number of seconds other DNS servers and applications are allowed to cache the Record.

If you need more detailed technical guides, refer below or search at https://osspl.myorderbox.com/kb/

Mail Exchanger (MX) Record (Anchor: defmx): An MX Record identifies the email server(s) responsible for a domain name. When sending an email to user@osspl.com, your email server must first looks up the MX Record for xyz.com to see which email server actually handles email for xyz.com (this could be mail.osspl.com or someone else's email server like mx1.osspl.com). Then it looks up the A Record for the email server to connect to its IP address.

An MX Record has a Preference number, indicating the order in which the email server should be used. Email servers will attempt to deliver email to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.

Canonical Name (CNAME) Record (Anchor: defcname): 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 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.

Example:

www.abc.in could be CNAME to www.abc.com.

The most popular use of the CNAME Record, is to provide access to a Web Server using both the standard www.yourdomainname.com and yourdomainname.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 shorter 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.

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

The most important function of the NS Record is Delegation. Delegation implies 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.yourdomainname.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 an NS Record delegates a sub-domain (subdomain.yourdomainname.com)to a DNS Server with a name in that sub-domain (ns1.subdomain.yourdomainname.com), an A Record for that server (ns1.subdomain.yourdomainname.com) must exist in the Parent Zone (yourdomainname.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.

Text (TXT) Records (Anchor: deftxt): TXT Records provide the ability to associate some text with a domain or a sub-domain. 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.

Example:

You may add a TXT Record for yourdomainname.com with the value as This is my email server. Here, if anybody was checking the TXT Records of yourdomainname.com, would notice the above text appearing in the TXT Record.

TXT Record can be used to implement the following:

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). 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 name. 1. The technology requires two sides to work in tandem:

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

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.

DomainKeys: DomainKeys is an email authentication system (developed at Yahoo!) designed to verify the authenticity of the email 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). 2

Service (SRV) Record (Anchor: defsrv): An SRV or Service Record is a category of data in the DNS specifying information on available services. When looking up for a service, you must first lookup the SRV Record for the service to see which server actually handles it. Then it looks up the Address Record for the server to connect to its IP Address.

The SRV Record has a priority field similar to an MX Record's priority value. Clients always use the SRV Record with the lowest priority value first, and only fall back to other SRV Records if the connection with this Record's host fails. If a service has multiple SRV records with the same priority value, clients use the weight field to determine which host to use. The weight value is relevant only in relation to other weight values for the service, and only among SRV Records with the same priority value.

Newer Internet Protocols such as SIP (Session Initiation Protocol) and XMPP (Extensible Messaging and Presence Protocol) often require SRV support from clients.

Start of Authority (SOA) Record (Anchor: defsoa): Each Zone contains a single SOA Record, which holds the following values 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 the 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 DNS servers when changes to the Zone or its Records are made.

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

Retry Interval: How often the 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 servers to cache negative responses (such as Record does not exist, etc.).

Manage DNS

2025-07-02T08:38:07Z

Admin:

If you have a domain name registered with us and it is using our default name servers, login to Domain cPanel to Manage DNS records (A, TXT, CNAME, etc) on DIY basis.

Visit https://www.indiahosting.org > My Domains > Login with your email > Or use forgot password > Click My Account > Manage Orders > List/Search Orders > Click Domain > Scroll Down to DNS Management > Click Manage DNS > DNS Service interface > Edit, Remove records

[[File:Locate DNS.png|thumb|alt=Manage DNS|Manage DNS]]

Once DNS changes are saved, it may take upto 48 hours for propagation. If you need faster and more secure DNS services, buy Premium DNS from right side menu in Domain cPanel.

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 Resource Records (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 Time To Live TTL (TTL), specifying the number of seconds other DNS servers and applications are allowed to cache the Record.

If you need more detailed technical guides, refer below or search at https://osspl.myorderbox.com/kb/

Mail Exchanger (MX) Record (Anchor: defmx): An MX Record identifies the email server(s) responsible for a domain name. When sending an email to user@osspl.com, your email server must first looks up the MX Record for xyz.com to see which email server actually handles email for xyz.com (this could be mail.osspl.com or someone else's email server like mx1.osspl.com). Then it looks up the A Record for the email server to connect to its IP address.

An MX Record has a Preference number, indicating the order in which the email server should be used. Email servers will attempt to deliver email to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.

Canonical Name (CNAME) Record (Anchor: defcname): 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 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.

Example:

www.abc.in could be CNAME to www.abc.com.

The most popular use of the CNAME Record, is to provide access to a Web Server using both the standard www.yourdomainname.com and yourdomainname.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 shorter 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.

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

The most important function of the NS Record is Delegation. Delegation implies 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.yourdomainname.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 an NS Record delegates a sub-domain (subdomain.yourdomainname.com)to a DNS Server with a name in that sub-domain (ns1.subdomain.yourdomainname.com), an A Record for that server (ns1.subdomain.yourdomainname.com) must exist in the Parent Zone (yourdomainname.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.

Text (TXT) Records (Anchor: deftxt): TXT Records provide the ability to associate some text with a domain or a sub-domain. 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.

Example:

You may add a TXT Record for yourdomainname.com with the value as This is my email server. Here, if anybody was checking the TXT Records of yourdomainname.com, would notice the above text appearing in the TXT Record.

TXT Record can be used to implement the following:

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). 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 name. 1. The technology requires two sides to work in tandem:

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

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.

DomainKeys: DomainKeys is an email authentication system (developed at Yahoo!) designed to verify the authenticity of the email 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). 2

Service (SRV) Record (Anchor: defsrv): An SRV or Service Record is a category of data in the DNS specifying information on available services. When looking up for a service, you must first lookup the SRV Record for the service to see which server actually handles it. Then it looks up the Address Record for the server to connect to its IP Address.

The SRV Record has a priority field similar to an MX Record's priority value. Clients always use the SRV Record with the lowest priority value first, and only fall back to other SRV Records if the connection with this Record's host fails. If a service has multiple SRV records with the same priority value, clients use the weight field to determine which host to use. The weight value is relevant only in relation to other weight values for the service, and only among SRV Records with the same priority value.

Newer Internet Protocols such as SIP (Session Initiation Protocol) and XMPP (Extensible Messaging and Presence Protocol) often require SRV support from clients.

Start of Authority (SOA) Record (Anchor: defsoa): Each Zone contains a single SOA Record, which holds the following values 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 the 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 DNS servers when changes to the Zone or its Records are made.

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

Retry Interval: How often the 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 servers to cache negative responses (such as Record does not exist, etc.).

File:Locate DNS.png

2025-07-02T08:37:14Z

Admin:

Manage DNS

2025-07-02T08:36:13Z

Admin: Created page with "If you have a domain name registered with us and it is using our default name servers, login to Domain cPanel to Manage DNS records (A, TXT, CNAME, etc) on DIY basis. Visit https://www.indiahosting.org > My Domains > Login with your email > Or use forgot password > Click My Account > Manage Orders > List/Search Orders > Click Domain > Scroll Down to DNS Management > Click Manage DNS > DNS Service interface > Edit, Remove records Once DNS changes are saved, it may take..."

If you have a domain name registered with us and it is using our default name servers, login to Domain cPanel to Manage DNS records (A, TXT, CNAME, etc) on DIY basis.

Visit https://www.indiahosting.org > My Domains > Login with your email > Or use forgot password > Click My Account > Manage Orders > List/Search Orders > Click Domain > Scroll Down to DNS Management > Click Manage DNS > DNS Service interface > Edit, Remove records

Once DNS changes are saved, it may take upto 48 hours for propagation. If you need faster and more secure DNS services, buy Premium DNS from right side menu in Domain cPanel.

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 Resource Records (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 Time To Live TTL (TTL), specifying the number of seconds other DNS servers and applications are allowed to cache the Record.

If you need more detailed technical guides, refer below or search at https://osspl.myorderbox.com/kb/

Mail Exchanger (MX) Record (Anchor: defmx): An MX Record identifies the email server(s) responsible for a domain name. When sending an email to user@osspl.com, your email server must first looks up the MX Record for xyz.com to see which email server actually handles email for xyz.com (this could be mail.osspl.com or someone else's email server like mx1.osspl.com). Then it looks up the A Record for the email server to connect to its IP address.

An MX Record has a Preference number, indicating the order in which the email server should be used. Email servers will attempt to deliver email to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.

Canonical Name (CNAME) Record (Anchor: defcname): 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 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.

Example:

www.abc.in could be CNAME to www.abc.com.

The most popular use of the CNAME Record, is to provide access to a Web Server using both the standard www.yourdomainname.com and yourdomainname.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 shorter 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.

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

The most important function of the NS Record is Delegation. Delegation implies 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.yourdomainname.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 an NS Record delegates a sub-domain (subdomain.yourdomainname.com)to a DNS Server with a name in that sub-domain (ns1.subdomain.yourdomainname.com), an A Record for that server (ns1.subdomain.yourdomainname.com) must exist in the Parent Zone (yourdomainname.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.

Text (TXT) Records (Anchor: deftxt): TXT Records provide the ability to associate some text with a domain or a sub-domain. 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.

Example:

You may add a TXT Record for yourdomainname.com with the value as This is my email server. Here, if anybody was checking the TXT Records of yourdomainname.com, would notice the above text appearing in the TXT Record.

TXT Record can be used to implement the following:

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). 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 name. 1. The technology requires two sides to work in tandem:

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

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.

DomainKeys: DomainKeys is an email authentication system (developed at Yahoo!) designed to verify the authenticity of the email 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). 2

Service (SRV) Record (Anchor: defsrv): An SRV or Service Record is a category of data in the DNS specifying information on available services. When looking up for a service, you must first lookup the SRV Record for the service to see which server actually handles it. Then it looks up the Address Record for the server to connect to its IP Address.

The SRV Record has a priority field similar to an MX Record's priority value. Clients always use the SRV Record with the lowest priority value first, and only fall back to other SRV Records if the connection with this Record's host fails. If a service has multiple SRV records with the same priority value, clients use the weight field to determine which host to use. The weight value is relevant only in relation to other weight values for the service, and only among SRV Records with the same priority value.

Newer Internet Protocols such as SIP (Session Initiation Protocol) and XMPP (Extensible Messaging and Presence Protocol) often require SRV support from clients.

Start of Authority (SOA) Record (Anchor: defsoa): Each Zone contains a single SOA Record, which holds the following values 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 the 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 DNS servers when changes to the Zone or its Records are made.

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

Retry Interval: How often the 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 servers to cache negative responses (such as Record does not exist, etc.).

Apps

2025-05-15T06:25:53Z

Admin: /* Why we do not have apps for Google Play or Apple Store? */

==== Why we do not have apps for Google Play or Apple Store? ====
As a small agency, dealing with Google APKs, Microsoft, Apple and their marketplace windows are big harassment. Since 2017, we’re not even developing or recommending any mobile apps as a policy both for long-term security and protecting our network integrity. Refer the [https://www.wisepoint.org/1300 official announcement].

Apps

2025-05-15T06:25:11Z

Admin: Created page with "==== Why we do not have apps for Google Play or Apple Store? ==== As a small agency, dealing with Google APKs, Microsoft, Apple and their marketplace windows are big harassment. We’ll not even developing or recommending any mobile apps as a policy both for long-term security and protecting our network integrity. Refer the [https://www.wisepoint.org/1300 official announcement]."

==== Why we do not have apps for Google Play or Apple Store? ====
As a small agency, dealing with Google APKs, Microsoft, Apple and their marketplace windows are big harassment. We’ll not even developing or recommending any mobile apps as a policy both for long-term security and protecting our network integrity. Refer the [https://www.wisepoint.org/1300 official announcement].

Drupal is an open source (OS) CMS framework that allows you to publish, manage and organize many types of simple or complex websites and large corporate CMS portals. It is highly developed Content Management System for developing and implementing world class content rich websites. Drupal functionality, combined with many modules and themes will enable you to build any type of dynamic web site with ease and much more... Drupal community offers hundreds of freely available themes, modules and other extensions.

[[File:Logo.png|thumb|right|Drupal CMS]] PHP programmers can create and use their own modules and themes on Drupal platform. Take a look at the Drupal Site for more information. Prime offers Drupal Web Hosting, Shared hosting, dedicated hosting, Drupal Installation services and solutions, drupal on could, drupal mobile, drupal hosted solutions and more...

If you already own a domain, just change name server settings or you can optionally purchase a domain if you do not own one. Access Top Class Hardware and Server Specs with Latest Software. The servers run the latest and most optimized application software. Drupal for SEO? Technically, Drupal has everything to become a magnet for search engines. But you need compelling content to become SEO champion. Having one does not automatically guarantee another though, both demand it's own unique approach.

Secure, reliable, oldest hosting providers in India - Offers Drupal Hosting, customization, design, setup with many related support / services. Install any version of Drupal on our fast web servers with latest Apache / Nginx, MariaDB / MySQL, Bootstrap, Node.js, Redis, Ruby, Java and PHP support. If you already own a domain, just change name server settings or you can optionally purchase a domain if you do not own one. Access Top Class Hardware and Server Specs with Latest Software to power your drupal portal. The servers run the latest and most optimized application software.

Hundreds of corporate, community and high-end Drupal sites and portals developed, customized, hosted and maintained by us including American Surgeons Association, High Commission of Srilanka, Educom Pearson, Indian Ministry of Commerce, Golf Union of India, Academy for Clinical and Surgical Excellence, etc. How to implement it? Hire the right web design agency, cut the hype.

==External links==
*[https://h.osspl.com Drupal Demo]

[[Category: About]]
[[Category: Products]]
[[Category: Linux Hosting]]
[[Category: Windows Hosting]]
[[Category: Multi Domain Hosting]]
[[Category: Web Design]]
[[Category: Website Builder]]
[[Category: Custom Servers]]
[[Category: Virtual Private Server]]
[[Category: Digital Marketing]]
[[Category: Mobile Apps]]
[[Category:Property]]
[[Category:Indian websites]]
[[Category: Reseller]]

Registering and Managing Child Name Servers

2023-12-21T13:06:29Z

Admin:

1. Registering and Managing Child Name Servers

1.1. Add a Child Name Server (Anchor: add)

1.2. Modify a Child Name Server (Anchor: modify)

1.3. Delete a Child Name Server (Anchor: delete)

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 other domain names. Child Name Servers can be registered only by the owner of the domain name under which they are registered.

Example:

A Child Name Server ns2.xyz.com can only be registered by the Owner of xyz.com.
Note

.WEB.IN domain name do not support Child Name Servers.
Registering and Managing Child Name Servers

Login to your Control Panel, search for the domain name and proceed to the Order Information view. 1
About Lock / Suspension
Note

If the domain name is Locked/Suspended, you will have to first get it Unlocked/Unsuspended it before proceeding further.

For Resellers: If the domain name is Locked by you, you may proceed without Unlocking it.

For Resellers: If the domain name is Locked by Prime, you need to get it Unlocked first. Contact our Support Team at https://h.osspl.com.

For Resellers: If the domain name is Suspended by either you or Prime, it needs to be first Unsuspended, before you can proceed.
Additional Information

Unlocking a domain name

Unsuspending a domain name

Click the Child Name Servers link.

Here, you may:
Add a Child Name Server (Anchor: add)

Enter the Host Name of the Child Name Server you wish to add in the Host Name box, mention its IP Address (IPv4 or IPv6) and click the Save button.

Examples:

For yourdomainname.com, you may use the Host Name as ns1.yourdomainname.com and an IPv4 IP Address as 111.222.333.444.

yourdomainname.biz could have the Host Name as dns1.yourdomainname.biz and an IPv6 IP Address as 2001:0db8:0:0:0:0:1428:57ab.
Note

Registering a Child Name Server as mentioned above is just the first step. The Child Name Server is required 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 either an Address (A) Record for IPv4 or AAAA Record for IPv6 or Canonical (CNAME) Record for this Name Server within the Zone for the domain name (of this Child Name Server) in your own DNS Server, thus binding the NS to the IP Address.

Examples:

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

Similarly, you may add an AAAA Record as

ns1.yourdomainname.com. 38400 IN AAAA 2001:0db8:0:0:0:0:1428:57ab

If you wish to simply point your Name Servers to other Name Servers, then you may do so by either:

you may either add a CNAME Record to your Service Provider's Name Server, after enabling Managed DNS service through them:

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

or

you may add an A or AAAA Record to your Service Provider's Name Server IP Address (depending upon whether your Service Provider has an IPv4 or IPv6), after enabling Managed DNS service through them:

ns1.yourdomainname.com. 38400 IN A 777.888.999.000

or

ns1.yourdomainname.com. 38400 IN AAAA 2001:0db8:0:0:0:0:1428:57ab
Additional Information

Creating DNS Records through Prime's DNS Service
Errors and Domain Name Extension Specific Conditions
Note

Generally, a domain name may have any number of Child Name Servers associated with it.

You will encounter the below error message in case an invalid or reserved IP Address is used:
Attention

Object does not exist
Additional Information

IPv4 Address Space

IPv6 Address Space

An IPv6 Address may be entered in either of the following formats:

2001:0db8:0000:0000:0000:0000:20.40.87.171

2001:0db8:0000:0000:0000:0000:1428:57ab

2001:0db8:0000:0000:0000::1428:57ab

2001:0db8:0:0:0:0:1428:57ab

2001:0db8:0:0::1428:57ab

2001:0db8::1428:57ab

2001:db8::1428:57ab

IPv6 Addresses are not supported for some TLDs:

.CA

.CO

.DE

.ES

.NZ

.RU

.WS

Generally, each Child Name Server may have upto 13 unique IP Addresses associated with it.

In case of .CA domain names, each Child Name Server can have only a single IP Address associated with it.

Multiple Child Name Servers can be associated with the same IP Address. However, such Child Name Servers cannot be used together as Name Servers for a .CA domain name.

Example:

You can create Child Name Servers as ns1.yourdomain.ca and ns2.yourdomain.ca and associate them with the same IP Address. However, you cannot use ns1.yourdomain.ca and ns2.yourdomain.ca together as Name Servers for yourdomain.ca.

You can create Child Name Servers as ns1.yourdomain.ca and ns2.yourdomain.ca and associate them with the same IP Address. However, you cannot use ns1.yourdomain.ca and ns2.yourdomain.ca together as Name Servers for yourotherdomain.ca.

In case of a .CN domain name (Anchor: cnrules), an IP Address can be associated with only one Child Name Server. However, each Child Name Server can have multiple such IP Addresses associated with it.

If a particular IP Address is already associated with any other .CN domain name's Child Name Server registered through any Registrar, then it can not be used with any other Child Name Server under any other .CN domain name.

Examples:

Address 66.22.22.22 with it. This Child Name Server would be created only if the IP Address 66.22.22.22 is not already associated with any other .CN domain name's Child Name Server registered through any Registrar.

For .COM.DE (Anchor: comderules) domain names, each Child Name Server may only have a single IPv4 and/or a single IPv6 IP Address associated with it.

Each .DE domain name (Anchor: derules) needs to have at least 2 Name Servers and can have upto 13 Name Servers. The limitation of supporting a maximum of 13 Name Servers is common for both Child Name Servers and Name Servers.

Examples:

If you add 4 Name Servers for your .DE domain name, then you may now add only upto 9 Child Name Servers or Name Servers.

If you add 2 Name Servers and 2 Child Name Servers for your .DE domain name, then you may now add only upto 9 Child Name Servers or Name Servers.

To add a Child Name Server for your .DE domain name, you need to follow the below mentioned process:

In the Zone of your .DE domain name, add an Address (A) Record for the first Child Name Server that you plan to submit for your .DE domain name.

Example:

ns1.myname.de 38400 IN A 111.222.333.444
Additional Information

How to Manage Address Records with Prime?

In the Zone of your .DE domain name, add a NS Record for the above Child Name Server.

Example: In the Zone of myname.de, add a NS Record for ns1.myname.de.

myname.de 38400 IN NS ns1.myname.de
Additional Information

How to Manage NS Records with Prime?

Create a Zone for your .DE domain name on the above Child Name Server. Add the Child Name Server as a Name Server (NS) Record in this Zone as well as Zone created for your .DE domain name on the existing Name Servers. This is required because every Child Name Server that you create/add under a .DE domain name is automatically associated with that .DE domain name as a Name Server.

Example:

myname.de 38400 IN NS ns1.myname.de

Once the above A and NS Records start resolving, add this Child Name Server to your .DE domain name.
Additional Information

Registering and Managing Child Name Servers

Repeat the above steps for any number of Child Name Servers that you wish to add.
Note

You must add one Child Name Server at a time. Otherwise, an error will be encountered.

Example: In order to create a Child Name Server ns1.myname.de, you need to:

add an A Record for ns1.myname.de,

add a NS Record for ns1.myname.de,

create a Zone for myname.de on ns1.myname.de and add ns1.myname.de as a NS Record in this Zone as well as the Zone created for myname.de on the existing Name Servers for myname.de, and

add the Child Name Server ns1.myname.de at the .DE Registry.

Once the Child Name Server ns1.myname.de is thus created, you need to repeat the above 4 steps for ns2.myname.de and so on.

In case of .DE domain names, all Child Name Servers that you create/add are automatically associated with that .DE domain name as a Name Server. Due to this limitation, you will only be able to add upto 13 Child Name Servers for .DE domain names.

The maximum number of Name Servers that can be associated with any .DE domain name is 13. If you have already added other Name Servers (not Child Name Servers of this .DE domain name), then the number of Child Name Servers that you may create would reduce by that many.
Additional Information

Changing Name Servers of a Domain Name

Examples:

yourdomainname.de

Child Name Servers created: ns1.yourdomainname.de and ns2.yourdomainname.de

These Child Name Servers get automatically added as Name Servers as well for this domain name: ns1.yourdomainname.de and ns2.yourdomainname.de

yourotherdomainname.de

Name Servers used: ns1.hostingprovider.com, ns2.hostingprovider.com

Child Name Servers created: ns1.yourotherdomainname.de, ns2.yourotherdomainname.de

These Child Name Servers get automatically added as Name Servers for this domain name: ns1.yourotherdomainname.de, ns2.yourotherdomainname.de

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

This means that now for the domain name yourotherdomainname.de, you may 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 .DE domain name as a Name Server.

The IPv4 Address associated with each Child Name Server of a .DE domain name needs to be unique.

.DE domain names do not support IPv6 Addresses.
Additional Information

.DE Name Servers and Child Name Servers related Rules

In case of .ES domain names (Anchor: esrules), you may associate only a single IPv4 Address per Child Name Server.

In case of .EU domain names (Anchor: eurules), 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.

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 may create would reduce by that many.
Additional Information

Changing Name Servers of a Domain Name

Examples:

yourdomainname.eu

Child Name Servers created: ns1.yourdomainname.eu and ns2.yourdomainname.eu

These Child Name Servers get automatically added as Name Servers as well for this domain name: ns1.yourdomainname.eu and ns2.yourdomainname.eu

yourotherdomainname.eu

Name Servers used: ns1.hostingprovider.com, ns2.hostingprovider.com

Child Name Servers created: ns1.yourotherdomainname.eu, ns2.yourotherdomainname.eu

These Child Name Servers get automatically added as Name Servers 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 may 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.

Apart from the above, in case of .EU domain names, each Child Name Server may have upto 9 unique IP Addresses associated with it.

Example:

You can Register a Child Name Server with the Host Name ns1 for yourdomainname.eu and associate upto 9 unique IP Addresses with this Host Name.

For .IN.NET (Anchor: innetrules) domain names, each Child Name Server may only have a single unique IP Address associated with it.

In case of .NL domain names (Anchor: nlrules), you may associate upto 10 IP Addresses per Child Name Server.

The same IP Addess cannot be associated with multiple Child Name Servers.

in case of .NZ domain names (Anchor: nzrules).

Examples:

Consider a domain name yourdomain.co.nz with Name Servers as ns1.yourdomain.com and ns2.yourdomain.com. The total number of additional Name Servers that can be added under yourdomain.co.nz alongwith any Child Name Servers that can be created under yourdomain.co.nz will be 8.

On a similar note, a domain name yourdomain.co.nz is using its own Child Name Servers ns1.yourdomain.co.nz and ns2.yourdomain.co.nz as its Name Servers as well. Here, the total number of additional Name Servers that can be added under yourdomain.co.nz, taken together with any new Child Name Servers created under yourdomain.co.nz will be 6.

Moreover, each Child Name Server under a .NZ domain name can have only 1 IPv4 Address associated with it.

Example:

You may Register a Child Name Server with the Host Name ns1 for yourdomainname.co.nz and associate only a single IP Address of the form 66.11.11.11 with it.

In case of .RU domain names (Anchor: rurules), all Child Name Servers that you create/add, are automatically associated with that .RU domain name as a Name Server. Due to this limitation, you will only be able to add upto 13 Child Name Servers for .RU domain names.

The maximum number of Name Servers that can be associated with any .RU domain name is 13. If you have already added other Name Servers (not Child Name Servers of this .RU domain name), then the number of Child Name Servers that you may create would reduce by that many.
Additional Information

Changing Name Servers of a Domain Name

Examples:

yourdomainname.ru

Child Name Servers created: ns1.yourdomainname.ru and ns2.yourdomainname.ru

These Child Name Servers get automatically added as Name Servers as well for this domain name: ns1.yourdomainname.ru and ns2.yourdomainname.ru

yourotherdomainname.ru

Name Servers used: ns1.hostingprovider.com, ns2.hostingprovider.com

Child Name Servers created: ns1.yourotherdomainname.ru, ns2.yourotherdomainname.ru

These Child Name Servers get automatically added as Name Servers for this domain name: ns1.yourotherdomainname.ru, ns2.yourotherdomainname.ru

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

This means that now for the domain name yourotherdomainname.ru, you may 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 .RU domain name as a Name Server.

In case of .SX domain names (Anchor: eurules), all Child Name Servers that you create/add, are automatically associated with that .SX domain name as a Name Server. Due to this limitation, you will only be able to add upto 10 Child Name Servers for .SX domain names.

The maximum number of Name Servers that can be associated with any .SX domain name is 10. If you have already added other Name Servers (not Child Name Servers of this .SX domain name), then the number of Child Name Servers that you may create would reduce by that many.
Additional Information

Changing Name Servers of a Domain Name

Examples:

yourdomainname.sx

Child Name Servers created: ns1.yourdomainname.sx and ns2.yourdomainname.sx

These Child Name Servers get automatically added as Name Servers as well for this domain name: ns1.yourdomainname.sx and ns2.yourdomainname.sx

yourotherdomainname.sx

Name Servers used: ns1.hostingprovider.com, ns2.hostingprovider.com

Child Name Servers created: ns1.yourotherdomainname.sx, ns2.yourotherdomainname.sx

These Child Name Servers get automatically added as Name Servers for this domain name: ns1.yourotherdomainname.sx, ns2.yourotherdomainname.sx

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

This means that now for the domain name yourotherdomainname.sx, you may 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 .SX domain name as a Name Server.

Apart from the above, in case of .SX domain names, each Child Name Server may have upto 10 IP Addresses associated with it.

Example:

You can Register a Child Name Server with the Host Name ns1 for yourdomainname.sx and associate upto 10 IP Addresses with this Host Name.

Child Name Servers can not be created under a .TEL domain name (Anchor: telrules), due to restrictions placed by the Registry.

In case of .UK domain names (Anchor: ukrules), each Child Name Server can have only a single unique IP Address associated with it.

Example:

You can Register a Child Name Server with the Host Name ns1 for yourdomainname.co.uk and associate only a single unique IP Address with this Host Name.

For CentralNic (Anchor: crules) domains, each Child Name Server may only have a single IPv4 and/or a single IPv6 IP Address associated with it.
Additional Information

Identifying CentralNic Domains
Modify a Child Name Server (Anchor: modify)

.AU Specific Condition
Note

.AU domain names do not support modification of a Child Name Server. You need to instead delete the existing Child Name Server and add another.
Additional Information

Instructions for Deleting a Child Name Server

Instructions for Adding a Child Name Server

Modifying the Hostname: Make the modifications in the Host Name textbox and click the Save button.
Domain Name Extension Specific Conditions
Note
Modification of the Hostname of a Child Name Server under a .ES domain name is not allowed.

Modification of the Hostname of a Child Name Server under a .NL domain name is not allowed.

If you modify the Hostname of a Child Name Server under a .NZ domain name, you need to manually make necessary modification to the domain name(s) using the original Child Name Server.

Example

Consider a domain name yourdomain.co.nz with a Child Name Sever as ns1.yourdomain.co.nz, which is being used as a Name Server for yourdomain.co.nz. If you modify the Hostname for ns1.yourdomain.co.nz from ns1 to ns2, you need to manually modify the Name Server for yourdomain.co.nz from ns1.yourdomain.co.nz to ns2.yourdomain.co.nz.

Modifying the IP Address: Make the modifications in the IP Address textbox and click the Save button.
Errors, IPv6 Format and IPv6 Support
Note

You will encounter the below error message in case an invalid or reserved IP Address is used:
Attention

Object does not exist
Additional Information

IPv4 Address Space

IPv6 Address Space

An IPv6 Address may be entered in either of the following formats:

2001:0db8:0000:0000:0000:0000:20.40.87.171

2001:0db8:0000:0000:0000:0000:1428:57ab

2001:0db8:0000:0000:0000::1428:57ab

2001:0db8:0:0:0:0:1428:57ab

2001:0db8:0:0::1428:57ab

2001:0db8::1428:57ab

2001:db8::1428:57ab

IPv6 Addresses are not supported for some TLDs

.CA

.CO

.DE

.ES

.NZ

.RU

.WS

Delete a Child Name Server (Anchor: delete)

Click the Delete link to delete individual Child Name Servers.
Errors and Restrictions
Note

You will encounter the below error message while deleting a Child Name Server if this is being used by another domain name of the same extension as a Name Server:
Attention

Object association prohibits operation

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

You will need to modify the Name Servers of all domain names using the Child Name Server as their authoritative Name Server and try attempt the Child Name Server deletion.

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.

Deletion of a Child Name Server under a .ES domain name is not allowed.

Deletion of a Child Name Server under a .UK domain name is not allowed.

Error due to Lock / Suspension / Outbound Transfer
Note

You will encounter the below error message in case the domain name is either:

Locked/Suspended at the Registry (and not under our system), or

a Transfer Away for the domain name to another Registrar is under process.

Attention

Domain Status does not allow this operation.

If you wish to modify/delete your domain name's Child Name Server in these circumstances, you have the following solutions:

Lock/Suspension applied at the Registry: Contact our Support Team at https://h.osspl.com to know the reason for Lock/Suspension and how this Lock/Suspension may be removed.

While a Transfer Away is under process:

Cancel the Transfer through the link listed in the email sent to the Registrant/Administrative Contact of the domain name and then perform the required modification, or

Wait for the Transfer to complete and then carry out the desired modification at the New Registrar.

Support Knowledge Base Wiki.

Here, we have listed information on our current web products and services and answers to possibly all your queries or faqs. This Support Wiki cum KnowledgeBase has been divided into categories indicating a particular interface or a particular product or service offering. These have been further logically divided into sub-categories and answers, detailing a particular action or guide.

If you are unable to locate your answer, please use search box provided on each page or inform our support team.

[[Category: Control Panel]]
[[Category: Domain]]
[[Category: Business Email]]