The Manage Web Interface (MWI) is the end-user portal where domain owners administer their own domains. If a reseller has enabled the OpenSRS managed DNS service on a domain, the domain owner can sign in to MWI and edit DNS zone records directly. This article walks through pointing the domain at the OpenSRS managed DNS nameservers and creating zone records.
How managed DNS in MWI works
To use OpenSRS managed DNS through MWI, the reseller must first enable the service on the reseller account. Once enabled, the domain owner switches the domain's nameservers to the OpenSRS managed DNS nameservers and then adds, edits, or removes individual zone records inside MWI.
Before you begin
- Confirm that your reseller has enabled OpenSRS managed DNS for the domain.
- Have your MWI sign-in credentials ready.
- Have the zone record values you intend to add (IPs, hostnames, priorities) prepared in advance.
Step 1: Sign in to MWI
- Go to manage.opensrs.net.
- Sign in with the credentials provided by your reseller.
Step 2: Point the domain at the OpenSRS managed DNS nameservers
- Click Nameservers/DNS.
- Change the nameservers to the following:
- ns1.systemdns.com
- ns2.systemdns.com
- ns3.systemdns.com
- Save the change.
Warning: Changing nameservers immediately routes all DNS traffic for the domain through the new servers. Any custom records configured on the previous nameservers will not resolve until you recreate them in the new zone. Plan this change carefully — switching nameservers can interrupt mail and website availability.
Step 3: Open the DNS zone editor
- Click Modify DNS Zone.
- The zone editor opens, displaying any existing records.
Step 4: Add a DNS record
- Choose the record type you want to create (see the reference table below).
- Enter the values for the record's fields.
- Click Save DNS Record.
- Repeat for each additional record.
DNS record type reference
| Record Type | Purpose and fields |
| A | Maps a hostname to an IPv4 address. Subdomain — third level of the domain name (e.g., www or ftp). IP Address — IPv4 address (e.g., 123.45.54.123). |
| AAAA | Maps a hostname to an IPv6 address. Subdomain — third level of the domain name. IPv6 Address — eight groups of four hexadecimal digits (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). |
| CNAME | Canonical Name. Points a subdomain to another hostname to create an alias. Subdomain — third level of the domain name. Hostname — the FQDN you want the subdomain to resolve to. |
| MX | Mail Exchange. Directs incoming mail for the domain to the correct mail server. Subdomain — third level of the domain name. Priority — preference value 0–255 (lower is preferred). Hostname — FQDN of the mail server. |
| SRV | Service record used by protocols that locate services (e.g., SIP, XMPP). Subdomain, Hostname, Priority (0–255), Weight (relative weight for equal priorities), Port (TCP or UDP port). |
| TXT | Text record. Attaches arbitrary text to a hostname — commonly used for SPF, DKIM verification, and domain ownership tokens. Subdomain — third level of the domain name. Text — up to 254 characters. |
Next steps
- Verify resolution — Use a public DNS lookup tool to confirm new records resolve as expected after propagation.
- Contact your reseller — If Modify DNS Zone is not available, ask your reseller to enable managed DNS on your account.
- Review zone hygiene — Remove records that are no longer in use to keep the zone easy to audit.
Questions? Contact OpenSRS Support.
How helpful was this article?
Thanks for your feedback!
Do you still need help? If so please submit a request here.