Hi,

What to do if the domain name of one of my webserver, that me and some lab members use for work related stuff, is no longer resolved by our university DNS? When I first noticed it, I could see no resolution at all while now the domain resolves to a wrong IP. The site can be normally reached on any other network so there is no problem on my side I think.

Should I just wait (now more than 24 hours) or should I try anything? I am entitled to complain to our IT even though the issue is only with this not-really-professional FreeDNS subdomain?

EDIT: apparently some automatism marked this domain as malicious (absolutely it is not, not willingly and not compromised) and somehow DNS resolves to CNAME sinkhole.paloaltonetworks.com.

  • HjFUN@lemmy.worldEnglish
    3·
    1 year ago

    This may come down to details of their policies and how they interact and support each department. If it’s for your official work, and I’d say start with a ticket and if they resist then push it up the flag pole and don’t stop. (Assuming you’re not one,) Your PI ought to fight like hell to make sure their employees can do their jobs, and the chair fight to make sure their researchers can run their labs, and the dean much the same, but throwing heavier punches each step up. Really shouldn’t get to that point, but if you can’t do your job, rattle the cages until you can.

    • aesir@lemmy.worldOPEnglish
      2·
      1 year ago

      I already had contacts with our IT. I originally asked if they could host this service for us as it seemed the normal thing to do. They do not support anything custom (i.e. anything which is not a wordpress site) and just to give me a fourth level subdomain they wanted signatures from half the administration above me. That’s why I’m rogue with selfhosting also work stuff. But I think I can still complain just because their DNS gives back random IPs. This could even be hijacking, no?

      • taladar@sh.itjust.worksEnglish
        2·
        1 year ago

        I would probably send along the output of dig your.domain @uni-ip and dig your.domain @8.8.8.8 and dig your.domain @1.1.1.1 and dig your.domain @your-domains-authoritative-dns-server if you have that or some similar DNS client tool installed that allows direct requests to specific servers. If you don’t know the authoritative DNS servers for your domain, those are the ones in the NS records.