• EdgarallenpwnEnglish
    33•6 months ago

    Why is it usually DNS?

    (Network outages at work today. Guess what it was?)

    • @grandkaiser@lemmy.worldEnglish
      42•6 months ago

      DNS engineer here.

      It’s always DNS because no one wants to hire us. We’re prima donnas that don’t work much and demand large salaries. Companies think they can get away with having some random network guy “learn a bit of DNS” and it works!!.. For a while… Then it fails catestrophically and the DNS engineer that was let go to “save costs” smugly watches them crash and burn. The job is super easy and simple until you’re 48 hours into troubleshooting and the CTO is lighting money on fire trying to get the network back online. A big company can easily burn a DNS engineers 10 years salary in costs if they have a single large DNS failure (security or downtime).

      • @Lumisal@lemmy.worldEnglish
        23•6 months ago

        Sounds like y’all should form a country wide DNS guild, and instead of looking for jobs, just ask band together, and then when the DNS eventually fails, they have no choice but to hire from the guild and pay 5 years salary at once to have it fixed. Then understand if getting hired and fired constantly, you just do a job every now and then and get a huge pay check. So contractor work, but you get to see the companies constantly burn themselves and give y’all with instead.

        • @grandkaiser@lemmy.worldEnglish
          13•6 months ago

          Any company that is willing to fire me to save costs isn’t worth working for. The job is so in-demand that if I put “looking for a job” in my linked-in, I get multiple offers within the hour. Not even joking. That’s how I got my current job.

          • @Lumisal@lemmy.worldEnglish
            5•6 months ago

            1. How long does it take to be a DNS engineer?

            2. How likely is it to be replaced in 10 years by AI?

            I was gonna go for chemistry but you have a convincing argument with the job offers coming to you rather than the other way around

            • @grandkaiser@lemmy.worldEnglish
              11•6 months ago

              1. Generally to be “in-demand”, you need about 6 years of experience & highly desirable certifications (at least one security cert such as sec+ or CASP, dns-related cert such as Infoblox CDCA, and typically something else like cloud engineering or maybe automation engineering related). Getting into DNS is usually something that happens after you’ve already been an enterprise network engineer for a number of years. It’s highly specialized and rather difficult.

              2. Not possible. While AI can theoretically do the job, error is too expensive. AI already does much of my work, but I have to make risk assessment & I run the automation systems. I already automate much of my daily work. But when big stuff breaks, automation won’t fix it.

      • @Serinus@lemmy.worldEnglish
        12•6 months ago

        I recently called my ISP to complain about the internet issues for the last 5 hours. I told them I’m a dev and kind of know what I’m doing. I’ve already tried multiple devices, restarted the modem multiple time, etc. You know, I haven’t restarted the router.

        As I was pulling up the router page, I tried to ping cnn.com from the router’s tools. It went through. On the desktop it wouldn’t. It’s my pi-hole.

        Sorry, ISP. This one’s on me.

        Was a real easy call for the support guy though.