Manage access to private DNS
Access to private DNS is governed by:
- projects — they define access within an isolated resource group;
- role model — it defines access for different users within an account and project. Read more about access within the role model in the Managing access in Servercore products.
Access within the role model
member
A user with full access to all services. Access management is unavailable for: users, service users, user groups and federations.
billing
User with access to billing management and no access to service management.
iam.admin
A user with access to user management and no access to services or billing. This user cannot manage their own account: modify permissions, manage notifications, or delete the user. The first user with the iam.admin role is created by the Account Owner.
iam.viewer
User with access to view everything that iam.admin manages.
reader
User with access to view everything that member manages in the same access scope.
vpc.private_network.admin
User with access to manage private networks, subnets, and ports, as well as private DNS.
Adding ports to a cloud server and deleting ports added to a cloud server is not available; this requires the member role.
vpc.private_network.viewer
User with access to view everything that vpc.private_network.admin manages in the same access scope.