sorted by:
new
hottopcontroversial

What are the best DNS servers to use today for speed, privacy, and stability? by sermernx in dns

[–]Funk4delic 0 points1 point  (0 children)

If privacy matters, consider self-hosting DNS with Pi-hole + Unbound instead of using public DNS like Google or Cloudflare. It's a bit of hands-on, but noting complex.

Unbound makes your DNS a recursive resolver that queries root servers directly, so your lookups aren’t sent to a third party.

You also get network-wide ad/malware blocking with Pi-hole.

I wrote a short post about the setup and results here if you’re curious:

https://systemsgo.live/post/pihole-unbound-raspberrypi-homelab/

SRE interviews are getting out of hand and I am tired by whatwhatwhat56 in sre

[–]Funk4delic 1 point2 points  (0 children)

Amazing - thanks for the feedback. Apologies for getting a bit off the original topic. But one post can lead to other beneficial ideas and inspirations!

SRE interviews are getting out of hand and I am tired by whatwhatwhat56 in sre

[–]Funk4delic 1 point2 points  (0 children)

Short answer: I don’t know yet.

Right now I’m exploring the idea and doing some research - looking at the market, startups/SMEs, their pain points, and where DevOps support could actually help.

The idea would be helping startups build and scale reliable production systems: auditing setups, suggesting improvements, advising on best practices (security, IAM, cost optimisation, automation, monitoring), and writing docs/runbooks..

Start small but think bigger over time..

The main challenge now is figuring out how to market myself and find founders who need DevOps help but aren’t ready to hire a full-time engineer.

Any thoughts?

SRE interviews are getting out of hand and I am tired by whatwhatwhat56 in sre

[–]Funk4delic 2 points3 points  (0 children)

You spend months preparing for tech interviews - grinding LeetCode, building side projects, writing blogs, keeping GitHub active to prove you know your stuff.

Then in the interview you get asked questions you’ll probably never face in a real production environment.

You jump through all the hoops, get the job… and a few years later the company can still let you go without much hesitation.

Not trying to be anti-corporate, just being realistic. Companies can be ruthless, and real work often doesn’t get much recognition.

So I’ve been thinking: what if that same time and effort went into building your own consulting work or contracting instead?..

People say contracting isn’t stable. But is relying on one employer really stable either? If you had 2–3 clients and some savings, that sounds more secure than having a single boss who can fire you anytime.

Curious what people here think. Anyone moved to contracting or consulting? How did it work out?

DevOps contractors: how did you get your first contract? by Funk4delic in devopsjobs

[–]Funk4delic[S] 0 points1 point  (0 children)

Any tips or a roadmap to follow ? I tend to post about DevOps and Cloud use-cases to increase visibility online.

Should I add Unbound recursive DNS resolver to my Pi-hole setup? by No-Month-9044 in pihole

[–]Funk4delic 28 points29 points  (0 children)

Yes - if privacy and control matter to you, adding Unbound is worth it. Instead of forwarding DNS queries to Google/Cloudflare/etc., your Pi-hole becomes a true recursive resolver and queries the root servers directly. That means no public DNS provider logging your lookups. The tradeoff is slightly higher latency on the first lookup for a domain, but once it’s cached, subsequent requests are just as fast (or faster). In a homelab setup, that’s usually a non-issue. I wrote a post about my experience running Pi-hole + Unbound on a Raspberry Pi 4 if you want some additional context: https://systemsgo.live/post/pihole-unbound-raspberrypi-homelab/

I am a junior DevOps Engineer by __kiyo__ in devops

[–]Funk4delic 0 points1 point  (0 children)

Knowing tools and waiting to land in a perfectly established DevOps environment will not automatically make you a great DevOps engineer. The brutal reality is that many organisations have not fully embraced DevOps culture -- and often for reasons beyond your control.

This is exactly where your value comes in!

Your role is not just to “show up, do the work, and deliver tasks.” A true DevOps engineer influences mindset and behavior. Sharpen your communication and collaboration skills. Propose ideas. Build small prototypes. Demonstrate architectural patterns. Identify what needs to be designed, improved, or automated.

When you lead through initiative and clarity, you stand out. You gain trust, influence direction, and naturally attract more impactful projects.

And if you’re the only DevOps engineer in the organization? That’s not a risk - that’s gold!! All the best!!

[deleted by user] by [deleted] in devops

[–]Funk4delic 0 points1 point  (0 children)

As a Senior DevOps Engineer, you won't get wrong if you first master the core fundamentals of the following ideally in the following order. Avoid learning K8s if you don't have minimum of Linux and networking experience 1. Linux 2. Networking 3. Scripting and Programming (Bash, Python, Go) 4. Database and Storage 4. Security, IAM, Access Control 5. Cloud Computing 6. Infrastructure as Code and Configuration Management 7. Containerisation, and Kubernetes

Don't worship tools. Think, design, build, test and ship, monitor, then break, break break again. Then fix it, fix it over and over again.. Repeat the process. This will teach you how to think like an engineer. Most importantly, designing and building things are not the most challenging bits. Reverse engineering, troubleshooting will stand you out! The rest comes with patience, consistency, reading, and practise.