Radar has landed - discover the latest DDoS attack trends. Get ahead, stay protected.Get the report
Under attack?

Products

Solutions

Resources

Partners

Why Gcore

  1. Home
  2. Developers
  3. What Is Domain Name System (DNS)?

What Is Domain Name System (DNS)?

  • By Gcore
  • August 9, 2023
  • 13 min read
What Is Domain Name System (DNS)?

Any time you’re online, you’re using the Domain Name System (DNS) whether you realize it or not! When we’re online, we typically rely on website names, email addresses, or search engines to find what we need and communicate successfully. However, computers operate differently, communicating with each other using a system of numbers known as IP addresses. Finding and remembering a string of random numbers for every website we want to visit would be near-impossible for us. That’s where DNS comes in handy. DNS translates human-readable website names into IP addresses, allowing us to visit websites, send emails, and book flights by remembering just a catchy address, like gcore.com, instead of a string of numbers, like 92.223.84.84. In this comprehensive guide, you’ll learn everything there is to know about DNS, including what it is, how it works, security concerns, and Gcore Hosting benefits.

What Is DNS?

DNS (the Domain Name System) translates user-friendly website names, like www.gcore.com, into numerical IP addresses that computers use to communicate with each other, like 92.223.84.84 or 2a03:90c0:9994::9994. Both your device and the website you want to view have numbers that need to connect. DNS is like the internet’s phonebook, and IP addresses are like phone numbers.

Beyond websites, DNS is used for all online resources, including:

  • Email: When sending an email, your email client uses DNS to look up the Mail Exchange (MX) records of the recipient’s domain. This is how it knows where to send the email.
  • Video conferencing: Apps like Zoom and Microsoft Teams use DNS to connect users to their servers for video meetings.
  • Mobile apps: Apps on your smartphone that connect to the internet use DNS to convert the domain of the web service into an IP address.
  • Online gaming: Games played online use DNS to connect players to game servers.
  • Internet of things (IoT) devices: Smart home devices use DNS to turn a service’s website name into an IP address so they can use internet services.
  • Cloud: Many cloud services rely on DNS to route traffic and perform load balancing across multiple servers or data centers.
  • Content delivery networks (CDNs): CDNs use DNS to direct a client request to the nearest server holding the cached content.
  • VPNs: VPNs use DNS to resolve the domain names of their servers so that users can connect to them.

Users and servers over a network, with IP addresses used to facilitate network connections

DNS is a distributed database, which means that the IP data it holds is spread out across many servers, rather than being stored in one central place. DNS servers are distributed worldwide, managed by different organizations and internet service providers (ISPs.)

How Does DNS Work?

From the user’s point of view, entering a website address into the browser results in an almost instant content display. To go one level deeper, when the user requests a website (for example,) the DNS resolver gets the IP address from the web server, and then returns the information to the user’s device.

A simple illustration of how users access website content via DNS

However, behind the scenes, the DNS resolver performs a critical process called DNS lookup or DNS recursive query, which is central to how DNS operates. Let’s learn about it in more depth.

What Is DNS Lookup?

DNS lookup is when a DNS resolver asks DNS servers to find the IP address or related information of a domain name. When you enter a domain name in your web browser (or any other internet application,) the DNS resolver starts a DNS lookup to query the domain name into its matching IP address, giving you access to the desired content.

How Does DNS Lookup Work?

How DNS lookup works

Here’s how DNS lookup works:

  1. DNS query initiated: When you enter a domain name in your web browser (or any application requiring internet access,) your device initiates a DNS query to find the corresponding IP address.
  2. DNS resolver cache check: The DNS resolver first checks its local cache—the DNS cache—to see if it recently resolved the same domain name. If the information is found in the cache, it can provide the IP address directly without the need for further queries to the name servers; i.e., we can skip to step 6.
  3. Query root name servers: If the domain information is not found in the DNS cache, the DNS resolver queries the root server. The root name server then responds to the resolver’s query with the TLD name server responsible for the specific domain extension. For this one it is “example.com,” so the TLD is “com.”
  4. Contact TLD name servers: The DNS resolver then queries the TLD name servers to obtain the authoritative name servers addresses responsible for the queried domain (e.g., “example.com.”)
  5. Query authoritative name server: The DNS resolver sends a query to one of the authoritative name servers to obtain the IP address associated with the domain name. The authoritative name servers respond to the DNS resolver with the IP address.
  6. Establish connection: Now that the DNS resolver has obtained the IP address “192.0.2.1”, it sends it back to the user’s browser. The resolver will also store this information in the DNS cache respecting the TTL (time to live), which was provided as a part of the authoritative answer. With the IP address, the computer/device can connect to the appropriate server. The web content is then delivered to the device, allowing the user to access the website.

What Are the DNS Record Types?

DNS records consist of the following common record types: A, AAAA, CNAME, MX, NS, and TXT. Each record is used to store a different type of information about domain names and the resources connected to them, such as an email service or a website’s IP address. DNS records are usually held and managed by the domain registrar or the domain’s authoritative name servers. Let’s explore the specific functions of each of these DNS records in the table below.

DNS Record TypePurposeExample
ATranslates a domain name into an IPv4 addressA record for “example.com” pointing to “192.168.1.1”
AAAATranslates a domain name to an IPv6 addressAAAA record for “example.com” pointing to “2001:0db8:85a3::8a2e:0370:7334”
CNAMECreates an alias for a domain nameCNAME record for “shop” to example.com domain name pointing to “website-builder.ursite.com”
MXShows which mail servers are in charge of receiving emailsMX record for “example.com” pointing to “mail.example.com”
TXTStore text information for various purposes such as SPF configuration or domain name verificationTXT record for “example.com” with an email SPF configuration
NSStands for “name servers;” specifies authoritative name servers for the domain nameNS record for “example.com” pointing to “ns1.example.com” and “ns2.example.com”
SOAProvides essential parameters for the zone, including primary name server and administrator email addressProvides essential parameters for the zone (e.g., ns1.example.com, admin.example.com)

