During the deployment of websites, service portals, digital platforms, or specialized application systems, one of the most critical infrastructure configuration steps is changing DNS and updating the A record so that the domain connects accurately to the server running the system. This is a foundational step in every DNS configuration project, domain-to-server routing process, and digital healthcare platform deployment.
For enterprises, corporations, and organizations operating digital services in the healthcare sector, this action must be carried out with precision because domain stability directly impacts access to websites, patient portals, admin portals, data integration systems, and the end-user experience. Especially in the context of healthcare digital transformation, standardizing DNS infrastructure is not merely a technical task, but also an essential part of the operational strategy for digital health platforms, health information systems, and healthcare interoperability.
This article has been prepared by BSS to help our partners clearly understand the nature of DNS, A records, the relationship between domains and servers, and the coordination process when a domain is being managed by a vendor or a third party.
I. The Role of DNS in Digital Platform Deployment
For a website or digital platform to function on the Internet, the domain must point to the correct infrastructure operating the system. The component responsible for this is DNS.
DNS, short for Domain Name System, is the mechanism that converts easy-to-remember domain names into IP addresses that servers and browsers can understand. DNS can be viewed as a routing system: when a user accesses a domain name, DNS determines which IP address that domain should connect to, thereby directing the user to the correct server.
For example, if a domain is configured to point to the IP address 103.70.13.166, DNS is the component that helps the browser understand that this domain is connected to the server with that IP address.
In BSS’s digital healthcare system deployment projects, DNS plays an especially important role because a domain may serve not only as a corporate website, but also as an access point for business-critical platforms such as:
- Patient portals
- Internal portals
- Hospital integration systems
- Healthcare monitoring applications
- Digital data management platforms
- Service layers requiring high stability within healthcare technology environments
Therefore, properly changing DNS is a necessary condition to ensure service continuity and the stable operation of the system.
I.1 What is an A Record?
Within the DNS system, there are many different types of records, and the A record is one of the most basic, common, and important.
An A record is used to define that:
A domain or subdomain points to a specific IPv4 address.
In other words, the A record is where the configuration states, “Which IP address is this domain pointing to?”
For example, when BSS provides the following server IP:
103.70.13.166
then asking our partners or the DNS administrator to update the A record means configuring the relevant domain or subdomain to point to this exact IP address.
When a user enters the domain in a browser, the DNS system reads the A record to determine the destination. If the A record is configured correctly, the request will be routed to the correct server hosting the website or application.
A simple way to think about it is:
- The domain name is the name of a location on the Internet
- The IP address is the actual address of that location
- The A record is the instruction line showing which address that name corresponds to
This is why, when BSS asks a partner to update the A record, the essence of the request is to configure the domain so that the system can operate on the correct infrastructure already deployed.
I.2 What Does “Point the Domain to the Server” Mean?
During deployment discussions, BSS often uses the phrase:
“Please point the domain to the BSS server.”
From a technical perspective, this means the partner needs to update the DNS so that the domain points to the correct IP address of the server running the system.
The concept of “server” here should not be understood simply as a physical machine in an office. In practice, the server may be:
- A physical server in a data center
- A virtual private server (VPS)
- A cloud server
- Or an infrastructure component within a cloud computing environment
What matters is not the physical location of the server, but whether the domain is configured to reach the correct infrastructure operating the service. Therefore, when BSS provides a specific IP address and requests an A record update, that is the method by which the partner’s domain is connected to the correct system.
In digital health systems, health information systems, or platforms requiring multiple layers of data integration, accurately pointing the domain is a prerequisite for upper-layer components such as SSL, reverse proxy, application routing, and business logic to function properly.
I.3 Distinguishing Between Domain, DNS, and Server
In practice, these three concepts are often confused. However, for effective technical coordination, partners should clearly distinguish them.
What is a domain?
A domain name is the address users use to access the system, for example:
- example.com
- portal.example.com
What is DNS?
DNS is the system that manages the records allowing the domain to be directed to the correct destination, such as a website server, mail server, or platform service.
What is a server?
A server is where the application, website, or system is actually installed and operated.
These three components are closely related, but they do not necessarily reside in the same place or with the same provider. In many cases:
- the domain is registered with one vendor,
- DNS is managed on another platform,
- while the server is operated on BSS infrastructure or by another cloud provider.
This is why, when changing DNS, a partner does not need to “buy the domain again” or “switch domain providers,” but simply work with the entity that has DNS administration rights in order to update the record.
I.4 What Should Be Done If DNS Is Managed by a Vendor?
This is a very common situation for businesses. Many organizations do not directly hold DNS administration access, but instead assign it to:
- The domain provider
- The hosting provider
- The in-house IT operations team
- Or the vendor managing the existing infrastructure
In that context, when BSS requests a DNS change or an A record update, the partner does not necessarily need to perform the technical action directly. What needs to be done is:
- Identify the correct person or unit that holds DNS administration access
- Forward the configuration information provided by BSS
- Request that party to update the A record as required
- Notify BSS after completion so connectivity can be checked
In short, if DNS is managed by a vendor, then the vendor is the party responsible for making the change.
The key principle is:
Whoever has the authority to edit the DNS zone is the one who can change the A record.
I.5 When Does a Partner Need to Change the A Record?
Typically, BSS will request an A record update in situations such as:
- Deploying a new website
- Migrating a website to infrastructure operated by BSS
- Connecting a landing page or microsite
- Configuring a service portal
- Pointing a subdomain to an application platform
- Changing production infrastructure
- Upgrading the deployment environment during digital transformation
In all of the above scenarios, the goal is the same:
to ensure that the partner’s domain or subdomain is accurately connected to the server running the system.
See more about projects implemented by BSS:
- Binh An General Hospital
- Khang Tri Men’s Health & Fertility
I.6 What Information Is Needed to Update an A Record?
Depending on the DNS provider, the administration interface may vary. However, the basic information fields when configuring an A record usually include:
Type: A
Host / Name: the root domain or subdomain to be pointed
Value / Points to / IP address: the server IP address
TTL: DNS cache duration, which can usually remain at the default if there is no special requirement
For example, if BSS provides the IP address:
103.70.13.166
Then the configuration will include:
Type: A
Value: 103.70.13.166
The Host/Name field will depend on whether the partner needs to point the root domain or a specific subdomain.
Root Domain Configuration
If configuring the root domain, the Host field is often:
For example:
tencongty.vn → 103.70.13.166
Subdomain Configuration
If configuring a subdomain, the Host field will be the corresponding subdomain name.
For example:
- www.tencongty.vn → Host is www
- portal. tencongty.vn → Host is a portal
- app.vn → Host is an app
Determining this correctly is very important because pointing the wrong target may cause the system to fail to operate as intended.
II. Does the System Update Immediately After DNS Is Changed?
One important point to note is that DNS does not always update immediately after a change is made.
After the A record is updated, the information needs time to propagate across the global DNS system. This process is commonly referred to as DNS propagation.
The effective time may be:
- Just a few minutes
- Several hours
- Or, in some cases, up to 24–48 hours
This timeframe depends on several factors such as:
- The TTL of the record
- DNS provider cache
- Browser cache
- Operating system cache
- Network provider cache
Therefore, after changing DNS, it is normal to encounter a situation where:
- some users can already access the new system,
- while others still see the old system.
This is a normal occurrence. Once the partner confirms that the update has been completed, BSS will assist in checking the actual access status.
III. Important Notes Before Changing DNS
To ensure that the A record update is performed safely and accurately, BSS recommends that partners pay attention to the following points.
III. 1 Identify the Correct Domain or Subdomain to Point
First, it is necessary to clearly determine whether the system uses:
- the root domain,
- or a separate subdomain.
This directly affects the Host/Name field in the configuration.
III. 2 Check Existing Records
Many domains already have existing A records. In such cases, it is necessary to review them in order to:
- Update the correct record currently in use,
- Avoid unwanted duplicate records,
- Reduce the risk of incorrect resolution.
III. 3 Do Not Confuse Website DNS with Email DNS
Changing the A record usually applies to a website or application. This action does not mean changing the email configuration.
However, if changes are made incorrectly within the DNS zone, other records may accidentally be affected, such as:
- MX
- SPF
- DKIM
- TXT
Therefore, BSS recommends that the update be carried out by a qualified party or the unit directly administering DNS.
III. 4 Identify the Actual DNS Management Location
The place where the domain is registered is not always the place where DNS is actually managed. In some cases:
- The domain is registered in one place,
- but DNS is pointed to Cloudflare or another service.
Therefore, changes must be made in the correct place that holds authority over the DNS zone.
IV. Coordination Process Between the Partner and BSS
To support a faster deployment process and minimize errors, BSS proposes the following coordination process.
Step 1: BSS Provides Technical Information
BSS sends the partner the necessary information, including:
- The server IP address to point to
- The domain or subdomain to configure
- Any relevant infrastructure notes, if applicable
Step 2: The Partner Works with the Party Managing DNS
If DNS is managed by a vendor or internal IT team, the partner forwards the configuration information to the correct point of contact for execution.
Step 3: The DNS Administrator Updates the A Record
The vendor or IT team performs the configuration according to the information provided by BSS.
Step 4: The Partner Notifies BSS
After the update is completed, the partner informs BSS so the connection status can be checked.
Step 5: BSS Verifies and Supports Completion
BSS will check:
- Whether the domain points to the correct IP
- Whether the system responds correctly
- Whether the access configuration is stable
- Whether supporting layers such as SSL, reverse proxy, or web server are ready
This process helps both parties coordinate more effectively, especially in projects requiring high accuracy such as digital healthcare platforms, hospital service portals, or systems demanding high infrastructure stability.
V. Why Is Accurate DNS Configuration Especially Important in Healthcare?
For many industries, DNS is a basic infrastructure component. However, in healthcare, its importance is even greater because digital infrastructure is often tied to:
- Sensitive data
- Continuous operational processes
- Multiple access points
- Integration requirements across systems
An incorrect DNS configuration may cause:
- Access disruption
- Incorrect domain routing
- Difficulties in environment integration
- Delays in system go-live
- Or negative impact on the end-user experience
As healthcare brands across Asia continue to accelerate digital health, health system integration, healthcare interoperability, and digital infrastructure modernization, standardizing foundational steps such as DNS configuration, A record setup, and domain routing becomes a prerequisite for building a secure, flexible, and scalable technology architecture.
VI. BSS and Its Direction in Supporting Healthcare Brands Across Asia
Bespoke Soft JSC (BSS) positions itself as a strategic technology partner for healthcare brands across Asia, accompanying partners in the process of building, integrating, and operating digital solutions.
BSS’s role goes beyond software development. It also includes supporting partners across essential infrastructure layers such as:
- domain and DNS
- cloud infrastructure
- system integration
- service portals
- digital health platforms
- data management systems
- and healthcare interoperability readiness layers
Therefore, an issue that may appear basic—such as changing DNS—is actually an important part of a structured and stable digital infrastructure deployment chain. When foundational steps are executed correctly, the application layers above can operate more safely and effectively.
VII. FAQ
What does changing DNS mean?
Changing DNS is the process of updating domain records so that a domain or subdomain points to the correct service, server, or infrastructure operating the system.What is an A record and what is it used for?
An A record is a DNS record used to point a domain or subdomain to a specific IPv4 address. It is a common configuration when connecting a website or application to a server.What does “point the domain to the server” mean?
It means updating DNS so that the domain leads to the correct IP of the server running the website, service portal, or application platform.If DNS is managed by a vendor, what does the partner need to do?
The partner needs to contact the unit holding DNS administration rights and send the A record information provided by BSS so that the unit can perform the update.How long does it take for the system to take effect after updating the A record?
DNS propagation usually takes from a few minutes to several hours; in some cases, it may take up to 24–48 hours depending on TTL, cache, and the DNS provider.Does changing the A record affect domain email?
Normally, changing the A record serves the website or application. However, if the DNS zone is edited incorrectly, other records such as MX, SPF, DKIM, or TXT may be affected.What support does BSS provide after the DNS update is completed?
After the partner or vendor completes the configuration, BSS can assist in checking the domain resolution status, system connectivity, service accessibility, and related configurations.Why should healthcare enterprises pay close attention to proper DNS configuration?
In the context of healthcare digital transformation, systems increasingly depend on integration, interoperability, and stable digital infrastructure. Accurate DNS configuration is a foundational step to ensure stable access and proper system deployment architecture.
