Skip to content

Latest commit

 

History

History
47 lines (35 loc) · 2.49 KB

start-with-subdomain.md

File metadata and controls

47 lines (35 loc) · 2.49 KB
Raw
copyright lastupdated keywords subcollection
years
2019, 2020
2020-07-06
IBM Cloud Internet Services, subdomain, CNAME
cis

{{site.data.keyword.attribute-definition-list}}

Getting {{site.data.keyword.cis_short_notm}} running with a new subdomain

{: #get-started-new-subdomain}

Follow these steps to practice using {{site.data.keyword.cis_short_notm}} with a subdomain or CNAME. This example uses the GoDaddy domain registrar. Your case might be different, depending on which registrar you use. {: shortdesc}

  1. Deploy a {{site.data.keyword.cis_short_notm}} instance by using the {{site.data.keyword.cloud_notm}} console or API.

    It is recommended that you mirror the name of your {{site.data.keyword.cis_short_notm}} instance with the domain or subdomain. {: note}

  2. Click Let’s get started.

  3. Enter the subdomain in the Domain name field and click Connect and continue.

  4. For new subdomains click Next Step, for existing subdomains click Import records.

  5. Make note the New NS records for entry into the GoDaddy DNS Management system.

  6. Log in to GoDaddy domain Registrar.

  7. Navigate to the DNS Management page for the candidate {{site.data.keyword.cis_short_notm}} domain. {{site.data.keyword.cloud}} must be updated through the API.

  8. Click ADD to create an NS Host record for each name server entry provided from {{site.data.keyword.cis_short_notm}}.

  9. Set up a DNS record with the supplied {{site.data.keyword.cis_short_notm}} NS Records

    • Type Nameserver
    • Host subdomain (the name of the subdomain, for example, subdomain.example.com)
    • Points to ns004.name.cloud.ibm.com
    • TTL ½ hour

  10. The DNS Management page now reflects the two new NS records for the subdomain.

  11. Go back to the {{site.data.keyword.cis_full_notm}} instance.

  12. After the NS Records are DNS propagated, it is reflected in the DNS tools, and you are ready to proceed.

  13. With completed NS propagation, click Check name servers.

  14. {{site.data.keyword.cis_short_notm}} starts checking NS configuration for the subdomain and might be in a Pending State.

    Any typographical errors in can produce a "silent" failure. If your subdomain is in the pending state for more than 30 minutes, you might have an error. {: note}

Upon successful subdomain name server and NS record confirmation, the {{site.data.keyword.cis_short_notm}} instance reports Active. Customers are now ready to start configuring the service and routing traffic to their services.