does anyone have any recommendations on picking up ideas for best practice & managing DNS ? I'm looking to improve how we do it now but it's not something i've ever needed to touch before (outside of windows anyhow). At the moment we're just a mess of masters, slaves, and recursive servers for domains and sub domains. There's like 17 machines involved in serving a total of ~500 records.
I want to do it better (simpler, cleaner, and more importantly ourselves - currently its farmed off to another team), but i'm not really able to find a good source of wisdom on running such a setup - gotchas, that type of thing.
the only books i can find are 'how' not 'why' really. Books on configuring bind and such.
no kidding. by the time we've allowed for geographic redundancy, and masters which control a sub domain (each with their own 2 slaves).... its just a mess. I'm in that awkward position where you smell bullshit but don't know enough on the topic to call it out. I'm pretty sure this isn't normal though. I really want to get this sorted before we ever think about ipv6 though.
we've got 1 machine which goes to 2 others, each to 2 others, 2 of those 4 go to 2 others. then there's 3 more which do one sub zone. I'm meant to be implementing dynamic updates on this lot and then it's 'well, you need to be able to update it here, or here... or maybe here also'.... then there's split horizon to think about and ....ugh.
i get how to configure bind more or less (id rather use powerdns i think), but i'm aware once i rubberstamp this setup and take over ownership of it i'll never get time to fix it due to fire fighting it.
ah... bind. I'm not DNS expert, if I had to architect this out I'd go after availability and geographic reachability, and then attack a DNS configuration that lets it replicate and play nice across them
personally, i'd build new, and move the domains one at a a time
you'd painfully learn how they all work, but then you'd be squarely solid.
at one point i was thinking 'ya know, screw the complexity and replication, just have one static config and use bittorrent sync to replicate it'. then just cookie cutter dns servers as needed off that. But i'm aware of noone doing that, ever - which is probably a bad sign :)
@JourneymanGeek yeah that was my thinking I guess. I don't mind it being non neckbeardy that's a plus in my book. non enterprise is a little more troublesome. I just wondered if anyone does dns and deals with replication as a separate issue. seems like dns doesn't really need that in the protocol these days. adds tons of complexity for what it gives you.
sorry, no, i do not have access to create my generic ones from here, additionally i do not think i will ever use something like that unless i am forced to. i like having things seperated.
It depends what you want out of Serverfault. It'll continue to provide impressions for years I'm sure now that SE appear to have basically given up on quality.
If you want quality interactions with peers and not amateurs then it's probably not performed for some considerable time
Does anyone know if I can have multiple VirtualHosts running in Apache on the same subdomain? I.e. I'd like to have it check /var/www first, and if that 404's then fall back on Passenger/rails.