Query the originating nodeLocating current application server...
The location is estimated based on the current server's public network exit and has nothing to do with the location of the user's device.
MiyaIP DNS Diagnostic Tool
DNS / NSLookup
Trace delegation from the root to authoritative answers
Query public DNS records for domain names and IPs. The default is to relocate authoritative servers from the root server each time, without saving DNS records, delegations, or query results.
Authoritative Direct QueryDo not cache resultsSupports IPv4/IPv6 PTR
DNS response pathAuthoritative server direct check
This query will restart from the root delegation and will not use MiyaIP or the public recursive cache.
The query cannot be completed at the moment
Please try again later.
Query completed
DNS response obtained
Reviewable results are listed below by record type.
- Query name
- —
- query mode
- —
- response server
- —
- slowest response
- —
- Record quantity
- —
- query time
- —
Authoritative delegation pathThis query is positioned step by step from the root server, and the path will not be cached across requests.0 steps
Cache status:MiyaIP DNS result caching is turned off.
Two query paths
Authoritative answers and recursive perspectives, each solving different problems
The default path emphasizes provenance and freshness; the recursive path is used to see the results currently given by common public resolvers.
Authoritative Direct Query
Location delegation begins with the root servers, eventually interrogating the authoritative DNS directly for the target zone. MiyaIP does not save delegations or results, nor go through a public recursive cache.
recursive query
Each request is re-initiated from the MiyaIP server to the specified public resolver, but the resolver itself may return a cached answer based on the record TTL.
record quick check
From address to email and service discovery
- A / AAAA
- Map names to IPv4 and IPv6 addresses respectively. The CNAME chain continues to be positioned in authoritative mode, following up to 8 levels.
- MX / TXT
- MX describes the mail receiving server and priority; TXT often carries SPF, domain name verification and other public text policies.
- NS / SOA
- NS represents the authoritative server for the zone; SOA contains administrative facts such as the master server, serial number, and zone refresh time.
- CAA / SRV / PTR
- CAA restricts the certificate authority, SRV describes the service port and weight, and PTR is used to query the reverse hostname from the IP.
FAQ
Correct understanding of "no cache" and test nodes
Why does Authoritative Direct Check still show TTL?
TTL is a record field published by the authoritative server that tells the recursive resolver how long it can be cached. The page showing TTL does not mean that MiyaIP has saved the record; clicking the query again will still complete the delegation and authority request again.
Can recursive mode bypass caching completely?
No. MiyaIP will turn off its own client and HTTP cache and reissue the request, but the public recursive resolver can use its own cache according to the authoritative TTL, so the page will be clearly marked "Recursive cache may exist".
Why is the test node not my location?
DNS requests are made by the current MiyaIP application server. The node country, region, and city are estimated based on the server's public network exit. They are used to explain the query link and do not represent your device or DNS settings.
Why might authoritative mode be unavailable?
Authoritative direct check requires the server to be able to access the public network UDP/TCP 53. If a network is deployed to intercept or hijack direct DNS connections, MiyaIP will stop and report being unavailable and will not pass off recursive answers as authoritative answers.