Most domains typically have multiple DNS record types in the zone file, including at least two NS (name server) records. The purpose of having multiple authoritative name servers is to create redundancy, in case one name server is temporarily unavailable, and enhance the availability and reliability of the DNS resolution process for the domain. This redundancy helps to distribute the DNS query load, making the domain more robust and resilient against potential server outages or network issues.

What Are the Components of DNS?

DNS is composed of several key components that work together to facilitate the translation of human-readable domain names into numerical IP addresses. The main DNS components are as follows:

#1 IP Address

IP address, or Internet Protocol address, is a unique set of numbers that identifies any device connected to a computer network. It serves as an identifier for that device, allowing it to send and receive data over the internet or a local network.

A lot of IP address activity happens behind the scenes. You don’t need to remember your device’s IP address or the website’s IP address to connect. DNS handles this for you, ensuring the right IP addresses are used to connect devices and exchange data smoothly. You also don’t usually need to think about your devices’ IP addresses; when you connect to a network, like home Wi-Fi, the router automatically assigns your device an IP address.

What Are IPv4 and IPv6?

Currently, there exist two versions of IP addresses: IPv4 and IPv6 (IP version 4 and IP version 6.) A single device can be assigned both an IPv4 and an IPv6 address.

IPv4 consists of four numbers separated by dots, like this: XXX.XXX.XXX.XXX. Each set can have a value from 0 to 255. For example, an IPv4 address could be 192.168.1.10.

IPv6 is the newer version of the Internet Protocol, created because the number of IPv4 addresses was running out. IPv6 consists of eight groups of four hexadecimal digits separated by colons. For example, an IPv6 address could be 2001:0db8:85a3:0000:0000:8a2e:0370:7334.

Types of IP Address

There are two types of IP address: public and private.

  1. Public IP address: This is a unique set of numbers assigned by your Internet Service Provider (ISP) to your router, which is connected to the internet. It works like a digital “address” for that device, allowing it to communicate with other devices and services on the global internet.
  2. Example: Imagine you have home internet, and your ISP named XYZ Internet Company gives your router a unique public IP address. Here’s what it looks like:
ISP ProviderPublic IP Address
XYZ Internet Company203.56.78.123

203.56.78.123 is your home’s digital address on the internet. When you visit a website, your device uses this address to connect to the website’s server, just like giving someone your home address so they can locate and visit you.

  1. Private IP address: This is a special set of numbers assigned to a device, like a computer within a private network. It is not visible or accessible from the internet. Instead, private IP addresses act as a means for devices in the same network to find and talk to each other.
  2. Example: Let’s say you need to set up an office. A network administrator can set up private IP addresses so that your office’s devices are connected to a local network. Here’s what that looks like:
DevicesPrivate IP Address
Laptop192.168.1.10
Printer192.168.1.30
Network Storage192.168.1.50

In this home office network example, each device is assigned a unique private IP address using the formula 192.168.1.X, where X is a different number per device. These private IP addresses enable seamless communication, data sharing, and collaboration among the devices within the local network.

DNS translates all of these complex numbers into a human-readable format, so we don’t need to keep track of all of these IP addresses for us to connect to the internet!

#2 Domain Name

A domain name is a simple, memorable name that is used to access online resources such as websites and email servers. Examples of domain names include “example.com,” “example.org,” and “example.net.” A domain is structured into different parts, separated by dots. Each part has a specific purpose and contributes to the overall hierarchical structure of the domain name. Here’s the typical structure of a domain name:

A fully-qualified domain name structure

Let’s break this down:

  • Root domain. The root domain is the base domain name without any subdomains. It is the main part of the domain name that represents the website’s identity. For example, in the “www.example.com,” “example.com” is the root domain.
  • Top-level domains (TLDs): This is the last part of a domain name that appears to the right of the furthest right “dot” symbol. TLDs are essential for categorizing and organizing domain names on the internet. Here are some common examples of TLDs:
Top Level Domains (TLD)Description
.comCommercial; commonly used for businesses and commercial websites
.orgOrganization; often used by non-profit organizations and non-commercial entities
.netNetwork; originally intended for network-related websites
Country-code top-Level Domains (ccTLDS)Description
.usCountry code TLD for United States
.ukCountry code TLD for United Kingdom
.caCountry code TLD for Canada

As of July 2023, China’s country code top-level domain (ccTLD) .cn is the most popular worldwide, with almost 30 million registered domains.

  • Second-level domain: A second-level domain is a part of the domain name that appears to the left of the top-level domain (TLD) and is located immediately to the left of the rightmost “dot” symbol. For instance, in the domain “gcore.com,” “gcore” is the second-level domain. Second-level domains serve as specific identifiers for websites, organizations, or individuals. Here are some additional examples below:
Domain NameSecond-Level Domain
gcore.comgcore
linux.orglinux
gov.ukgov
  • Subdomain (third-level domain): The subdomain, also known as third-level domain, is located to the left of the main domain and separated from it by a dot. Subdomains help to organize sections of a website with distinct web addresses. They appear before the main domain in a URL, allowing site owners to keep sections connected to the main domain. For instance, in “blog.example.com,” “blog” is the subdomain, “example” is the second-level domain, and “.com” is the TLD.

Fully-qualified domain example
Example URLSubdomain
www.example.comwww
support.example.netsupport
forum.example.orgforum

#3 DNS Resolver

A DNS resolver or DNS recursor is a server which executes the process of requesting information from authoritative DNS servers to find the IP addresses for domain names. When you enter a domain name in your web browser or perform an action requiring DNS resolution, the DNS resolver first checks its local cache—a temporary storage mechanism—to see if it recently resolved the same domain name. If the information is not found in the cache, the resolver looks for the corresponding IP address by initiating a DNS lookup.

