5 posts tagged with "dns"

Published on May 12, 2026

If you need a dns url redirect, the first thing to clear up is simple: DNS does not redirect web traffic. DNS only answers with records like A, AAAA, or CNAME. The actual redirect happens on a web server, reverse proxy, or registrar feature sitting in front of the domain.

This is where many setups go slightly sideways. A domain owner points a record and expects example.com to forward to www.example.com or to a new site path, but nothing moves. DNS did its job. It translated the name to an IP. It did not tell the browser to go somewhere else.

Published on April 30, 2026

A website restore usually starts at the worst possible moment - after a bad plugin update, a hacked admin account, a broken deployment, or a database mistake that went live before anyone noticed. When that happens, knowing how to restore website backup matters more than having a backup in the first place. The real job is getting your site back online without bringing old problems, missing data, or more downtime with it.

If you are responsible for a business site, online store, SaaS dashboard, or client environment, the safest restore is rarely the fastest click. It depends on what failed, when the issue started, and whether you need to restore the whole site or just one part of it.

In Part 1 of this guide, we configured the firewall and opened the necessary ports for mail delivery. Now that we have made sure that messages are being sent from your server, we need to check that the DNS records are configured correctly. Gmail, Outlook, and other major mail services strictly verify MX, SPF, DKIM, DMARC, and PTR before delivering messages to the primary inbox. Correct records sharply increase the chance that messages will land in the Inbox folder instead of Spam (or be completely rejected).

In the following steps, we will describe how to check the current DNS records of each type and provide recommendations on how to configure them correctly.

If your browser reports DNS_PROBE_FINISHED_NXDOMAIN, it means that it cannot determine the IP address of the requested site. This can happen for a variety of reasons:

• The domain name is not present in DNS servers or its registration has expired.
• The server responsible for the domain zone is unavailable.
• DNS is configured incorrectly on the device.
• Interference from a VPN, antivirus, or firewall.
• Issues with the internet service provider.

The accompanying error message may look slightly different in different browsers:

• Google Chrome: «This site can’t be reached».
• Mozilla Firefox: «Hmm. We’re having trouble finding that site».
• Microsoft Edge: «Hmm… can’t reach this page».
• Safari: «Safari Can’t Find the Server».

Introduction​

If you have ever configured a mail server or encountered reverse DNS checks for other reasons, you have likely heard about PTR records. But what exactly are they? Why can you often not set up a PTR record yourself? Let’s figure it out!