Since I'm off this week, today's project is to figure out my proxy server. I've already set it up to some degree, but I need to finish it out. Goal is to get it set up and finished by Wednesday, though I doubt it'll take that long. :blobfoxbongo:
Okay, so I can't CNAME the root of my domain like I wanted to, and I don't think I'll be able to get around handing control of the whole zone file over to BIND. The point of my struggle was to separate out the dynamic update (and BIND's gross auto-formatting) from the "static" stuff that I don't want changing automatically.
I've settled on having a "static" file that I make updates to, manually push over to the path BIND uses, and forcing it to re-sync. I may script something smarter later, but this satisifies my OCD for now.
Gonna go run (NOW FAO, NOT LATER) and work on setting up the secondary later. Also on the list: XoT and DNSSEC.
Well, I think I have laid out almost everything I want to set up in BIND. Still trying to figure out a few things:
1) Use a separate zone (or zones) subdomains that gets dynamically updated. I also want to CNAME my root domain to one of them (assuming I can? Basically I'm trying to use a dynamic IP for my root domain without letting BIND reformat my whole zone file).
2) Set up my secondary server with zone transfer over TLS. I worked on this earlier, but I ran into difficulty in getting the certificate. I'm not even sure what domain to fetch the cert for. Does it even need to be issued by a CA? There's so little documentation on XoT in BIND, let alone examples.
Turns out I didn't have to do either. I can bypass the reverse proxy by using a separate subdomain. Not sure if I'd prefer it to go through the proxy... maybe it should. But for now, it works and I'm happy enough with it.
Time to go run, and then I'll try tackling DNS. Whee~
So after getting my proxy going, I now have kind of a weird setup where my web server and turn server are hosted on the same backend, but the turn server isn't using the proxy. Like so:
NAT (443) => Proxy => Backend server => Web service NAT (coturn port) => Backend server => Turn service
And for some reason it doesn't work. But if I revert to the previous configuration without the proxy, it works.
@faoluin if you care about DNS security make sure you have 3 different NS running in 3 different AS running 3 different implementations of DNS (this is what Verisign does but at an even crazier level)
@feld I considered PDNS, but stuck with BIND because I guess I'm a masochist. |3 Might keep PDNS in the back of my mind for when I get fed up with BIND though.