#4 Servers

Specialized servers store and provide DNS information for specific domain names. They are managed by domain registrars, web hosting or cloud providers, or organizations. They work according to a hierarchy, starting from the highest level root name servers, then top-level domain (TLD) name servers, and finally to authoritative name servers for specific domains.

DNS server hierarchy

Each domain has multiple authoritative name servers associated with it. These authoritative name servers are responsible for holding the DNS records containing the corresponding IP address.

Let’s look at each level of the hierarchy in more depth.

  • Root name servers: These are the highest-level DNS servers in the hierarchy, providing information about top-level domain (TLD) name servers. When a DNS resolver needs to find a domain’s IP address, it contacts a root name server, which then directs the resolver to the appropriate TLD name server based on the domain’s extension (e.g., .com, .net, .org.) There are thirteen operators of root name servers worldwide.
  • Top-level domain (TLD) name servers: These servers handle the next level in the DNS hierarchy. They are responsible for specific domain extensions like .com, .org, .net, and country-code TLDs (ccTLDs) like .uk, .ca, etc. Each TLD name server is responsible for storing information about the domain names registered under that specific TLD. The Internet Assigned Numbers Authority (IANA) maintains a list of root zone databases.
  • Authoritative name servers: Authoritative name servers are responsible for storing and supplying specific and definitive DNS records from the second level onwards, including the IP address for the domain. They are officially appointed by either the domain owner or the domain’s registrar. For example, if our Gcore clients wish to use our DNS service, they are required to modify their name server details at the location they originally bought their domain, which is the domain registrar. Here’s what the authoritative name servers looks like:
Authoritative name serversValue
NS1ns1.gcorelabs.net
NS2ns2.gcdn.services

#5 DNS Zone File

A DNS zone file can be likened to an organized filing cabinet. It is a plain text document that houses critical information about a domain name. This file includes resource records, which enable the efficient pairing of domain names with their related requests, streamlining the process of finding what you need.

How a DNS zone file works

Every domain has a zone file of its own, containing different kinds of DNS resource records that describe the domain’s setup. The structure and language used in the zone file follow DNS standards such as RFC 1034 and RFC 1035, which define the architecture and specifications of DNS. This ensures that any DNS file can be easily read and interpreted by all DNS servers and other DNS-related software.

Here’s an example of a DNS zone file:

Components of DNS zone file

Let’s learn what each part means:

  1. Time to live (TTL): The initial line, “$TTL 3600,” establishes the zone’s default time to live (TTL) duration, which is 3600 seconds (1 hour.) The TTL determines how long DNS resolvers should store the records in their cache before looking for new information.
  2. Start of authority (SOA) record: The start of authority (SOA) record sets important details for the zone, like the main name server (ns1.example.com, ns2.example.com) and the email address of the zone’s administrator.
  3. Name server (NS) records: These records are the authoritative name servers that handle the DNS queries such as “ns1.example.com” and “ns2.example.com.”
  4. Address (A) records: This is a type of DNS resource record that maps a domain name to the corresponding IP address of the server hosting the domain. In our example above, the label “@” represents the origin of the domain, e.g., “example.com”), so that the domain itself is mapped to the IP address 192.168.1.10. Additionally, “www.example.com” and “mail.example.com” are mapped to their respective IP addresses.
  5. Mail exchange (MX) records: MX records define the mail servers responsible for receiving email messages for the domain. In this example, all emails for “example.com” will be delivered to the mail server “mail.example.com.”
  6. Canonical name (CNAME) records: CNAME records create aliases or alternate names for specific domain names. They point to the canonical (primary) name of another domain. In the example above, the CNAME record creates an alias for the domain name “ftp.example.com,” pointing it to the same IP address as “www.example.com.”

What Are DNS Attacks?

Since DNS is considered as a backbone of the internet, it is prone to attacks with potentially devastating effects. Tunneling attacks, malware, and DNS flooding are some of the risks associated with DNS. These can impact business owners who manage online services and websites. Potential disruptions as a result of a DNS attack include website service interruption, data breaches, and domain reputation damage, rendering DNS security measures essential.

Here are some of the most common DNS attacks:

DNS AttackDescription
DNS cache poisoningAttackers insert fake information into DNS caches, causing domain names to be resolved incorrectly. By manipulating the cached data in DNS resolvers, they can redirect users to malicious websites, intercept sensitive data or cause a denial of service attack. This attack type exploits vulnerabilities in DNS resolvers and can spread rapidly, affecting a large number of users. Example: Attackers targeted XYZ Company, a file sharing website, by compromising DNS records and injecting malicious data into the DNS resolver’s cache. This manipulation led to the legitimate domain name of XYZ Company being associated with a fake IP address controlled by the attackers.
DNS spoofingMalicious entities create fake DNS responses, leading users to be redirected to fraudulent websites or unintended destinations. In this DNS attack, attackers exploit DNS vulnerabilities to inject fake DNS responses into caches, redirecting users to deceptive destinations. This can result in users unknowingly sharing sensitive information with malicious sites or downloading harmful content. Example: Cybercriminals executed a DNS spoofing attack on ABC-Shop, an e-commerce platform. The attackers used fake DNS responses into the cache that led users to redirect them to the attacker’s website where it posted fake products, instead of to ABC-Shop. The attackers thereby stole customers and damaged ABC-Shops’ reputation with fake, subpar quality goods.
DNS reflectionThis is a type of DDoS attack where the attacker sends fake DNS requests to public DNS servers, using the victim’s IP address as the source. The DNS servers then respond to the victim’s IP, generating a massive flood of responses that overwhelms the victim’s network. Example: TechZone, a computer repair chain, experienced a DNS reflection attack where attackers flooded public DNS servers with fake requests, spoofing TechZone’s IP address. The flood of responses overwhelmed TechZone’s network, disrupting their online services, causing financial losses.
DNS floodingDNS flooding is a type of cyberattack that overwhelms DNS servers with a high volume of request, causing disruptions to services. Malicious actors use techniques like botnets to generate a massive number of DNS queries, exhausting server resources and rendering legitimate services unavailable. Example: Gaming-ABC is a gaming company that was targeted by malicious actors, who flooded its DNS servers with a massive volume of queries using a botnet. The overwhelming number of requests disrupted Gaming-ABC’s DNS infrastructure, causing service disruptions for players trying to access the games.
DNS malwareDNS malware refers to harmful software that alters DNS settings to redirect users to malicious websites. When a device is infected, the malware replaces legitimate DNS servers with unauthorized or malicious ones. Users are unknowingly redirected to fraudulent sites, leading to phishing attacks or malware distribution. To protect against DNS malware, users should update security software and be cautious with links and downloads. Example: Toys Co faces a DNS malware attack when an employee’s device becomes infected. The DNS malware redirects DNS queries to malicious servers controlled by attackers. This leads Toys Co to experience data theft and compromised business operations.

