Manage cookies that are used for advertising, such as ad personalization, remarketing, and ad effectiveness analysis.
3.11. Domain is paid, but not working
The article is relevant to the following situations:
- Registered new domain, but the site is not working.
- Renewed existing domain, but the site is not working.
- The site operates at
example.com, but does not open atwww.example.com(or vice versa). - After changing DNS records, the site does not work or opens at the old address.
- After setting new NS, the domain continues to work from the old ones.
Short description
In DNS system there is a situation when some server caches data and domain state for a certain period, which is set with TTL (time-to-live) or configured on the server itself, after which the information is updated. In most cases, the caching period does not exceed 24 hours. You may encounter such caching when changing domain DNS records, changing NS, as well as after domain registration or restoration.
Detailed description
The principle of operation of the domain name system on the internet is described below.
Before registering a domain name, you enter the domain name example.com on your device. The following operations occur:
- Your device sends a request to the DNS server of your Internet Service Provider.
- The ISP's DNS server sends a request to the DNS server of the domain zone (in this case, it is the DNS server of the .COM zone).
- The DNS server of the domain zone responds to the ISP's DNS server that the domain does not exist.
- Your ISP's DNS server is responding to your device that the domain does not exist.
- The DNS server of the internet provider stores this information for future use (the retention period for this information may be several hours).
flowchart LR
device["💻 Your
device"] dns_isp[("🌐 DNS server
of Internet Service Provider")] dns_zone[("🌐 DNS server
of the .COM domain")] device-->dns_isp-->dns_zone dns_zone-->dns_isp-->device
device"] dns_isp[("🌐 DNS server
of Internet Service Provider")] dns_zone[("🌐 DNS server
of the .COM domain")] device-->dns_isp-->dns_zone dns_zone-->dns_isp-->device
Some time passes and you register a domain on our site. We send you a notification that the domain has been successfully registered. You enter the domain address on your device, but you still get a response that no such domain was found. This is due to the fact that operations are now taking place that are different from those that took place at the beginning, i.e.:
- Your device sends a request to the DNS server of your Internet Service Provider.
- Your ISP's DNS server responds to your device that the domain does not exist. ⚠️ This time the ISP's DNS server does not send the request to the DNS server of the .COM zone, which already knows about the existence of the
example.comdomain. This is due to the fact that the DNS-server of the ISP has remembered that such a domain does not exist, and it will remember it from 1 to 24 hours.
flowchart LR
device["💻 Your
device"] dns_isp[("🌐 DNS server
of Internet Service Provider")] dns_zone[("🌐 DNS server
of the .COM domain")] device-->dns_isp-.-xdns_zone dns_zone-.-xdns_isp-->device
device"] dns_isp[("🌐 DNS server
of Internet Service Provider")] dns_zone[("🌐 DNS server
of the .COM domain")] device-->dns_isp-.-xdns_zone dns_zone-.-xdns_isp-->device
A similar situation occurs when changing domain records, but, unlike the previous one, the response from DNS-servers of the domain zone (.COM or others) comes with an indication of the server where DNS-records of the requested domain are located, most often it is NS of the hosting provider. In this case, the order of obtaining records for the domain example.com is approximately as follows:
- Your device sends a request to the DNS server of your Internet Service Provider.
- The ISP's DNS server sends a request to the DNS server of the domain zone (in this case, it is the DNS server of the .COM zone).
- The DNS server of the domain zone responds to the ISP's DNS server that the domain data is hosted on the following NS.
- The ISP's DNS server sends a request to the NS reported by the domain zone's DNS server.
- Your ISP's DNS server receives the domain data and transmits it to your device.
- The ISP's DNS server stores this information for future use (the retention period of this information is usually equal to the value of the TTL record).
Then the ISP's DNS server either returns the data from its cache, or performs all requests again. It is impossible to clear the cache of ISP DNS servers, so you need to either wait for them to update their information or use public DNS.
(12)
Comments