Support & operations · Practice guide

Check connected services after changing domain settings

Illustrative situation

After a DNS change, the main website opens correctly but an important subdomain and email-related records were overlooked. A successful homepage check is only one part of verifying a domain-setting change. Other addresses, booking destinations or email-related services may depend on the same arrangements. Decide the affected list before making the change.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What this means for your practice

Ask the supplier to check every affected service from appropriate test locations or environments. Keep the previous settings available while investigating inconsistent results.

An example to discuss with your team

Use a test checklist containing a working homepage and a failed dependent subdomain. Confirm the change cannot be marked fully verified on the homepage result alone.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

How to review the arrangement

Ask the supplier to use a sample checklist where the homepage works but one important dependent address fails. The change should remain unresolved for that service. Record observations and any uncertainty while updates take effect. Keep the prior settings available so investigation does not rely on recollection.

Use a checklist based on the planned change

Before the supplier makes the change, agree which addresses and services need checking afterwards. Include relevant subdomains, booking destinations and email-related services identified by the technical owner. This keeps verification tied to the work performed rather than a generic instruction to 'check the website'.

Ask the supplier to explain any differences observed from different connections or locations and how they will be followed up. Record what was checked and what remains uncertain, with the prior settings available through the agreed recovery process. A working homepage should not close a change if another affected service fails. Use an illustrative checklist containing one successful and one unsuccessful result to confirm how the team would report the position. The practice needs an understandable conclusion about each service it relies on, including any temporary limitation, rather than a single successful result standing in for the whole change.

How to check the result

Count unresolved dependent-service failures after DNS changes.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.