Reliable DNS hosting, a DNS firewall, and mitigation solutions are essential measures to combat cybercrimes and address DNS security concerns.

At Gcore, our mission is to deliver a fast, reliable internet experience for users and create a safe online space for businesses to offer their products and services, free from worries about DNS attacks. Let’s explore how Gcore assists in mitigating DNS security risks and helps your business to succeed in a volatile cybersecurity environment.

Gcore DNS Hosting Benefits

At Gcore, we ensure that your website performance is consistent and outstanding with our DNS Hosting. We provide services to keep you safe from DNS attacks, ensuring that your website stays safe and your customers can always enjoy your business without experiencing downtime.

Let’s explore some key features of Gcore DNS hosting:

Gcore DDoS- and Bot-Protected DNS Hosting

Our DNS Hosting service leverages anycast network technology with hundreds of global nodes, providing superior security and unmatched resilience, even against the most extreme DDoS attacks. We ensure that only legitimate traffic reaches your website. Without proper DDoS protection, your website is vulnerable to DNS attacks that can cause your website to become unavailable to your visitors.

Another security concern is DNS flooding, a type of DDoS attack that employs botnets to generate an overwhelming number of DNS queries, causing resource exhaustion and preventing legitimate users from accessing the website. Website owners are rightly concerned about such an attack, since downtime means lost revenue and lost customers. Gcore Bot Protection defends against this risk.

Gcore DDoS-protected DNS Hosting

Gcore Geobalancing

GeoDNS or Geo Balancing is a DNS capability that leverages the client’s geographical location to deliver personalized DNS responses. Geobalancing is Gcore’s specialized product in this arena. It directs users to the closest or most suitable server based on their geographic region, improving the performance of online services and reducing latency. Users from Asia will be directed to an Asian server, while European users will be sent to a European server. This ensures a better user experience and improved efficiency for your online services.

Gcore’s GeoDNS directs users to their nearest DNS server

Gcore DNS Failover

DNS failover ensures that your business services remain accessible even during server outages. If any of your servers experience downtime, our failover system kicks in automatically, seamlessly redirecting user requests to an available server. This ensures uninterrupted service performance, safeguarding your business operations and customer experience.

DNS failover process

Gcore DNS Advanced Features

Gcore DNS advanced features offer enhanced security and performance measures:

Learn more about Gcore’s DNS solution for an exceptional DNS experience.

Conclusion

DNS plays a critical role in the functioning of the internet, translating human-readable domain names into numerical IP addresses, allowing seamless communication between devices and access to online services. However, DNS management comes with risks, such as DNS attacks that can disrupt services and compromise data security.

At Gcore, we prioritize fast and secure internet using comprehensive DNS solutions like DNS failover, Geobalancing, and anycast network. Trusting us with your DNS management means you can focus on your core business, knowing your website is performing and protected to the highest standard. If you’re interested in learning more or setting up DNS Hosting with us, reach out to our experts.

Explore Gcore DNS

Related articles

How do CDNs work?

Picture this: A visitor lands on your website excited to watch a video, buy an item, or explore your content. If your page loads too slowly, they may leave before it even loads completely. Every second matters when it comes to customer retention, engagement, and purchasing patterns.This is where a content delivery network (CDN) comes in, operating in the background to help end users access digital content quickly, securely, and without interruption. In this article, we’ll explain how a CDN works to optimize the delivery of websites, applications, media, and other online content, even during high-traffic spikes and cyberattacks. If you’re new to CDNs, you might want to check out our introductory article first.Key components of a CDNA CDN is a network of interconnected servers that work together to optimize content delivery. These servers communicate to guarantee that data reaches users as quickly and efficiently as possible. The core of a CDN consists of globally distributed edge servers, also known as points of presence (PoPs):Origin server: The central server where website data is stored. Content is distributed from the origin to other servers in the CDN to improve availability and performance.Points of presence (PoPs): A globally distributed network of edge servers. PoPs store cached content—pre-saved copies of web pages, images, videos, and other assets. By serving cached content from the nearest PoP to the user, the CDN reduces the distance data needs to travel, improving load times and minimizing strain on the origin server. The more PoPs a network has, the faster content is served globally.How a CDN delivers contentCDNs rely on edge servers to store content in a cache, enabling faster delivery to end users. The delivery process differs depending on whether the content is already cached or needs to be fetched from the origin server.A cache hit occurs when the requested content is already stored on a CDN’s edge server. Here’s the process:User requests content: When a user visits a website, their device sends a request to load the necessary content.Closest edge server responds: The CDN routes the request to the nearest edge server to the user, minimizing travel time.Content delivered: The edge server delivers the cached content directly to the user. This is faster because:The distance between the user and the server is shorter.The edge server has already optimized the content for delivery.What happens during a cache miss?A cache miss occurs when the requested content is not yet stored on the edge server. In this case, the CDN fetches the content from the origin server and then updates its cache:User requests content: The process begins when a user’s device sends a request to load website content.The closest server responds: As usual, the CDN routes the request to the nearest edge server.Request to the origin server: If the content isn’t cached, the CDN fetches it from the origin server, which houses the original website data. The edge server then delivers it to the user.Content cached on edge servers: After retrieving the content, the edge server stores a copy in its cache. This ensures that future requests for the same content can be delivered quickly without returning to the origin server.Do you need a CDN?Behind every fast, reliable website is a series of split-second processes working to optimize content delivery. A CDN caches content closer to users, balances traffic across multiple servers, and intelligently routes requests to deliver smooth performance. This reduces latency, prevents downtime, and strengthens security—all critical for businesses serving global audiences.Whether you’re running an e-commerce platform, a streaming service, or a high-traffic website, a CDN ensures your content is delivered quickly, securely, and without interruption, no matter where your users are or how much demand your site experiences.Take your website’s performance to the next level with Gcore CDN. Powered by a global network of over 180+ points of presence, our CDN enables lightning-fast content delivery, robust security, and unparalleled reliability. Don’t let slow load times or security risks hold you back. Contact our team today to learn how Gcore can elevate your online presence.Discover Gcore CDN

