Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Hosting and infrastructure

    Understand hosting and infrastructure

    A website depends on services that can belong to different providers. Map the chain between domain name, DNS resolution, server, files, data and email. This helps diagnose an outage and plan a transfer without confusing responsibilities.

    63 concepts to explore with definitions and practical advice.

    Search the full glossary
    Code screens on a desk
    AI-generated illustration

    A reading path

    1. Name and destination

    Identify the domain owner and records connecting services. A hosting change should not be confused with transferring the domain.

    • Domain ownership

      Documented ability of an organisation to identify the registrant, renew and transfer its domain and manage DNS settings through authorised people.

    • DNS

      Distributed system publishing records associated with domain names, including addresses and mail information. DNS does not itself store the website’s pages. Distinguish the authoritative server’s response from copies held by resolvers. Cache lifetimes explain some temporary differences between visitors.

    • Registrar

      Organisation through which a domain is registered and managed. Registrar, DNS provider and hosting provider can differ; keep their responsibilities and access arrangements distinct.

    2. Execution and storage

    The server supplies resources and can execute processing. Identify files, database and media requiring backup or transfer.

    • Web hosting

      Service making website files, databases and resources available on servers connected to the Internet.

    • Server

      Software or a system handling client requests and providing responses. Server availability differs from business-operation success: a responding page may still show an application error.

    • Object storage

      Storage that keeps files as objects with metadata, often in cloud infrastructure.

    3. Versions and availability

    A cache can serve a previously received response. Availability metrics and logs help observe the service with a known period and scope.

    • Cache-Control

      HTTP header specifying storage and reuse directives. no-cache requires validation before reuse; no-store requests no storage; private restricts storage to private caches. These directives serve different needs and must match the content actually served.

    • Uptime

      The share of time a service is considered available under a defined rule. State period, check frequency and exclusions; an accessible homepage does not prove booking or contact works.

    • Server log

      Timestamped record of requests or events processed by a server, used for diagnosis, security and crawl analysis. Record format, time zone and observed layer. Proxy and application logs may describe different stages of the same request.

    Useful distinctions

    DNS / Web hosting

    DNS helps reach a name’s destination; hosting supplies website resources. Correct resolution does not guarantee that the server serves the correct page.

    Browser cache / CDN

    Browser cache concerns a copy on the device. A CDN distributes resources through intermediary infrastructure. Review update rules for each layer.

    Educational example

    Use the vocabulary to make a decision

    Two laptops beside a router, storage drive and coloured markers
    AI-generated illustration · Compare copies of a page after a correction.

    Situation

    A corrected page still shows old content for some visitors.

    Before deciding

    Compare the response without a local copy, cache rules and possible variants. Do not change DNS to solve merely cached content.

    A concrete check

    Check an HTML page, medium and related journey response before and after the fix.

    From a word to an observation

    Find where an older version persists

    A browser, intermediary and server can retain copies. Compare the same resource and its headers before concluding that a change has not been published.

    On a narrow screen, scroll the table horizontally to read all three columns.

    Illustrative observations to adapt to your project
    Observed signalWhat to checkWhat it means
    One browser displays an old pageCompare a request without the local cache.A local copy is one explanation to investigate.
    HTML is current but styling is oldExamine the CSS file URL and cache rules.Resources can have different retention periods.
    A 304 status is returnedCheck the validator and reused local version.304 allows reuse of the copy; it does not transmit a new complete page.

    Next step : Record the affected resource, version and cache policy. A versioned URL can distinguish versions of a changed file.

    Technical reference : MDN — HTTP caching. The scenarios and numerical examples above are educational, not measurements of this website.

    Examine the interpretation

    An old resource on screen does not automatically identify DNS

    Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.

    1. Resource identified
    2. Revalidation observed
    3. Version reconciled

    A page opens at the expected address, but a stylesheet remains old. The network record shows that resource was reused from a cache.

    Which mechanism should this finding lead you to inspect first?

    The HTTP cache for that resource

    Checking its URL, headers and actual stored copy helps explain why that version is displayed again.

    Domain-name resolution alone

    DNS has a different role. Observing a reused resource copy is not enough to blame DNS for the old presentation.

    A useful next step : Identify the resource and cache before changing configuration. A one-off browser refresh is not by itself a lasting correction.

    Reference to explore : MDN · HTTP caching · Consulted .

    Frequently asked questions

    Does moving files transfer email?

    Not necessarily. Email has its own services and records. Identify it separately, then verify receiving and sending after planned changes.

    Does a backup prove recoverability?

    It is a copy to examine. A tested restoration checks that required files and data are present and compatible with the recovery environment.

    Primary reference documents

    These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.

    Related topics