We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Search a web-collected historical set of China Mobile DNS address records and recorded locations.
Static address directory. Connectivity, resolution speed and access from your network are not checked.
Source label: web-collected. The original publisher and collection date have not been verified. Region labels retain the source wording where no translation is available; access and resolver availability are unverified.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page is a static directory of 63 DNS-related address records labelled for China Mobile. Each row shows a starting IP address, an ending IP address, and a location description retained from the collected record. It is intended for looking up or comparing a historical entry, such as one copied into an old ticket or configuration note. The directory does not send DNS queries or check whether an address currently answers.
When the start and end IP fields match, the record lists one address. When they differ, they mark the endpoints recorded for that row; the listing does not establish that every address between them operates as a resolver. Some entries use IPv4 notation and two entries use compressed IPv6 notation, where “::” represents one or more zero-valued groups under the IPv6 text format. Location is a stored label, not a live geolocation result or a verified service boundary. DNS itself is a distributed naming system, but the presence of an IP in this directory does not show that it currently provides DNS service. See the references for the protocol background and IPv6 notation.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter an address or a word from the recorded location in the table search. The search matches text in the rows; it is not a numeric range-membership test. An address lying between two displayed endpoints may not appear when you search for that address.
Compare the start and end values before treating an entry as a single address or a recorded range. Keep the location text with the address when noting a match so the original description is not lost.
Select a column heading to change sort order. Use the column menu to show or hide fields, and the previous and next controls to move through pages. These controls reorganize the displayed records; they do not validate or update them.
The directory includes the record 112.4.0.55 to 112.4.0.55, labelled “Jiangsu China Mobile DNS Server.” The matching endpoints mean the row contains one listed address. It also includes 2409:8088::a and 2409:8088::b, both carrying a nationwide wording in the source label. These examples reproduce directory entries only: neither the wording nor the format confirms present-day ownership, reachability, public access, or resolver health.
Use cases
See how the tool fits into real work and everyday tasks.
A network administrator can search an address copied into a past incident record and compare the stored location wording. Treat a match as a lead for follow-up, then confirm the intended resolver with the responsible network operator.
An English-speaking reader can use the address and retained location label to identify which directory entry a Chinese-network document may be referring to. The page helps with record lookup, while the original publisher and collection date remain unknown.
Q&A
Find concise answers to common questions and confusing cases.
This directory does not test resolution or availability, so it cannot confirm that any entry works today. Check current instructions from the network operator responsible for your connection.
Public access has not been verified. A provider or campus resolver may be intended for a particular network, and the word “DNS” in a location label is not proof of open access.
Search looks for matching text in the displayed row fields; it does not test whether a typed address falls numerically between the row endpoints. Search for an endpoint or the location wording, then inspect the range manually.
The labels preserve wording from records whose original publisher and collection date are unknown. They are not normalized geographic data, and this page does not independently verify attribution.
Notes
Review scope, result limitations, and important precautions before use.
The records are labelled web-collected, but their original publisher and collection date are unknown. Public accessibility, current operator attribution, resolver health, and completeness are unverified; the 63 rows are a count of entries in this snapshot, not a coverage total. Addresses may have changed purpose or assignment since they were collected. Do not use this directory alone to choose or replace DNS settings. For a working configuration, use current instructions from the provider of the network you are actually using and retain a way to restore prior settings.
Related
Discover related tools, collections, and available API capabilities.