What is a CDN?

Whether you’re running an e-commerce store, streaming videos, or managing an app, delivering content quickly and reliably is essential to keeping users satisfied. This is where a content delivery network (CDN) comes into play. A CDN is a globally distributed network of servers that work together to deliver content to users quickly, minimizing latency. Instead of relying on a single server, a CDN uses edge servers—called points of presence (PoPs)—to cache or temporarily store copies of your content closer to the user. This optimizes website performance, drastically cuts down on load times, and improves the user experience. Research suggests that a one-second lag in page loading speed can significantly decrease engagement, citing a 7% decline in conversions and an 11% decrease in page visits. CDNs considerably speed up load times by reducing latency through content caching closer to the user. By splitting up your website’s traffic over several servers, CDNs also protect it from online threats. Distributed denial-of-service (DDoS) attacks are lessened by CDNs because they spread traffic among a network of servers, improving security and availability. What Challenges Do CDNs Address?CDNs tackle two key challenges to improve website and application performance: Slow load times: Users sometimes experience frustratingly slow-loading websites and applications. This is because data must travel from a server to the end user’s device, causing latency. CDNs move servers closer to end users, reducing the distance that data has to travel and speeding up load times.  High traffic volumes: High traffic volumes during peak times or cyberattacks can overwhelm your website and lead to latency or site unavailability. Since CDNs distribute traffic across multiple servers, no single server is overwhelmed. This helps prevent crashes and delivers smooth performance for all users.Common Use Cases for CDNsCDNs are vital across a range of industries, providing measurable improvements in content delivery and user experience. E-commerce websites use CDNs to guarantee quick page loading and frictionless shopping experiences, even during periods of high traffic. Speed is crucial for online businesses. A study found that the average cost of downtime for e-commerce websites is around $500,000 per hour. This includes lost sales, operational costs, and long-term damage to brand reputation Streaming services rely on CDNs to deliver high-quality video content while minimizing buffering. Netflix states that its CDN contributes to the daily delivery of over 125 million hours of streaming content, guaranteeing a seamless experience for customers worldwide. Gaming companies use CDNs to lower latency and provide a consistent real-time user experience, especially during live multiplayer matches, where it is essential to preserve an engaging and fair gameplay experience. News outlets and blogs benefit from CDNs by ensuring their content loads quickly for readers around the world, during large-scale traffic surges, especially during major events like elections or breaking news.  The Benefits of a CDNFaster Website PerformanceEvery second counts when delivering content online. Slow websites frustrate users and harm your business. CDNs speed up content delivery by caching data closer to users, reducing page and file load times. Whether you’re delivering static content (such as CSS, HTML or JPG files) or dynamic content (like data generated by user interactions or API calls), a CDN ensures optimal performance regardless of user location. While factors like DNS settings, server configurations, and code optimization all play a role, the physical distance between your origin server and your users is a factor that only a CDN can solve. Increased Availability and ReliabilityDowntime can seriously affect online businesses. Hardware failures, traffic surges, and cyberattacks can reduce your website’s availability, harming your customers’ experience and causing financial or reputational damage. In fact, around 98% of organizations report that just one hour of downtime costs over $100,000. A CDN ensures that your website remains available, fast, and reliable by leveraging essential features such as: Load balancing: This process dynamically distributes traffic across multiple servers to optimize performance and prevent overload.Intelligent failover: Automatically redirects traffic if a server goes offline, ensuring continuity with minimal disruption.Anycast routing: Directs users to the closest or most efficient server, further reducing latency and enhancing response times.Security FeaturesAs cyber threats continue to grow in sophistication and frequency, securing your website or application is more critical than ever. According to recent statistics from Cobalt’s 2024 Cybersecurity Report, weekly attacks worldwide increased by 8% in 2023, while attackers used more sophisticated strategies to exploit vulnerabilities. Strong security measures that not only safeguard your website but also guarantee optimal performance are necessary in light of these evolving threats. CDN security features not only improve website performance but also defend against a wide range of attacks by distributing traffic across multiple servers, which mitigates DDoS attacks and filters out malicious traffic before it reaches your website. These features, from DDoS protection to safeguarding APIs, help maintain uptime, protect sensitive data, and guarantee a seamless user experience. Most modern solutions like Gcore CDN integrate robust security measures into content delivery, such as:SSL/TLS encryption facilitates secure data transmission by encrypting traffic, protecting sensitive information from being intercepted.L3/L4 DDoS protection blocks large-scale cyberattacks designed to flood your network and disrupt services.L7 DDoS protection guards your website from more complex attacks targeting how the website functions, helping it continue to operate smoothly.Web application firewall (WAF) acts as a shield, blocking harmful traffic such as hacking attempts or malicious scripts before they can affect your site.API security protects the communication between your application and other software, preventing unauthorized access or data theft.Bot protection identifies harmful automated traffic (bots), preventing activities like data scraping or login attempts with stolen credentials while allowing useful bots (like search engine crawlers) to function normally. Elevate Your Online Experience With a CDNA CDN is no longer a luxury—it’s a necessity for businesses that want to deliver fast, reliable, and secure online experiences. Whether your goal is to optimize performance, manage high traffic, or protect your site from attacks, a well-configured CDN makes all the difference.Ready to enhance your website’s performance? Our futureproof CDN runs on a global network of over 180 points of presence, so your customers get outstanding performance no matter where in the world they’re located. Get in touch with our team today to learn how our CDN can benefit your business.Discover Gcore CDN

