DNS webserver, please explain

Started by land_driver, Aug 22, 2022, 04:29 AM

Previous topic - Next topic

land_driverTopic starter

Hey, I'm trying to figure out how to host a website on a server. Here's the short version of what I did:

1. Rented a web server from ubuntu to digitalocean.com.
2. Bought a domain.
3. Instead of using the registrar's own Dns-servers, I used third-party ones (ns1.zilore.net and ns2.zilore.net).
4. Added an a-record for my domain in the control panel of zilore, indicating the ip of my web server.
5. However, when I ping my domain from Windows, it doesn't display the ip of my web server.

I thought that changing the dns servers might take some time, but even after a day, there is still no request to my server. What am I missing in this whole process and why am I not getting any requests?

Also, why can a dns-server for a domain be specified not only on the domain management site but also on the web server management site? For instance, digitalocean offers a section where you can add a domain, register dns (or ns) servers for it, and add A-records of the correspondence between Ip and the domain. I hope you can help me understand this better. Thank you!


If you're having trouble with your DNS host, give it some more time. The issue may actually be with your ISP. If that doesn't work, consider using your registrar's DNS hosting - it's free, though it can crash once a year with all of its servers.

When setting up your website on a server, there are two options: using the server control panel or the hosting control panel on the server itself. With the former, you specify the domain name as the server name for OS installation, while the latter links the domain to a specific site/directory on the server. This is important because the server may have many websites, and without this specification, it will default to the "default virtual host," which is not ideal.

In some cases, the server control panel and hosting service's client panel may be integrated into a single entity.

If you're still having trouble, try using a proxy. It's possible that requests to your site for a domain are taking too long to resolve somewhere.

As an additional note, it's always important to have some basic troubleshooting skills and knowledge when it comes to web hosting and DNS. Knowing how to identify and potentially solve issues can save you a lot of time and frustration.


Following the advice given above, it would be best to wait a little longer as the issue might lie with your Internet service provider. If the problem persists, reach out to their technical support for assistance. Ideally, their administration should be available 24/7.

In the future, it's generally best to avoid using a different company for DNS hosting and instead stick with either your registrar or hoster. Using another company's DNS hoster should only be necessary in certain situations.

It's always important to carefully consider which companies you work with when setting up a website or any kind of online presence. Building a strong foundation from the beginning can help prevent issues down the road. Additionally, understanding the basics of web hosting and DNS can help you troubleshoot any problems that arise.


DNS is a technology that allows you to use human-readable site names in your browser's search bar and the browser to locate the desired website and display it. Essentially, DNS converts domain names entered into the browser search bar into IP addresses of specific servers. This is important because without DNS, you would have to manually remember IP addresses to access specific resources.

Now that we understand the basic principle of operation, where does DNS get its information from? The answer lies in a distributed database stored on DNS servers that form a hierarchy. DNS servers use a TCP/IP stack and a combination of software and hardware responsible for processing DNS queries.

When you enter a query in your browser's search bar, the browser first looks for a DNS record on your local computer in the hosts file. If there's no desired address, the request is sent to the user's Internet provider's local DNS server. From there, if the record isn't found, the request goes higher to the geographical server zones until the necessary DNS record is found. Once the browser receives the IP address, it sends a request to the server for the desired web page.

The DNS query rises from local data stores to the top level, which is faster than making a request first to the root DNS server then going down. Additionally, it's the local DNS server (resolver), not the browser, that polls the DNS servers of the second, upper, and root levels for records. Once a domain's information is found, resolver returns it to the browser and writes it to the cache for 24 hours. While this may slow down the initial request time, this cache can improve future loading speeds since the DNS records are already stored in the cache.

The history of hosts files is interesting; it used to be the only way to avoid remembering IP addresses. Nowadays, it's mostly a historical vestige and is only used for testing and development purposes.

Overall, DNS is an essential component of web browsing and ensures that you can easily access websites without having to remember IP addresses. Understanding how DNS works can help you troubleshoot issues and improve performance.


It seems like you've followed the correct steps to host your website on a server. However, there could be a few reasons why your domain is not resolving to your web server's IP address:

1. DNS Propagation: Changes made to DNS settings can take time to propagate across the internet. Although it typically happens within a few hours, it can sometimes take up to 24-48 hours. You mentioned it has been a day, so it's possible propagation is still in progress.

2. Incorrect DNS Configuration: Double-check the DNS configuration you set up with zilore.net. Ensure that you added the correct A record for your domain and pointed it to the correct IP address of your web server.

3. TTL Value: Time To Live (TTL) is a setting that determines how long DNS information is cached by other DNS servers and devices. If you made recent changes, the TTL value could still be active, causing delays in DNS resolution. Lowering the TTL value before making changes can help propagate updates faster.

Regarding your question about DNS servers, domain management sites and web server management sites often offer options to configure DNS servers for convenience and flexibility. The domain management site allows you to manage DNS records for your domain, while the web server management site allows you to specify DNS servers for the server itself. It's important to ensure that both are configured correctly for your domain to resolve properly.

In summary, double-check your DNS configuration, give it more time for propagation, and consider adjusting the TTL value. If the issue persists, you may want to reach out to your domain registrar or web hosting provider for further assistance.