Can’t resolve kuleuven.be (a major Belgian university) with 1.1.1.1/1.0.0.1

It appears the website for KU Leuven (kuleuven.be), a major Belgian university, cannot be resolved using 1.1.1.1 or 1.0.0.1 even after flushing the DNS cache at https://1.1.1.1/purge-cache/

Both staff and students are affected by this.

dig @1.1.1.1 +short kuleuven.be

Yields no results

dig @8.8.8.8 +short kuleuven.be

But with Google’s DNS, it works fine.

Submitting the domain name at https://1.1.1.1/purge-cache/ doesn’t help either.

Can someone please take a look?

This issue also affects subdomains like idp.kuleuven.be for example.

1 Like

Hi Wouter,

Please see
https://dnssec-analyzer.verisignlabs.com/kuleuven.be
and
https://dnssec-analyzer.verisignlabs.com/idp.kuleuven.be
and suggest to the DNS administrators to fix these DNSSEC problems.

Hope this helps.

What problems? The zone does not use DNSSEC, and those reports look clean to me.

1 Like

I guess I went on a tangent from:

I’m unable to reproduce any issue with these hostnames:

[email protected]:~$ dig @1.1.1.1 +short kuleuven.be
134.58.64.15
[email protected]:~$ dig @1.1.1.1 +short idp.kuleuven.be
134.58.64.57
[email protected]:~$ date -u
Sat 24 Apr 2021 06:46:01 PM UTC

@amayorga Not sure what is going on here but I still seem to be having this issue with idp.kuleuven.be and the apex domain in particular…

[email protected]:~$ dig @1.1.1.1 +short www.kuleuven.be
134.58.64.12
[email protected]:~$ dig @1.1.1.1 +short kuleuven.be
134.58.64.15
[email protected]:~$ dig @1.1.1.1 +short idp.kuleuven.be
[email protected]:~$ dig @8.8.8.8 +short www.kuleuven.be
134.58.64.12
[email protected]:~$ dig @8.8.8.8 +short kuleuven.be
134.58.64.15
[email protected]:~$ dig @8.8.8.8 +short idp.kuleuven.be
134.58.64.57
[email protected]:~$ date -u 
Mon Apr 26 09:08:20 UTC 2021

Edit: did a test a few hours later and now none of the above domains resolve + any other subdomain of the universty’s website

[email protected]:~$ dig @1.1.1.1 +short idp.kuleuven.be
[email protected]:~$ dig @1.0.0.1 +short idp.kuleuven.be
[email protected]:~$ dig @1.1.1.1 +short www.kuleuven.be
[email protected]:~$ dig @1.0.0.1 +short www.kuleuven.be
[email protected]:~$ dig @8.8.8.8 +short idp.kuleuven.be
134.58.64.57
[email protected]:~$ dig @8.8.4.4 +short idp.kuleuven.be
134.58.64.57
[email protected]:~$ dig @8.8.4.4 +short www.kuleuven.be
134.58.64.12
[email protected]:~$ dig @8.8.8.8 +short www.kuleuven.be
134.58.64.12
[email protected]:~$ dig +short CHAOS TXT id.server @1.1.1.1
"DFW"
[email protected]:~$ dig +short CHAOS TXT id.server @1.0.0.1
"DFW"
[email protected]:~$ date -u
Mon Apr 26 12:40:01 UTC 2021

It is very strange indeed. When I first reported the issues, both the root domain and subdomain were not resolved using 1.1.1.1. Then a few days later, both worked fine.

Not it seams only the root domain is working.

What is going on here?

This confirms you wife’s story (she works for a college associated with Leuven) that she experiences connection issues from time to time.

It seems our resolver is not able to connect the nameservers of kuleuven.be in DFW. I’ve override it with a temporary path, it should be working now. I’ll try to contact the admin on the other side to figure out what’s wrong.

1 Like