How to Migrate Your Video Files to Gcore Video Streaming

Migrating large volumes of video files from different platforms can be daunting and time-consuming, often discouraging companies from moving to a superior provider. But it doesn’t have to be this way. We’ve created this three-step guide to help you efficiently migrate your video files to Gcore from other popular streaming platforms.Step 1: Get Links to Your VideosFirst, obtain links to your videos and download them. Look for your provider in the list below, or refer to the general SFTP/S3 storage section if applicable. After completing the steps for your provider, go straight to step 2.Google DriveShare the file: Open Google Drive and locate the MP4 file you want to download. Right-click on the file and select “Share.”Get the shareable link: In the sharing settings, click “Get link.” Ensure the link-sharing option is turned on.Set sharing permissions: Adjust the sharing permissions so “Anyone with the link” can view or download the file. Copy the generated link.Amazon S3Edit S3 block public access settings: Go to the S3 management console, select the bucket containing your MP4 file, and edit the Block Public Access settings if necessary.Add a bucket policy: Implement a bucket policy that grants public read access to your files.Get the list of objects: Navigate to the Objects tab, find your MP4 file, and click on the file to obtain the Object URL, which will be your download link.VimeoAccess the video: Log in to your Vimeo account and go to the video you wish to download.Select options: Click on the “Settings” button (gear icon) below the video player.Get video file link: In the settings menu, go to the “Video File” tab, where you can find the download link for your MP4 file.MUXEnable master access: Log in to your MUX account, navigate to the video asset, and enable master access if it’s not already enabled.Retrieve URL to master: Once master access is enabled, the URL to the master file will be available in the video asset details. Copy this URL for downloading the file.DropboxCreate a shareable link: Log in to your Dropbox account and locate the MP4 file you want to share. Click on the “Share” button next to the file.Set access permissions: In the sharing settings, create a link and set the permissions to “Anyone with the link.” Copy the generated link to download the file.General SFTP or S3 StorageAccess storage: Log in to your SFTP or S3 storage service control panel.Manage buckets/directories: Navigate to the appropriate bucket or directory containing your MP4 files.Retrieve download links: Generate HTTP/S links for the files you want to download. You can then use these links to download the files directly.Step 2: Check Availability to DownloadEnsure that your video files are available and ready for download, preventing any interruptions or issues during the migration process.Open HTTP/S link in a browser: Copy the HTTP/S link for the MP4 file and paste it into your browser’s address bar. Press Enter to navigate to the link.Check the video plays correctly in the browser: Verify that the video starts playing once the link is opened. This step ensures that the file is accessible and the link is functioning properly.Right-click to download: While the video is playing, right-click on the video player. Select “Save video as…” from the context menu. Choose a destination on your local disk to save the MP4 file.Step 3: Upload to Gcore Video StreamingNo matter which provider you’re migrating from, you need to upload your videos to Gcore Video Streaming storage. There are three primary methods to upload videos to Gcore storage:Copy from external storage: If your videos are available via public HTTPS URLs, you can directly copy the video files from external storage to Gcore. This method efficiently transfers files without downloading them to your local device first.Upload from a local device: Videos can be uploaded from your local host, backend, browser, or mobile app using the TUS resumable upload protocol. This method is resilient to interruptions, ensuring a smooth upload process by resuming from the point of failure.Batch upload: This method will soon be available to migrate extensive collections of videos, allowing you to transfer vast numbers of video files efficiently.The simplest migration option is to obtain video URLs and copy them to Gcore Video Hosting, eliminating the need to download and reupload videos.Example API Request to Copy Video from External StorageTo copy a video from another server, specify the origin_url attribute in the POST API request. The original video will be downloaded for video hosting on our server. Here is an example of the API request to set a task for copying a video from external storage:curl -L 'https://api.gcore.com/streaming/videos/' \-H 'Content-Type: application/json' \-H 'Authorization: APIKey 1234$0d16599c' \-d '{ "video": { "name": "Gcore Demo", "description": "Video copied from an external S3 Storage", "origin_url": "https://s-ed1.cloud.gcore.lu/demo-video/gcore.mp4" } }Refer to the complete documentation for detailed steps and examples of API requests. The original file must be in MP4 format or one of the following formats: 3g2, 3gp, asf, avi, dif, dv, flv, f4v, m4v, mov, mp4, mpeg, mpg, mts, m2t, m2ts, qt, wmv, vob, mkv, ogv, webm, vob, ogg, mxf, quicktime, x-ms-wmv, mpeg-tts, vnd.dlna.mpeg-tts. Streaming formats like HLS (.m3u8/.ts) and DASH (.mpd/.m4v) are intended for final video distribution and cannot be used as original file formats. Here are examples of good and bad links:Good link: https://demo-files.gvideo.io/gcore.mp4Bad link (chunked HLS format): https://demo-files.gvideo.io/hls/master.m3u8Note: Currently, only one video can be uploaded per request, so transferring your library in batches will require automation.Migrate to Gcore Video Streaming TodayGcore Video Streaming makes video migration easy with support for multiple sources and automatic transcoding. Whether you’re moving files from cloud storage, hosting platforms, or API-based services, Gcore streamlines video administration. Store, process, and distribute videos in various formats, complete with features like subtitles and timeline previews.With seamless migration and automatic transcoding, Gcore ensures your videos are optimized and ready for distribution, saving you time and effort. Simplify your video management and ensure your content is always accessible and in the best format for your audience with Gcore’s robust video streaming solutions.

