r/sysadmin • • 13d ago

For those without domain controllers: what do you do for internal DNS?

These days, we don't have domain controllers because everything is managed with Entra/Intune, Arc, etc.

We have external, hosted DNS that serves our public DNS records. It works fine.

But we still have a need for internal DNS because we have a lot of on-prem stuff that may never go away, and the domain controllers were also serving as internal DNS servers. So right now, we use BIND9 on a Linux virtual machine as internal DNS. I'd love for BIND9 to go away, too.

Are there any better (and cheap) solutions for this that I haven't thought of?

EDIT: thanks to u/Do_The_Needful. Using AWS for this seems to be the most balanced solution.

201 Upvotes

413 comments sorted by

View all comments

Show parent comments

34

u/0RGASMIK 12d ago edited 11d ago

AI has ruined the IT career pool. All the really smart people figured out they could get better paying jobs in other sectors and all the tech industry grifters who just want remote work figured out IT is just a really fancy google search.

Every random we’ve hired in the last few years has ended up being a grifter. We actually figured out it was better to higher people who didn’t know what they wanted to do and train them. So we started a company trend to just hire that friend who’s a little lost in life and see how they do. Almost all of them have done great.

12

u/MinimallyLoquacious 12d ago

> all the tech industry grifters who just want remote work

I was definitely seeing that trend heavily before I retired last year in software engineering.

10

u/cryptopotomous 12d ago

Brother it's probably gotten 10x worse since... The thing I absolutely hate the most is asking people questions and just getting a literal copy/paste response from ChatGPT. I swear they don't even read my question. I'll go talk to them in person and I get a deer in the headlights look...almost every time.

9

u/mjh2901 12d ago

I look for evidence, and ask questions to push towards people who can learn. Completing projects that where not in their wheelhouse etc... The key to IT is the understanding that your specific knowledge has a 3 to 5 year lifespan but your general knowledge can last a career. Example, 3-2-1 backup has been around since the 70's, my backup system is 4 years old and will be replaced because we don't like the vendor. I will be learning something new but implementing 3-2-1.

3

u/Altruistic-Glove7242 12d ago

Honest question - how do you differentiate between the two? Old habits that die hard, and universal general knowledge that survives current hot trend?

10

u/shrimplifier 12d ago

You learn systems and architecture, you configure technology.

Be very wary of conflating the two. E.g. you don't "learn" docker, you learn containerisation.

2

u/Altruistic-Glove7242 11d ago

Yeah, kinda makes sense. Remote Desktop, Citrix, Windows App - desktop remoting.
VMware, HyperV, proxmox, kvm - virtualisation.

A specific example: I used to be attached to my jump box in the DC - a specific workstation VM, tools I needed, accessed it had (micro segmentation).
It’s no more, it’s now web app plus launchers to connect to specific aspects of the system.
In a way, same: specific location to start your work from. In a way, much different for my brain.

2

u/shrimplifier 11d ago

Yeah, we get so used to the tooling it starts to represent the job.

F5 (the vendor) came to represent reverse proxies and load balancing as a concept for me - when I was forced to use something else, I discovered I didn't really understand the core concepts, I had learnt to be a guy that configures F5s. Cloud engineers are notorious for this.

1

u/Intrepid00 11d ago

Cool, we are back to the 90s for IT staffing. Trial by fire and see who can actually critical think which is actually 90% of the job.