=== jelly-home is now known as jelly [14:52] Holla [14:53] I am wanting to run my own dynamic dns style thing, ideally one that will natively use a mysql database for its records [14:53] any dbms is fine in reality tho - it's for an in house dyndns style thing for our subdomains [14:54] using mysql just makes it easier because that's what that servers other stuff already uses [14:54] and a database so that I can manipulate it quickly and easily from software [14:55] it'll be a memory persistant table so dns queries will still be fast [14:55] just need to find the best dns server for the task [14:55] It never has to do any other routing or anything even so maybe even write a script or a light script already exists? [14:56] idk [14:56] an index.php would be very simple that all subdomains get routed to [14:56] via apache2 config [14:57] but that /would/ be slow without somehow getting apache2 to reuse a worker pool just for that... urgh [14:58] I guess I can do that now i've talked it out... A plug n play solution would have been good but would probably take more work to make that how I wanted [15:00] EddyKid: closest thing I think you could get is PowerDNS with a MySQL backend, but that's not a custom solution. And you require the proper items to do the DNS. https://blog.heckel.io/2016/12/31/your-own-dynamic-dns-server-powerdns-mysql/ might get you close but it's not vetted (and I don't like PowerDNS) [15:01] Yeah the only real thing about this is that it will require a worker pool maintained as I said; how much dns is enough dns lol [15:01] etc [15:02] I can probably even do a timeout and stuff [15:02] I'm no apache-spert === EddyKid is now known as IdiotSandwich [15:13] well i think the question is exactly what're you using it for, for a few machines i doubt you'll have a resource problem, if you intend to set up a full blown publicly usable dynamic DNS service then you're going to need to build out the infra [15:13] and probably write a solution yourself and preconfigure a few things like DynDNS has. [15:13] It actually doesn't seem entirely crazy for there to be a native dns add on for apache/nginx/whatever... [15:13] that's a much larger project ;) [15:13] DNS != Web Application [15:13] lol.. [15:13] they don't speak the same language. [15:14] I am aware.. [15:14] 20 years dev'ing ;p [15:15] I'm just saying for extremely light weight work, but moreso than a typical php script worker pool - run one natively as an apache/etc extension which is self-managed [15:16] I could personally even do dns-over-https [15:16] but that wouldn't be for everyone ofc [15:17] and it's definitely quite small to start with but each instance of will need to support atleast a few hundred entries - not massive haha [15:17] The centralized part needs records from all say, 300 "servers" it "manages" [15:18] (airquotes because it could well be cloud based with central storage in the end) [15:19] it's server<=>server too if that helps [15:21] idk I think even just to start with I'll literally just do the routing to a php script which can have concurrent requests [15:21] it's super dumb [15:22] or node.js, but that has heavier less dynamic startup times [15:22] ie php only loads what it needs to load not what MIGHT be required, node.js does this entirely at load [15:25] i think your discussion of 'best practices' belongs elsewhere as it's not an Ubuntu question or Ubuntu Server specific discussion [17:20] Nobody can help me? [17:21] oops [17:21] wrong channel === StathisA_ is now known as StathisA === StathisA_ is now known as StathisA === StathisA_ is now known as StathisA