Primary DNS addresses V4 and V6 detecting as unconfigured.
When I logged into portal, I noticed the website was saying that I was not using NextDNS even though I haven't touched my network settings in a while.
This device is not using NextDNS.
This device is currently using ”EDGEUNO SAS” as DNS resolver.
Visiting test.nextdns.io seemed a bit random, with sometimes correctly showing it was using my profile and sometimes without it.
{
"status": "unconfigured",
"resolver": "200.25.56.100",
"srcIP": "[redacted IPv6]",
"server": "edgeuno-sao-1"
}
I thought something changed my network settings all sudden but no, Windows and router both has the correct addresses. I attempted to resolve domains with that resolver but none of the three I saw were reachable directly.
Started playing with nslookup and dns addresses assigned to me and noticed some responses were a bit off between primary and secondary addresses of each protocol (V4 and V6). Resolving test.nextdns.io with primary lead me to these addresses:
Name: test.nextdns.io
Addresses: 2800:1e0:1020:3::5
200.25.57.69
Attempting with secondary gave me a different set:
Name: test.nextdns.io
Addresses: 2a00:11c0:f:ffff::5
37.252.238.25
So, I removed all of the primary addresses and left only secondary of each:
{
"status": "ok",
"protocol": "DOH",
"profile": "[redacted]",
"client": "[redacted V6]",
"srcIP": "[redacted V6]",
"anycast": true,
"server": "anexia-sao-1",
"clientName": "unknown-doh",
"deviceName": "[redacted, devname is correct too]",
"deviceID": "[redacted]"
}
Success! Everything was good.
Is this happening with someone else? Did I have set something wrong?
1 reply
-
Disregard my post, I found out what's happening. librewolf (Firefox fork) browser has had set DoH to Quad9 servers and not picking what I had set before! Now I have no idea why it was misconfigured and for how long it was, probably a few weeks.
Everything is okay now.
Content aside
- 1 mth agoLast active
- 1Replies
- 32Views
-
2
Following