5 Ways to Improve Website Speed for E-Commerce

In part 1 of this guide, we explained why site speed matters for e-commerce and how you can track your current speed.Now, speed up your page load times with these five techniques.#1 Assess Your Current Site SpeedFirst, check your site’s current performance. Use tools like Google PageSpeed Insights or real user monitoring (RUM) tools. PageSpeed Insights evaluates individual web pages for mobile and desktop performance, providing actionable insights to improve speed and user experience.Here’s an example of how your metrics might look:#2 Adopt Code and Image Optimization TechniquesE-commerce websites often have a huge number of images, videos, and/or animations, which can slow down load times. Since these media are essential, the key is to optimize all heavy components.Compress images and use lazy loading via your website host. Minimize redirects and remove broken links, consulting a technical SEO expert if required. These actions can significantly reduce page weight.#3 Adopt CDNs and Edge ComputingThe majority of online shoppers have purchased from an e-commerce store in another country and an additional 22% plan to in the future. Hosting location impacts speed. The further your servers are physically located from your customers, the higher the latency. So, having servers distributed globally improves your load speed and allows you to deliver great customer experiences, no matter where your customers are located.Imagine that your e-commerce website is hosted on a web server in the US, but you have shoppers from the EU. When shoppers from the US browse your store, they may not experience much latency. But shoppers from Germany will, because of the time it takes their browser to send requests to your US server, wait for the server to process them, and deliver a response. A reliable CDN and edge computing provider caching your website content—images, videos, payment portals and all—at the edge makes for speedy content delivery globally.In addition to shortening the distance between your servers and buyers, CDNs also enable load balancing. Say you’re running a Black Friday sale with traffic surges far beyond your normal quantities. Your CDN provider can distribute the traffic evenly between its network of available servers, preventing any one server from being overworked, thereby improving server response times. So, if your Black Friday surge comes mostly from the New York area, a CDN can push some of that traffic from the New York, NY server to the nearby Manassas, VA and Boston, CT servers. Customers won’t notice a difference since both servers are nearby, but spreading the load means all servers continue to perform optimally.#4 Use Fast Authoritative DNSDNS is like the internet’s phone book, translating human-friendly domain names (like www.example.com) into IP addresses that computers use to find each other. When this translation happens quickly, it reduces the time it takes for a user’s browser to locate your website, leading to faster page load times.#5 Rinse and RepeatSite speed optimization is continuous. The internet changes daily; technology advances and competitors emerge. Don’t get comfortable with your site speed. Continuously track speed scores and make improvements.Website Speed Solutions in One Intuitive PlatformWebsite speed is a game-changer for e-commerce success. A website that loads in under a second is the magic number to boost user experience, slash bounce rates, and skyrocket your e-commerce business’ conversion rates.Stay ahead of your e-commerce competitors by choosing tools and platforms designed with your e-commerce website speed in mind. With 180+ PoPs worldwide and a 200+ Tbps network capacity, Gcore CDN and DNS are ideal speed optimization solutions for global e-commerce sites. Contact us today to discover how we can supercharge your site speed.Explore CDN for e-commerce

What Website Speed Is and Why It Matters for E-commerce Success

Website visitors are more impatient than ever—websites that take longer than three seconds to load lose more than half their visitors. For an e-commerce business, that translates to losing half its potential sales, which is bad news for revenue. In this article, we explain what e-commerce website speed is, how it’s measured, and how you can improve it for better customer retention and higher sales.Why Does Site Speed Matter?Website speed measures the time from when visitors click your link to when they see a fully functioning page. With the surge in e-commerce businesses around the world, buyers have many choices and will quickly abandon slow-loading websites out of frustration. Most customers won’t return to a slow website, and 89% will turn to a faster competitor. Satisfied customers are more likely to recommend your website to others, making high user satisfaction an effective marketing strategy.Just a second—or less—of load time can make the difference between a potential customer purchasing from you or your competitor. Conversion rates drop markedly with every additional second of load time. If your site loads in one second or less, you’re looking at a 3% conversion rate. That almost halves when you add just one second of wait time.That’s not surprising, since churn and bounce rates increase with slower load times, meaning potential buyers either leave your site before interacting and/or don’t return.Page load times also affect search engine optimization (SEO) rankings—your spot on search engine results pages. When buyers search for your products, if you don’t appear at the top, your competitors will—and your customers are more likely to visit their site instead of yours.Evidently, optimizing page load time is a non-negotiable for any e-commerce business.Metrics and Indicators to TrackSpeed can be measured and reflected by either technical or business metrics.Technical IndicatorsGoogle Core Web Vitals are metrics that measure various features contributing to a high-quality page experience. They’re an industry-standard way to measure your technical website load speed.Largest contentful paint (LCP) is the time it takes for the largest content on your site to load. An ideal LCP value is below 2.5 seconds, while above 4 seconds signals a poor page experience.First input delay (FID) is the delay between a user’s interaction (e.g., clicking a button) and the browser’s response. Google considers any FID value below 100 ms good, and above 300 ms poor.Cumulative layout shift (CLS) measures how much your content moves around while loading. Poor CLS can cause users to accidentally click on the wrong buttons.Keep track of the following additional technical metrics:Time to first byte (TTFB) is the time between a browser requesting your webpage and the first byte of data arriving. It often triggers the “reduce initial server response time” message in page speed diagnostics.Time to interactive (TTI) measures the time it takes for your website to become fully interactive. Google considers a TTI of below 5 seconds good, and above 7.3 seconds poor.Round-trip time (RTT) is the time it takes for requests to reach the origin server, be processed, and return to the client.Business MetricsThese metrics give you insights into how your website’s speed impacts sales. Although they’re not a direct speed measurement, speed has a direct impact on them.Conversion rate measures the percentage of your website’s visitors who make a purchase.Engagement time measures how much time customers actively spend on your website, such as browsing products or making a purchase. It’s connected to bounce rate, which is the opposite—how many customers leave your site without engaging at all, often caused by slow loading.Search ranking affects your site’s visibility, traffic, and revenue. Fast load times contribute to better SEO rankings.Explore part 2 of this guide to discover 5 practical tips to speed up your e-commerce website performance.

