Skip to content

Commit 740e8cf

Browse files
authored
Merge pull request openshift#7562 from ahardin-rh/enterprise-3.9-stage
[enterprise-3.9] Added an Update DNS for Custom Routes section for On…
2 parents 6ca2ecf + bf0bc19 commit 740e8cf

File tree

2 files changed

+11
-2
lines changed

2 files changed

+11
-2
lines changed
Loading

dev_guide/routes.adoc

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -348,8 +348,11 @@ custom hosts or certificates will be rejected in {product-title} Starter. In
348348
{product-title} Pro, a default host is provided if the user does not specify a
349349
custom host.
350350

351-
Once your custom route is created in in {product-title} Pro, you must update
352-
your DNS provider by creating a canonical name (CNAME) record. Your CNAME record
351+
[[update-dns-for-custom-routes]]
352+
== Update DNS for Custom Routes
353+
354+
Once your custom route is created in {product-title} Pro, you must update your
355+
DNS provider by creating a canonical name (CNAME) record. Your CNAME record
353356
should point your custom domain to the {product-title} router as the alias. The
354357
{product-title} router's domain is different for every cluster.
355358

@@ -358,4 +361,10 @@ should point your custom domain to the {product-title} router as the alias. The
358361
CNAME records cannot be set for a naked domain (`example.com`). A subdomain must
359362
be specified (`www.example.com`).
360363
====
364+
365+
In {product-title} Pro, you can view a created custom route to see the CNAME
366+
record that you must provide to your DNS provider.
367+
368+
image::update-dns-for-custom-routes.png[View a created custom route to see the CNAME record]
369+
361370
endif::[]

0 commit comments

Comments
 (0)