Hi, I am reconfiguring my home network, and one thing that always bothered me was my domain name setup using just foo or foo.local.
I am considering the following;
I have a publicly registered domain, with a public DNS server, let's call it foo.net.
I have a paid class 2 validation with StartSSL, so I can issue certificates for any hosts and subdomains of foo.net, e.g. *.home.foo.net and *.foo.net. (I am currently using this for Hyper-V replication over HTTPS and using the hosts file to resolve FQDN's)
I want to use home.foo.net as my home DNS domain, e.g. server-1.home.foo.net.
I want to use my own DNS server to resolve *.home.foo.net, and forward all other requests to my upstream ISP (or Google) DNS server.
To recap, the primary reason for using a public domain is to allow me to issue SSL certificates by a public registrar, i.e. no need to create and distribute my own root certificates.
Any concerns, gotchas, good idea, bad idea?
P.
I am considering the following;
I have a publicly registered domain, with a public DNS server, let's call it foo.net.
I have a paid class 2 validation with StartSSL, so I can issue certificates for any hosts and subdomains of foo.net, e.g. *.home.foo.net and *.foo.net. (I am currently using this for Hyper-V replication over HTTPS and using the hosts file to resolve FQDN's)
I want to use home.foo.net as my home DNS domain, e.g. server-1.home.foo.net.
I want to use my own DNS server to resolve *.home.foo.net, and forward all other requests to my upstream ISP (or Google) DNS server.
To recap, the primary reason for using a public domain is to allow me to issue SSL certificates by a public registrar, i.e. no need to create and distribute my own root certificates.
Any concerns, gotchas, good idea, bad idea?
P.