Improve Your Privacy and Data Security with TLS Encryption on CDN

The web is a public infrastructure: Anyone can use it. Encryption is a must to ensure that communications over this public infrastructure are secure and private. You don’t want anyone to read or modify the data you send or receive, like credit card information when paying for an online service.TLS encryption is a basic yet crucial safeguard that ensures only the client (the user’s device, like a laptop) and server can read your request and response data; third parties are locked out. You can run TLS on a CDN for improved performance, caching, and TLS management. If you want to learn more about TLS and how running it on a CDN can improve your infrastructure, this is the right place to start.What Is TLS Encryption and Why Does It Matter?TLS, transport layer security, encrypts data sent via the web to prevent it from being seen or changed while it’s in transit. For that reason, it’s called encryption in-transit technology. TLS is also commonly called HTTPS when used with HTTP or SSL, as previous versions of the technology were based on it. TLS ensures high encryption performance and forward secrecy. To learn more about encryption, check out our dedicated article.TLS is a vital part of the web because it ensures trust for end users and search engines alike. End users can rest assured that their data—like online banking information or photos of their children—can’t be accessed. Search engines know that information protected by TLS is trustworthy, so they rate it higher than non-protected content.What’s the Connection Between TLS and CDN?A CDN, or content delivery network, helps improve your website’s performance by handling the delivery of your content from its own servers rather than your website’s server. When a CDN uses TLS, it ensures that your content is encrypted as it travels from your server to the CDN and from the CDN to your users.With TLS offloading, your server only needs to encrypt the content for each CDN node, not for every individual user. This reduces the workload on your server.Here’s a simple breakdown of how it works:Your server encrypts the content once and sends it to the CDN.The CDN caches this encrypted content.When a user requests the content, the CDN serves it directly to them, handling all encryption and reducing the need to repeatedly contact your server.Without a CDN, your server would have to encrypt and send content to each user individually, which can slow things down. With a CDN, your server encrypts the content once for the CDN. The CDN then takes over, encrypting and serving the content to all users, speeding up the process and reducing the load on your server.Figure 1: Comparison of how content is served with TLS on the web server (left) vs on CDN (right)Benefits of “Offloading” TLS to a CDNOffloading TLS to a CDN can improve your infrastructure with improved performance, better caching, and simplified TLS management.Increased PerformanceWhen establishing a TLS connection, the client and server must exchange information to negotiate a session key. This exchange involves four messages being sent over the network, as shown in Figure 2. The higher the latency between the two participants, the longer it takes to establish the connection. CDN nodes are typically closer to the client, resulting in lower latency and faster connection establishment.As mentioned above, CDN nodes handle all the encryption tasks. This frees up your server’s resources for other tasks and allows you to simplify its code base.Figure 2: TLS handshakeImproved CachingIf your data is encrypted, the CDN can’t cache it. A single file will look different from the CDN nodes for every new TLS connection, eliminating the CDN benefits (Figure 3). If the CDN holds the certificates, it can negotiate encryption with the clients and collect the files from your server in plaintext. This allows the CDN to cache the content efficiently and serve it faster to users.Figure 3: TLS and CDN caching comparedSimplified TLS ManagementThe CDN takes care of maintenance tasks such as certificate issuing, rotation, and auto-renewal. With the CDN managing TLS, your server’s code base can be simplified, and you no longer need to worry about potential TLS updates in the future.TLS Encryption with Gcore CDNWith the Gcore CDN we don’t just take care of your TLS encryption, but also file compression and DNS lookups. This way, you can unburden your servers from non-functional requirements, which leads to smaller, easier-to-maintain code bases, lower CPU, memory, and traffic impact, and a lower workload for the teams managing those servers.Gcore CDN offers two TLS offloading options:Free Let’s Encrypt certificates with automatic validation, an effective and efficient choice for simple security needsPaid custom certificates, ideal if your TLS setup has more complex requirementsHow to Enable HTTPS with a Free Let’s Encrypt CertificateSetting up HTTPS for your website is quick, easy, and free. First, make sure you have a Gcore CDN resource for your website. If you haven’t created one yet, you can do so in the Gcore Customer Portal by clicking Create CDN resource in the top-right of the window (Figure 4) and following the setup wizard. You’ll be asked to update your DNS records so they point to the Gcore CDN, allowing Gcore to issue the certificates later.Figure 4: Create CDN resourceNext, open the resource settings by selecting your CDN resource from the list in the center (Figure 5).Figure 5: Select the CDN resourceEnable HTTPS in the resource settings, as shown in Figure 6:Select SSL in the left navigationClick the Enable HTTPS checkboxClick Get SSL certificateFigure 6: Get an SSL certificateYour certificate will usually be issued within 30 minutes.Our Commitment to Online SecurityAt Gcore, we’re committed to making the internet secure for everyone. As part of this mission, we offer free CDN and free TLS certificates. Take advantage and protect your resources efficiently for free!Get TLS encryption on Gcore CDN free

Subscribe to our newsletter

Get the latest industry trends, exclusive insights, and Gcore updates delivered straight to your inbox.