Use the exact host you intend to configure
Before adding a record, identify the full hostname and the service it should reach. A record for `docs.example.com` is different from one for `example.com`; entering the root name by mistake can redirect or break a different part of the domain. Check the record type and target against the instructions for the service you are connecting.
If the DNS interface asks for a host label rather than a full name, enter only the portion it expects. Some interfaces append the domain automatically, so entering the full name there may create an unintended hostname. Review the final record as displayed after saving before relying on it.
Verify the subdomain independently
After saving, check the exact subdomain record and test the service at that hostname. The root domain may continue working while a subdomain is misconfigured, so test each address people will use. If the service requires a certificate or ownership check, complete that step for the subdomain as well.
Keep a note of why the record exists and which service depends on it. That context helps future administrators distinguish an active subdomain from an abandoned entry. When removing or changing the service later, review its DNS record separately rather than assuming that deleting the root domain's records will remove it.