Hello, unfortunately we have the same situation. Many surveys on a subdomain of limequery.org, which are no longer accessible for many of our participants. I have also reported this to Limesurvey GmbH.

Good to know that this is a more general issue. I have also messaged my contacts at Limesurvey about this issue. Let's see what they say.

I am still able to access bikemn.limequery.org though.

Thanks again Holch. Hope that LimeSurvey is sending you T-shirt or something for all this assistance!

We're looking closely into this issue right now. Hopefully we can resolve it tonight. Sorry for the delay.

I see outdated glue records on limequery.org. That can lead to wrong nameservers. Might not be the only issue, but that should be fixed.

Replace the glue records (which are set via the domain registry not your nameserver).
ns1.limesurvey.org is currently set to 136.243.106.133 instead of 167.235.201.250.
ns2.limesurvey.org is currently set to 145.239.7.156 instead of 5.161.47.82.

Yeah, we're looking at this, jelo, thanks. It's a bit problematic since it can take some hours for the change to be propagated.

For me it is the same: eudemos.limequery.com/admin cannot be found. It is not a local internet problem, as I can access this forum.
It seems, that the domain is not listed in the nameserver??

I can see that site from Canada.

From Germany, too

When the root cause is fixed it will take up to 72 hours to be in every DNS resolver.

If you cannot access the domain you can temporary change the DNS settings on your device to use a different resolver. These resolver might have piked the right Nameserver IP addresses.

E.g public DNS like Google DNS or Quad9
en.wikipedia.org/wiki/Quad9

In browsers like Firefox there is an option "Enable DNS over HTTPS" where you can choose from DNS services and override the Nameserver set in your device (mostly your router IP which uses the provider' nameserver).

I agree with Jelo. Usually the DNS propagation is quite quick, but sometimes it takes a bit longer. During this period, people who use DNS via a Server that is not yet updated might not be able to access your site. So for respondents you can't do much, but just have to wait until the new information is distributed everywhere.

For your own access you can try different DNS servers, just like Jelo described. But be aware that this will only solve the problem for you. Others might still encounter the problem, if the DNS server they use is not updated yet.

And I can access eudemos.limequery.com/admin from Brazil as well.

holch wrote:

 So for respondents you can't do much, but just have to wait until the new information is distributed everywhere.
 

I would be surprised if it is working now.
I'm still getting two IP-addresses for every nameserver. If your local DNS resolver chooses the glue records the surveydomain cannot be resolved into an IP address.

Looks like the majority of DNS resolver choose the right set and ignore the outdated glue records.