David from Russia

So apparently, I’m so good at job hunting that scammers are now creating brand‑new domains just to talk to me. This week, I was “recruited” by someone pretending to be from Calspan using the domain calspancareers.com ... which, fun fact, was created 48 hours before they emailed me. Yes. Two. Days. This scammer domain was basically still wearing its hospital bracelet. They sent me a whole questionnaire, job description, fake HR guy named “Richard Bowman” (who exists nowhere except maybe in a fanfiction forum), and expected me to just… go with it. Unfortunately for them, I have this annoying habit called checking things. So here’s what happened next: 🟢 Contacted the REAL Calspan 🟢 Reported the scam to the FTC 🟢 Reported it to the FBI 🟢 Reported the domain to the registrar 🟢 Verified the WHOIS data 🟢 Confirmed the domain was younger than a loaf of bread 🟢 Whispered “ #getfucked ” like a cybersecurity monk achieving enlightenment Honestly, at this point I’ve done more incident resp...

  If there’s one service that quietly makes or breaks an IT environment, it’s DNS . It’s the first thing users blame on “the Wi‑Fi,” the last thing junior techs check, and the root cause of more “mystery issues” than almost anything else in infrastructure. So, for the first entry in this rebooted newsletter, let’s get back to basics and back to best practices. Why DNS Matters More Than You Think DNS is the phonebook of your environment. If it’s slow, wrong, or misconfigured: Logins fail Apps time out Group Policy doesn’t apply Cloud services break Users swear the network is down And the worst part? Everything looks fine until you dig deeper. Everyday Best Practices for DNS 1. Always Use Internal DNS for Domain‑Joined Devices This is the #1 mistake in small and mid‑sized environments. If a domain‑joined machine uses Google DNS (8.8.8.8) or Cloudflare (1.1.1.1), expect: Slow logins Broken GPO Random authentication failures Azure AD / Entra ID sync issues Fix: Internal DNS → Forwar...