# DNS question **URL:** \ **Category:** Self-hosting\ **Created:** [May 25, 2023, 5:00pm UTC](https://meta.discourse.org/t/dns-question/266235 "2023-05-25T17:00:53Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![maiki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maiki/32/233950_2.png) [@maiki](https://meta.discourse.org/u/maiki)\ **Post date:** [May 26, 2023, 6:20pm UTC](https://meta.discourse.org/t/dns-question/266235/5 "2023-05-26T18:20:44Z")
> [@agf1997](#): > > I’d like to do this to effectively reserve the root for the future use of another service (say a webserver), but not require users to type in the subdomain to get to the discourse server for now. I’ve done this a bunch in the past, and one “gotcha” I always run into is **http** ://example.org → **https** ://discourse.example.org. Depending on the redirect, it can lead to messages in the browser saying it is trying to connect to an insecure website. To get around this I use a redirect service that provisions an SSL cert for the redirect, via my registrar at Gandi. They call it “[web forwarding](https://docs.gandi.net/en/domain_names/common_operations/web_forwarding.html)”. Make sure to test your redirect using different protocols (HTTP and HTTPS) to see how it works for your site visitors. 🙂 --- _[View the full topic](https://meta.discourse.org/t/dns-question/266235)._