www.whatsmydns.net
Open in
urlscan Pro
172.67.68.250
Public Scan
Submitted URL: https://www.whatsmydns.net/#A/fce.topekapublicschools.net
Effective URL: https://www.whatsmydns.net/
Submission: On April 05 via manual from US — Scanned from DE
Effective URL: https://www.whatsmydns.net/
Submission: On April 05 via manual from US — Scanned from DE
Form analysis 1 forms found in the DOM
<form id="f" class="flex flex-1 lg:flex-none flex-col sm:flex-row">
<div class="flex">
<input id="q" aria-label="Query" class="w-full sm:w-64 sm:mr-1 mb-3 sm:mb-0 shadow leading-tight appearance-none border border-gray-400 hover:border-gray-500 rounded py-2 px-3 text-gray-700 focus:outline-none focus:ring" type="text"
placeholder="www.example.com" autocapitalize="off" autocorrect="off" autofocus="autofocus">
</div>
<div class="flex">
<div class="inline-block relative flex-1 sm:w-24 mr-2 sm:mr-1">
<select id="t" aria-label="Record Type" class="block appearance-none w-full bg-white border border-gray-400 hover:border-gray-500 px-3 py-2 pr-8 rounded shadow leading-tight focus:outline-none focus:ring">
<option value="A" title="Host address (dotted quad)" selected="selected">A</option>
<option value="AAAA" title="IP v6 address (address spec with colons)">AAAA</option>
<option value="CNAME" title="Canonical name for an alias (domain name)">CNAME</option>
<option value="MX" title="Mail exchanger (preference value, domain name)">MX</option>
<option value="NS" title="Authoritative nameserver (domain name)">NS</option>
<option value="PTR" title="Domain name pointer (domain name)">PTR</option>
<option value="SOA" title="Start of Authority">SOA</option>
<option value="SRV" title="Service record">SRV</option>
<option value="TXT" title="Descriptive text (one or more strings)">TXT</option>
<option value="CAA" title="Certification Authority Authorization">CAA</option>
</select>
<div class="pointer-events-none absolute inset-y-0 right-0 flex items-center px-2 text-gray-700">
<svg class="fill-current h-4 w-4" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20">
<path d="M9.293 12.95l.707.707L15.657 8l-1.414-1.414L10 10.828 5.757 6.586 4.343 8z"></path>
</svg>
</div>
</div>
<div class="relative inline-block mr-2 sm:mr-1">
<button id="o" type="button" aria-label="Settings" class="shadow leading-tight bg-white text-gray-700 font-semibold py-2 px-3 border border-gray-400 hover:border-gray-500 rounded focus:outline-none focus:ring inline-flex items-center">
<svg class="fill-current h-5 w-5" viewBox="0 0 20 20">
<path fill-rule="evenodd"
d="M11.49 3.17c-.38-1.56-2.6-1.56-2.98 0a1.532 1.532 0 01-2.286.948c-1.372-.836-2.942.734-2.106 2.106.54.886.061 2.042-.947 2.287-1.561.379-1.561 2.6 0 2.978a1.532 1.532 0 01.947 2.287c-.836 1.372.734 2.942 2.106 2.106a1.532 1.532 0 012.287.947c.379 1.561 2.6 1.561 2.978 0a1.533 1.533 0 012.287-.947c1.372.836 2.942-.734 2.106-2.106a1.533 1.533 0 01.947-2.287c1.561-.379 1.561-2.6 0-2.978a1.532 1.532 0 01-.947-2.287c.836-1.372-.734-2.942-2.106-2.106a1.532 1.532 0 01-2.287-.947zM10 13a3 3 0 100-6 3 3 0 000 6z"
clip-rule="evenodd"></path>
</svg>
</button>
<div id="os" class="hidden origin-top-right absolute right-0 mt-1 w-56 md:w-64 rounded-md shadow-lg">
<div class="rounded-md bg-white ring-1 ring-black ring-opacity-5 p-2">
<label class="block text-gray-700 text-sm mb-2" for="c"> Expected Value: </label>
<input id="c" class="shadow leading-tight appearance-none border border-gray-400 hover:border-gray-500 rounded w-full py-2 px-3 text-gray-700 focus:outline-none focus:ring" type="text" placeholder="1.2.3.4" autocapitalize="off"
autocorrect="off">
</div>
</div>
</div>
<button id="s" type="submit" class="shadow leading-tight bg-white text-gray-700 font-semibold py-2 px-3 border border-gray-400 hover:border-gray-500 rounded focus:outline-none focus:ring inline-flex items-center">
<svg data-icon-search="" class="h-5 w-5" viewBox="0 0 20 20">
<path fill-rule="evenodd" d="M8 4a4 4 0 100 8 4 4 0 000-8zM2 8a6 6 0 1110.89 3.476l4.817 4.817a1 1 0 01-1.414 1.414l-4.816-4.816A6 6 0 012 8z" clip-rule="evenodd"></path>
</svg>
<svg data-icon-loading="" class="animate-spin h-5 w-5 hidden" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24">
<circle class="opacity-25" cx="12" cy="12" r="10" stroke="currentColor" stroke-width="4"></circle>
<path class="opacity-75" fill="currentColor" d="M4 12a8 8 0 018-8V0C5.373 0 0 5.373 0 12h4zm2 5.291A7.962 7.962 0 014 12H0c0 3.042 1.135 5.824 3 7.938l3-2.647z"></path>
</svg>
<span class="ml-2">Search</span>
</button>
</div>
</form>Text Content
A AAAA CNAME MX NS PTR SOA SRV TXT CAA
Expected Value:
Search
Donate
Los Angeles CA, United States
Speakeasy
Dallas TX, United States
Speakeasy
Atlanta GA, United States
Speakeasy
New York NY, United States
Speakeasy
Providence RI, United States
Verizon
68.111.104.202
Toronto ON, Canada
Radiant
68.111.104.202
Mexico City, Mexico
Total Play
Santa Cruz do Sul, Brazil
Claro
68.111.104.202
Paterna de Rivera, Spain
ServiHosting
68.111.104.202
Manchester, United Kingdom
Ancar B
68.111.104.202
Lille, France
Completel SAS
68.111.104.202
Amsterdam, Netherlands
Freedom Registry
68.111.104.202
Oberhausen, Germany
Deutsche Telekom
68.111.104.202
Zizers, Switzerland
Oskar Emmenegger
68.111.104.202
Sassuolo, Italy
Telecom Italia
68.111.104.202
Cullinan, South Africa
Liquid
68.111.104.202
Antalya, Turkey
Teknet Yazlim
68.111.104.202
St Petersburg, Russia
Yandex
Peshawar, Pakistan
PTCL
68.111.104.202
Ariyalur, India
Railwire
68.111.104.202
Shah Alam, Malaysia
TT Dotcom
68.111.104.202
Singapore, Singapore
Tefincom
68.111.104.202
Nanjing, China
NanJing XinFeng IT
68.111.104.202
Seoul, South Korea
KT
Osaka, Japan
NIFTY
68.111.104.202
Adelaide SA, Australia
Telstra
68.111.104.202
Melbourne VIC, Australia
Telstra
68.111.104.202
DNS PROPAGATION CHECKER
whatsmydns.net lets you instantly perform a DNS lookup to check a domain name's
current IP address and DNS record information against multiple nameservers
located in different parts of the world.
← back to map view
.
.
.
GLOBAL DNS CHECKER - HOW TO CHECK DNS PROPAGATION
whatsmydns.net is a free online tool that lets you quickly and easily perform a
DNS lookup to check DNS propagation and see information of any domain from DNS
servers located in many countries all around the world.
You can test changes made to new or existing domains and see if they have been
updated correctly without the need to manually query remote servers. This gives
you immediate insight into how users globally may be resolving DNS records for
your website, email or other online service.
Many operating systems include DNS tools to check DNS records manually for
diagnosing problems. However, using these tools can be complicated and difficult
to understand for non-technical people which is why the whatsmydns.net DNS
checker was created to help with quickly checking DNS propagation.
whatsmydns.net makes the process of performing global DNS checks easy by
maintaining a range of DNS servers to perform lookups with. These results are
then parsed and displayed on a map so that results are easier to understand at a
glance. Individual lookup results can be seen in detail by selecting a server
location from the list or clicking on the map markers once a search has been
completed.
WHAT IS DNS AND HOW DOES IT WORK?
The Domain Name System (known as DNS) is a system used to convert a name (like
www.google.com) into an IP address (like 192.168.2.1). These addresses are used
by computers to communicate with each other on the internet. Most people find
remembering names much easier than numbers, so DNS makes this process easy.
When you visit a website, your computer, phone or tablet will first check your
local DNS cache for the corresponding IP address. If your device has not
recently looked up this website, then it will need to ask your configured DNS
server which will forward the request on to the DNS server responsible for
managing the records. This process is known as a DNS lookup request.
Once the IP address is known, it is stored locally for a set period of time
known as the Time To Live (TTL) and used to speed up future requests. Updated
records will not be returned until this time has expired, this can often be the
cause of why DNS changes do not appear to be working right away.
WHAT IS DNS PROPAGATION?
DNS propagation is the term commonly used to check the current state of DNS
results globally and is often asked about when changes made to DNS zones do not
appear to be working as expected. This process can take from only a few minutes,
but often takes up to 48-72 hours and sometimes longer.
While technically DNS does not propagate, this is the term that people have
become familiar with. DNS requests are recursively forwarded and looked up from
the locally used resolver to the authoritative name server on demand and then
cached to speed up future lookup requests. For this reason, commonly used DNS
servers of large network providers located around the world have been selected
when performing DNS checks.
For popular websites, DNS results may be cached for people in different parts of
the world using many different recursive DNS resolvers. If you have recently
made changes to your configuration, and the TTL has not yet expired, then some
people may be receiving out of date results which could mean that they see an
older version of your website.
HOW LONG DOES DNS PROPAGATION TAKE?
How long DNS propagation takes usually depends on your records TTL setting. This
can be anywhere from several minutes up to 48-72 hours or longer. However, there
are sometimes other reasons for a long propagation time.
The main issues as to why DNS propagation can take so long are:
DNS Cache - The Time to Live (TTL) is the duration in which DNS data is allowed
to 'live' in the cache of a local device or DNS resolver. When this duration
expires, the local device or server removes existing DNS information and carries
out another DNS lookup to fetch new information. Higher TTL settings can often
cause a delay in DNS propagation.
Internet Service Providers - Your ISP also caches DNS results, which allows for
many users to access sites faster. For every website requested, they will ask
the DNS server responsible only once but return the same result for many users.
Some ISPs also overlook TTL rules, keeping a cached DNS record even if the TTL
has expired. This can make DNS propagation take longer than it should.
Other DNS Servers - You may not be using your ISPs DNS server, if this is the
case then the same issues that may be causing delays can still apply.
Domain Name Registrar - When changing web hosting or DNS providers for your
domain, it is often also required to update your authoritative name servers.
These changes will need to be reflected in the corresponding TLD nameserver for
your domain name. For example, if you were to change the NS records for
example.com, then the .com TLD nameserver would also need to update which can
cause delays in DNS propagation.
HOW DO YOU SPEED UP DNS PROPAGATION?
A technique used to speed up DNS propagation and prevent a delay is to lower
your DNS records TTL a few days in advance of making any changes so that when
the change is made any old records expire more quickly. Unfortunately, most
people who are having issues and trying to speed up DNS propagation only find
this out after making changes and are wondering why they're not seeing instant
results.
If you have checked DNS globally, and are seeing different results locally then
you may consider flushing your DNS cache, or using another DNS server. As a last
resort, manually overriding your local DNS entries in your systems hosts file
can also be done but should be considered a temporary measure and only works for
certain record types.
WHAT SERVER TYPES ARE USED IN A DNS CHECK?
There are 4 different types of DNS servers involved when performing a DNS check.
Each has a different role and may not be needed at all depending on the
situation, having all these different server types is what contributes to DNS
propagation issues.
Recursive Resolver - The DNS server your device communicates with is called the
recursive resolver and is issued to you automatically by your ISP, but can be
also configured on your router or individual devices. These DNS severs are
ideally located in close geographical proximity to return results as fast as
possible. These servers will cache a copy of the DNS results to speed up future
DNS lookup requests.
Root Name Server - This type of DNS server is responsible for returning the IP
address of the TLD (Top Level Domain) nameserver. For instance, if it is trying
to resolve example.com, the root name server returns the IP of the TLD name
server that runs .com domains.
TLD Name Server - This name server returns the authoritative name servers for
each domain under the Top Level Domain it's responsible for. The .com TLD name
server will return results for example.com but not example.org.
Authoritative Name Server - This stores DNS servers' configuration data for
specific domain names.
WHAT HAPPENS WHEN A DNS REQUEST IS MADE?
Below demonstrates the flow of events when a user requests to visit
www.example.com in their web browser for the first time and does not yet have
cached results. As you can see, each step introduces the possibility of a DNS
propagation delay.
1. → You type www.example.com into your web browser.
2. → Your device sends a request to your configured recursive resolver.
3. → The recursive resolver asks the root nameserver for the IP address of the
TLD nameserver responsible for .com domains.
4. ← The root nameserver returns the IP address of the .com TLD nameserver to
the recursive resolver.
5. → The recursive resolver asks the .com TLD nameserver for the address of
the authoritative nameserver responsible for example.com.
6. ← The .com TLD nameserver returns the IP address of the authoritative
nameserver to the recursive resolver.
7. → The recursive resolver asks the authoritative nameserver for the IP
address of www.example.com.
8. ← The authoritative nameserver returns the IP address of www.example.com to
the recursive resolver.
9. ← The recursive resolver returns IP address of www.example.com to the
browser.
10. → Your browser makes a web request directly to the resolved IP address.
WHICH DNS RECORD TYPES CAN BE CHECKED?
You can check DNS propagation for common record types including:
* A - The most common DNS record, used to point a domain to an IP address.
* CNAME - Also known as alias records, they point to other DNS records.
Sometimes used for subdomains like www.
* MX - Mail Exchanger records are used set email servers and their priority.
* NS - Name Server records store the authoritative nameserver.
* TXT - Text records are commonly used for configuration settings such as SPF
and DKIM records.
Additional types that can be checked which are usually used in more advanced
configurations include: AAAA, CAA, PTR, SOA and SRV.
MAKE SURE TO CHECK ALL YOUR DNS RECORDS
When checking DNS records, there are often multiple record types that you need
to verify are correct. For example, websites sometimes include www or other
subdomains as either an A or CNAME record, and email servers use the MX record
type.
Check Another Record Type ↑ or Check Another Domain ↑
.
.
.
Support Me If you find this service useful for checking DNS propagation, please
consider donating to help pay hosting costs and keeping the site up to date.
Donate via PayPal
DNS Tools DNS Checker DNS Lookup Reverse DNS Lookup What's My IP Address? DNS
Guides DNS Security Flush DNS Hosts File
DNS Lookup A Record Lookup AAAA Record Lookup CAA Record Lookup CNAME Record
Lookup MX Record Lookup NS Record Lookup PTR Record Lookup SOA Record Lookup SRV
Record Lookup TXT Record Lookup
Articles & Blog DNS Articles Development Blog DNS Servers Global DNS Servers
Australian DNS Servers France DNS Servers New Zealand DNS Servers United Kingdom
DNS Servers United States DNS Servers
Browser Extension Chrome new Social Media Contact Email: info@whatsmydns.net
Twitter: @whatsmydns Legal Privacy Policy
Powered By
00:00/02:54
10 Sec
34K
0
YouTube Says Using Videos to Train OpenAI's Sora Breaks Rules
Next
Stay
x