Question that doesn't really belong here ...

rf1234

I have a problem that doesn't really belong here. But I'm pretty desperate because somehow there doesn't seem to be a solution.
My website https://www.lgfinance.eu/ is not accessible for me: DNS_PROBE_FINISHED_NXDOMAIN
The DNS server can't find my website :-(
This morning I found out that there is no problem accessing the site in the neighboring town in the same county. But I myself have been cut off for at least 14 hours.
Nobody can help me! My ISP has no problem. It's based in Berlin. I have tested VPN with NordVPN: Does not work. The only thing that works is the TOR browser.
Then of course I also called my internet provider etc. I walked through the city and logged into various WiFi networks. None of them worked with my site. Neither did my cell phone.
I assume there's something wrong with the local infrastructure. But what? No one can help ... We'll have to wait and see. I can't live with that.
Does anyone have any ideas for me? Many thanks in advance!

kthorngren

See if the troubleshooting steps here help. If the problem is local to your PC maybe you just need to flush the DNS cache - described in the link.

Kevin

kthorngren

I'm able to open the website but when doing the ICANN lookup for lgfinance.eu I get these errors:

No registry RDAP server was identified for this domain. Attempting lookup using WHOIS service.
Failed to perform lookup using WHOIS service: TLD_NOT_SUPPORTED.

Looks like some good info regarding these errors in this thread.

Kevin

rf1234

Thanks, Kevin. Did pretty much all of that. It is weird. I don't think it is anything local in terms of my machine. My colleague has the same issues. He drove over to the next town - and everything worked. Just like using the Tor Browser and accessing my website from Finland for example.

This is crazy. Hope it'll work again tomorrow. If not I will involve the Plesk support team. Hope they can help somehow.

rf1234

I get this from ICANN

kthorngren

Just use the domain name, for example: lgfinance.eu or datatables.net.

Kevin

rf1234

I see; wasn't aware of that.

But when I use Eurid (they are responsible for eu domains) everything is fine:
https://whois.eurid.eu/en/search/?domain=lgfinance.eu

allan

I think your DNS provider is having issues. DNS records can take time to propage - they have a TTL (Time To Live), so as Kevin indicates there might be a cache of an old working resolution in some systems still. That could be your computer, your router, your ISPs router, etc.

You can use a tool called "dig" to query a specific DNS server for a given domain name and see if it knows about it. For example you can dig your home router (which will resolve from cache, or go to your ISPs DNS server or the configured server to get the data).

This site provides that online. I've set it up there to query for your domain name from the most common public DNS servers, and the one for your host.

Presumably you are using Strato for your DNS and web-server hosting? I think you need to get in touch with them if you haven't already. They don't have a public facing status page that I can see.

The .eu whois doesn't appear to show when the domain name expires like it does for .com and others. Make sure that is up to date as well (again, presumably from Strato).

Good luck! Things like this are a total headache!

Allan

kthorngren

I'm glad that I have forgotten about all those tools

Kevin

rf1234

The problem hasn't gone away. I will check Allan's suggestions today and ask the Plesk Support for help as well.

The good thing is that my customers aren't affected and my sales guy can use the TOR Browser which works.

Strato isn't particularly helpful with these things. I will probably have to use additional or different DNS servers. Will try all of that over the week end when my customers aren't working.

allan

If you are able to change the nameservers for your domain, it might be worth running it through CloudFlare or some other DNS provider. The web server appears to still be operational, its just the DNS progagation that has gone wrong.

Allan

rf1234

If you are able to change the nameservers for your domain

I should be and I want to try that - but facing some obstacles.

I've been "digging" deep, Allan :-). And called Strato again. It is a regional problem that is expanding unfortunately. Strato are still not aware of it. Just got a problem call from Eastern Westphalia - half way to Berlin from here ... Will take a while until the problem pops up in Berlin

I couldn't turn off DNSSEC and hence wasn't able to add more DNS servers. Will try 76.76.19.19 and 8.8.8.8 (Google) as well - as soon as Strato will have turned off DNSSEC.

allan

It depends on the TTL and when the cached request was made. It sounds like it had a long TTL, but it does appear that it is effectively going to take the site offline everywhere (it certainly is from here in the UK with Google's free DNS servers).

Do you know of any other domains that are using Strato? Are they having the same issue? (Use the site I linked to above to check global accessibility).

I reckon you should consider bypassing Strato in this case and use the domain name tools to change the nameservers to something that resolve globally (assuming their domain name tools allow you to change the name servers - I have come across some hosts which don't...).

Allan

rf1234

Do you know of any other domains that are using Strato? Are they having the same issue? (Use the site I linked to above to check global accessibility).

No I don't, but Strato is telling me they still don't have an issue. They seem to have nobody else having that problem.

I reckon you should consider bypassing Strato in this case and use the domain name tools to change the nameservers to something that resolve globally

I would like to do that but I am still unable to turn off DNSSEC and Strato doesn't allow me to change the DNS as long as DNSSEC is turned on.

This is what I am seeing in Plesk:

But I do need to make the change with Strato because they are hosting the virtual Linux Server - at least that is what Plesk is telling me.

And there it looks like this:

Since I can't turn off DNSSEC because it is stuck somehow, I can't do anything

allan

I think there might be a DNSSEC configuration issue with the current DNS server:

→ dig lgfinance.eu @8.8.8.8

; <<>> DiG 9.20.2 <<>> lgfinance.eu @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 11161
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
; EDE: 9 (DNSKEY Missing): (No DNSKEY matches DS RRs of lgfinance.eu)
;; QUESTION SECTION:
;lgfinance.eu.          IN  A

;; Query time: 96 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Fri Nov 15 15:34:17 GMT 2024
;; MSG SIZE  rcvd: 87

Note specifically:

; EDE: 9 (DNSKEY Missing): (No DNSKEY matches DS RRs of lgfinance.eu)

But if I query the source name server:

→ dig lgfinance.eu @ns3.stratoserver.net

; <<>> DiG 9.20.2 <<>> lgfinance.eu @ns3.stratoserver.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6828
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
;; QUESTION SECTION:
;lgfinance.eu.          IN  A

;; ANSWER SECTION:
lgfinance.eu.       150 IN  A   212.227.225.189

;; Query time: 66 msec
;; SERVER: 185.132.34.159#53(ns3.stratoserver.net) (UDP)
;; WHEN: Fri Nov 15 15:34:12 GMT 2024
;; MSG SIZE  rcvd: 57

It is fine.

Its getting to the point of being beyond my pay grade I'm afraid. There are a bunch of SO and similar questions about that specific error (e.g. here), but DNSSEC is not something I'm particularly familiar with.

This site might be useful for checking the DNSSEC chain.

I'd guess something between the registrar and your DNS server has gone out of sync.

Allan

rf1234

Thanks, Allan! The Plesk support is currently working on it. I hope they can kill the DNSSEC service for me so that I can eventually try different DNS servers.

allan

The only plus side I can see is that we know DNSSEC works...

Good luck!

Allan