nslookup
Team, Next DNS, greetings all. Been a while since my last presence here.
I wonder if you could help me understand what's the problem I'm getting into with nslookup command in windows 11.
Using #ping.nextdns.io (for servers location and latency and the command) #nslookup -type=txt whoami.ds.akahelp.net (for dns confirmation using windows 11 cmd line)
the ping information and the DNS result from the nslookup, it suggests that the DNS resolution for whoami.ds.akahelp.net
might be pointing to an Anexia server. Here is a breakdown of the relevant information:
- Ping Information:
- "anexia-mad": Ping response time of 18 ms
- "anexia-par": Ping response time of 40 ms
- "anexia-lis": Ping response time of 46 ms
- "anexia-lon": Ping response time of 111 ms
These entries indicate different Anexia server locations and their respective ping response times. These servers might be part of the Anexia network infrastructure.
- DNS Result from nslookup:
- Server: dns1.nextdns.io
- Address: 45.90.28.0
- Non-authoritative answer:
- whoami.ds.akahelp.net text =
- "ns"
- "193.168.204.73"
I would greatly apreciate any thoughts one this as I'm waiting to contact ISP and ask them to clear DNS caches from their services.
It's important to note that 193.168.204.73
is a private IP address in the range of private networks. Private IP addresses are not routable on the public internet, and they are commonly used within local network environments. Therefore, it is unlikely that 193.168.204.73
is the actual public IP address for the authoritative name server of the domain.
Regards
G70P
1 reply
-
193.168.204.73
•it is not a private IP.
• It is not part of Anexia but Netbarista.
• ipv4-netbarista-par-1.edge.nextdns.io
https://datatracker.ietf.org/doc/rfc1918/
Why do you even bother with this? If you have any problem with the internet the chances are that the issue is on your part and not on NextDNS.
Content aside
- 1 yr agoLast active
- 1Replies
- 132Views
-
1
Following