92
edits
Setting Up Wildcard Subdomains with SSL on a Debian Application: Difference between revisions
Jump to navigation
Jump to search
m
Setting Up Wildcard Subdomains with SSL on a Debian Application (view source)
Revision as of 01:36, 31 October 2024
, 31 October 2024no edit summary
(Created page with "This guide provides a step-by-step approach to setting up wildcard subdomains with SSL on a Debian-based application. Wildcard subdomains allow applications to dynamically support multiple subdomains (abc.example.com, xyz.example.com) under a single SSL certificate. In this guide, the focus is on configuring a Debian package to handle wildcard subdomains primarily through updates to the debian/postinst file. The guide uses the ''kaboom-api'' app as an example, with `sta...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
This guide provides a step-by-step approach to setting up wildcard subdomains with SSL on a Debian-based application. Wildcard subdomains allow applications to dynamically support multiple subdomains (abc.example.com, xyz.example.com) under a single SSL certificate. | This guide provides a step-by-step approach to setting up wildcard subdomains with SSL on a Debian-based application. Wildcard subdomains allow applications to dynamically support multiple subdomains (abc.example.com, xyz.example.com) under a single SSL certificate. | ||
In this guide, the focus is on configuring a Debian package to handle wildcard subdomains primarily through updates to the debian/postinst file. The guide uses the ''kaboom-api'' app as an example, with | In this guide, the focus is on configuring a Debian package to handle wildcard subdomains primarily through updates to the debian/postinst file. The guide uses the ''kaboom-api'' app as an example, with <code>staging-elearning.nl</code> as the domain name on which we’re setting up wildcard subdomains. | ||
If you do not need or prefer not to modify the application code itself, you can still follow the key steps and commands described in this guide directly from the terminal. This will allow you to set up SSL for wildcard subdomains without diving into the application’s Debian packaging configuration. | If you do not need or prefer not to modify the application code itself, you can still follow the key steps and commands described in this guide directly from the terminal. This will allow you to set up SSL for wildcard subdomains without diving into the application’s Debian packaging configuration. | ||
By the end of this guide, you will have a fully automated process for configuring and renewing SSL certificates for wildcard subdomains, leveraging tools like Certbot and DNS authentication. | By the end of this guide, you will have a fully automated process for configuring and renewing SSL certificates for wildcard subdomains, leveraging tools like Certbot and DNS authentication. | ||
== Prerequisites == | |||
=== 1. DNS Configuration for Wildcard Subdomains === | |||
Access your DNS repository and add the necessary A and AAAA records for the wildcard subdomain you plan to use. This typically involves adding entries like <code>*.example.com</code> pointing to your server’s IP address. | |||
The following is an example of what has been done for the domain name <code>staging-elearning.nl</code> | |||
<code>staging-elearning.nl.zone</code> | |||
<pre> | |||
$ORIGIN staging-elearning.nl. | |||
$TTL 3600 | |||
@ IN 3600 SOA delftsolutions.ns1.signaldomain.nl. info.signaldomain.nl. ( | |||
<serial> ; don't modify, auto incremented | |||
86400 ; secondary refresh | |||
7200 ; secondary retry | |||
3600000 ; secondary expiry | |||
600 ; negative response ttl | |||
) | |||
@ 3600 IN NS ns2.signaldomain.net. | |||
@ 3600 IN NS delftsolutions.ns1.signaldomain.nl. | |||
* IN 3600 A 193.5.147.172 | |||
* IN 3600 AAAA 2a0c:8187:0:201::196 | |||
</pre> | |||