What Is Root? Accounts, Android and DNS
Author: Domeny.ForSale editorial team Published
In brief: Root usually means the account with the highest privileges on Linux and related systems. On Android, “rooting” means gaining administrative access that the manufacturer normally does not provide to users. The word also refers to the root, or top level, of a directory structure or the DNS name hierarchy — so its meaning depends on the context.
Root on Linux: the account with the highest privileges
Root is a special administrator account whose user identifier, or UID, is 0. It can manage accounts, install system software, change settings, and read or modify files that ordinary users cannot access. Its actions may still be subject to additional system security measures or restrictions imposed by its environment, such as a container.
For everyday work, it is better to use an ordinary account and elevate privileges only when a specific task requires it. This limits the consequences of mistakes: an incorrect command run as root can damage the entire system, not just one person’s files.
Instructions for Linux often mention sudo. This tool allows an authorized user to run a command as another user, root by default. Simply having an account on the system does not grant permission to use sudo — that depends on the permissions configuration.
For example, on Ubuntu, the command sudo apt update refreshes information about available packages using administrative privileges. Creating a document in your own directory, however, should not require sudo. If a tutorial tells you to run a script downloaded from the internet as root, first check where it comes from and what it does: the script will gain extensive access to the system.
Root on Android: benefits and implications
Android uses the Linux kernel, but applications usually run in isolated environments with limited privileges. Rooting is the process of gaining the ability to perform actions with root privileges. Among other things, it may allow advanced system modifications, access to protected files, or the use of tools that require elevated privileges.
Rooting is not the same as unlocking the bootloader. The bootloader is the program that starts the operating system. Unlocking it may allow you to install modified system images, but does not in itself give you root access. Developer mode and USB debugging do not automatically grant these privileges either.
Before rooting, consider several possible consequences:
- Data loss: unlocking the bootloader often resets the phone to its factory settings.
- Problems with apps: banking, payment, or corporate apps may refuse to run on a modified device.
- More complicated updates: installing updates may require extra steps or remove modifications.
- Greater security risks: a malicious app that you grant root privileges can cause much more damage.
There is no single safe rooting procedure that works for every phone. What is possible depends on the model, device variant, and software version. Check the manufacturer’s official documentation for its unlocking rules and the implications for support; warranty coverage and statutory consumer rights are separate matters.
If you only want to change your phone’s appearance or reduce notifications, system settings and ordinary apps are usually enough. Rooting only makes sense when you can identify a feature you genuinely need and cannot obtain through a simpler method.
The root directory, /root, and document root
In a file structure, root means the root directory, the starting point for all paths. On Linux, it is written as /. For example, the path /home/anna/photo.jpg runs from the root directory through home and anna to a specific file.
Do not confuse / with /root. The first is the root of the entire file structure, while the second is usually the root user’s home directory, intended for that user’s files and settings. The account name and directory name are related, but they do not mean the same thing.
In web hosting, you will also encounter the term document root — the directory from which a web server serves a particular website’s files. It may be named public_html, www, or something else specified in the configuration. Access to this directory does not imply administrative access to the server.
If website installation instructions say “upload the file to the website root,” they usually mean the document root, not the system’s /. You can find the correct location in your hosting control panel, under the settings for the particular domain.
Root in DNS: the start of the domain hierarchy
DNS is a system that, among other things, lets you find the IP address associated with a domain name. Its hierarchy starts at the root, or root zone, written as a dot .. Below it are top-level domains such as .pl and .com.
Root servers point to the servers responsible for the relevant top-level domains. They do not store the addresses of every website or serve website content. Name resolution also uses caching, so not every query requires contact with a root server.
How can you tell which meaning of root is intended?
The easiest way is to look at the action described in the instructions. “Log in as root” refers to the administrator account; “root your phone” refers to modifying Android; “go to the root directory” refers to the file structure; and “root servers” refers to DNS infrastructure.
Before running a command that requires root privileges, establish exactly what it will change and how to undo that change. If the problem only concerns website files, check the site’s directory on your hosting service first — administrative privileges for the entire server may be completely unnecessary.
See also: What Is CDN?
Read also
