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?

  • lungdart@lemmy.caEnglish
    4·
    1 year ago

    I would migrate the domain. Don’t bother with flakey services. Cloudflare free tier can do some amazing things.

    In the meantime set it in your host file to the correct IP to get by.

    • aesir@lemmy.worldOPEnglish
      1·
      1 year ago

      I see your point, but now I do not think it is FreeDNS fault. DNSChecker.org shows my domain name properly resolved worldwide, and so it has been for months. I also created a second subdomain just now, exactly as the non-working one, and was properly resolved within seconds at my work pc. So I do not blame FreeDNS, I think it is our internal DNS server that is messed up or even hijacked.

        • aesir@lemmy.worldOPEnglish
          0·
          1 year ago

          I tried to set it to 8.8.8.8 but I have still the same result. Can it be overridden at the router level? So far the only solution is to manually add the damn line to etc/hosts.

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

            Probably not your problem but if 8.8.8.8 has some wrong DNS record cached you can flush the cache for one name at https://dns.google/cache and for 1.1.1.1 at https://one.one.one.one/purge-cache/

            There are also commands on each of the major operating systems to flush local caches.

            It is also possible that DHCP or IPv6 router advertisements reset your manual DNS setting of 8.8.8.8 depending on how you set it.

            • marsara9@lemmy.worldEnglish
              2·
              1 year ago

              Another thing that can be happening is that the router or firewall is redirecting all port 53 traffic to their internal DNS servers. (I do the same thing at home to prevent certain devices from ignoring my router’s DNS settings cough Android cough)

              One way you can check for this is to run “nslookup some.domain” from a terminal and see where the response comes from.