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 .
China Railcom DNS Address Directory
Was this tool helpful to use?
Your feedback helps us make it better
Read web-collected China Railcom DNS-related IPv4 records, ranges and location labels. Original source, collection date, public access and availability are unverified.
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 11 web-collected IPv4 records labelled for China Railcom / China Tietong networks. Each row has a starting IP, an ending IP and a location description kept with the record. DNS, the Domain Name System, is the distributed system used to look up information associated with domain names; this directory itself does not perform a lookup. It lets English-reading users inspect address records while researching Chinese network documentation or checking an older configuration.
When Start IP and End IP are identical, the record names one address. When they differ, the row records two boundaries. Those boundaries do not establish that every IP between them is a DNS resolver, or that either endpoint currently answers queries. The location is a stored text label, not a live location check or a confirmed service area. For example, the directory includes 61.232.202.158 to 61.232.202.158 with the label “China Railcom DNS, Xi'an, Shaanxi,” and 61.234.254.5 to 61.234.254.6 with “China Railcom DNS Server, Hunan.” These are examples of how the rows are written, not verified services.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use the table search to match displayed text, such as an exact IP string or words in a location label. The filter is text matching, not an IPv4 range containment test: an address lying between two endpoints may not match either endpoint. Try a spelling found in the stored label if a region search has no result. Sort by a column heading, choose which columns to show, and move through the pages as needed. The page size is 20 rows, so the current 11-record set fits on one page.
Compare the complete row with the configuration, ticket or source document you are investigating. Keep the start IP, end IP and location wording together; do not discard the endpoint distinction or treat the label as proof of current ownership. If you need a copy, CSV and JSON export and print controls are available. Export and print actions require sign-in and an active membership. A saved copy is still this same unverified directory; note when you saved it separately from any unknown original collection date.
Use cases
See how the tool fits into real work and everyday tasks.
An administrator can search for an address copied into a past incident and compare its stored label and endpoints with the ticket. The result helps identify what to ask the current service provider; it does not establish that the old configuration remains suitable.
A researcher can locate an address row associated with a region or China Tietong wording, then retain the full record as a lead for further checking with the relevant operator or network administrator.
Q&A
Find concise answers to common questions and confusing cases.
No. The directory's source label is web-collected, and its original publisher and collection date are unknown. Public access and current resolver health have not been verified.
No. A pair of endpoints does not identify every address between them as a resolver. Do not expand a range into a configuration list.
Search matches displayed text; it does not test whether an entered address falls numerically between the stored endpoints. Check the range manually or search for one of its displayed endpoints.
No. It displays stored records without querying the addresses. A separate check from the intended network and confirmation from its operator are needed to assess use.
Notes
Review scope, result limitations, and important precautions before use.
The records are identified as web-collected. The original publisher, collection date and complete record provenance have not been established, and the China Railcom wording does not certify that the operator published, owns or currently operates each listed address. The list may be stale, incomplete or associated with network-restricted resolvers. A failed query from another network does not prove an internal resolver is down; a successful query does not prove public access or continuing service.
Before changing a device or router setting, ask the current network operator which resolver is intended for that connection and follow its current instructions. Do not replace an automatically supplied resolver solely because an address appears here. The RFC below explains DNS background only; it is not evidence about these particular records.
Related
Discover related tools, collections, and available API capabilities.