Techniques for templated domain management

1. A computer-implemented method, the method comprising:

receiving, from a requester, a Domain Name System (DNS) request specifying a domain;

determining a type of the DNS request; and

sending, to the requester, a response including a predefined Internet Protocol (IP) address that is determined based on the type of the DNS request and not on the domain specified in the DNS request.

2. The computer-implemented method of claim 1 , wherein the type of the DNS request is A, and the predefined IP address comprises a 32-bit IP address.

3. The computer-implemented method of claim 1 , wherein the type of the DNS request is AAAA, and the predefined IP address comprises a 128-bit Internet Protocol version 6 (IPv6) address.

4. The computer-implemented method of claim 1 , further comprising inserting the domain into one or more portions of a DNS response that includes the predefined IP address.

5. The computer-implemented method of claim 1 , wherein the predefined IP address is associated with a templated HyperText Transfer Protocol (HTTP) server that responds to HTTP requests and Hypertext Transfer Protocol Secure (HTTPS) requests with redirection responses.

6. The computer-implemented method of claim 1 , further comprising configuring a domain name registrar to delegate the domain to a templated DNS nameserver that performs the receiving, determining, and responding steps.

7. The computer-implemented method of claim 6 , further comprising configuring the domain name registrar to delegate at least one other domain to the templated DNS nameserver.

8. The computer-implemented method of claim 1 , wherein the domain includes a misspelling of another domain.

9. A computer-implemented method, the method comprising:

receiving, from a client application, a first request specifying a first hostname;

in response to determining that the first request is a Hypertext Transfer Protocol Secure (HTTPS) request:

determining whether the security certificate associated with the first hostname is stored in a cache and has not expired,

if the security certificate is stored in the cache and has not expired, transmitting the security certificate stored in the cache and a redirection response to the client application, and

if the security certificate is not stored in the cache or a stored security certificate has expired:

generating the security certificate,

storing the security certificate in the cache, and

transmitting the security certificate and the redirection response to the client application; and

in response to determining that the first request is a HyperText Transfer Protocol (HTTP) HTTP request, transmitting the redirection response to the client application.

10. The computer-implemented method of claim 9 , wherein the redirection response specifies a default Universal Resource Locator (URL) that is not determined based on the first hostname.

11. The computer-implemented method of claim 9 , wherein the redirection response specifies a Universal Resource Locator (URL) overriding a default URL that is not determined based on the first hostname.

12. The computer-implemented method of claim 9 , wherein generating the security certificate comprises:

requesting the security certificate from a certificate authority; and

notifying a templated Domain Name System (DNS) nameserver to respond to a DNS request from the certificate authority with a secret code.

13. The computer-implemented method of claim 9 , wherein generating the security certificate comprises requesting the security certificate from a certificate authority, and satisfying a HTTP-based challenge by the certificate authority.

14. The computer-implemented method of claim 9 , wherein:

the receiving, determining, transmitting, and generating steps are performed by a templated HTTP server; and

the client application obtains an Internet Protocol (IP) address associated with the templated HTTP server from a templated Domain Name System (DNS) nameserver that responds to DNS requests with IP addresses associated with the templated HTTP server based on types of the DNS requests.

15. The computer-implemented method of claim 9 , further comprising:

receiving a second request specifying a second hostname;

determining that the second hostname matches a predefined hostname; and

not transmitting a security certificate or redirection response in response to the second request.

16. A system, comprising:

a templated Domain Name System (DNS) nameserver that, when executed on a first computing device, processes DNS requests by performing the steps of:

receiving a DNS request specifying a domain,

determining a type of the DNS request, and

responding to the DNS request with a predefined Internet Protocol (IP) address that is based on the type of the DNS request, wherein the predefined IP address is associated with a tem plated HyperText Transfer Protocol (HTTP) server; and

the templated HTTP server that, when executed on a second computing device, processes HTTP requests and Hypertext Transfer Protocol Secure (HTTPS) requests by performing the steps of:

receiving a request specifying a hostname, and

responding to the request with a redirection response.

17. The system of claim 16 , wherein, when templated DNS nameserver responds to the DNS request, the domain is not mapped to the predefined IP address.

18. The system of claim 16 , wherein the request is transmitted by a client application to the templated HTTP server subsequent to receiving the predefined IP address from the templated DNS nameserver.

19. The system of claim 16 , wherein a domain name registrar delegates the domain to the templated DNS nameserver.

20. The system of claim 16 , wherein the domain includes a misspelling of another domain.