NiceNIC, operating since 2006, provides registrar services through NICENIC INTERNATIONAL GROUP CO., LIMITED, its Hong Kong-incorporated ICANN-accredited entity (IANA Registrar ID 3765). It offers more than 2,500 domain extensions, with account-funding options including USDT and USDC. You can verify the registrar entity and published policies in the NiceNIC Trust Center. Beget is also an ICANN-accredited registrar (IANA ID 3806) and lists more than 500 domain zones. NiceNIC is an additional registration option for customers who need a particular extension, payment route or domain workflow—not a claim that Beget lacks registrar services.
By NiceNIC Content Team · Beget documentation, registrar records, DNS instructions and published pricing checked November 18, 2026.
Temporary Beget service notice — checked November 18, 2026: Beget's recovery FAQ, marked current as of November 17, says new domain registrations are temporarily suspended. It also says automatic domain renewal is temporarily unavailable and renewals must be requested manually. This is a dated service notice, not a permanent limitation on Beget's registrar offering. Check Beget's current recovery FAQ before making a time-sensitive decision; the status may change.
1. Understand the Three Services Before You Change Anything
A domain registrar, an authoritative DNS provider and a hosting company perform different jobs. You can use different providers for each layer.
Changing the registrar does not move your website files, database, PHP application or VPS. Changing nameservers does not transfer domain ownership. Changing an A record does not move your hosting subscription. These are separate operations, but each must be configured correctly.
Beget itself is an accredited registrar under IANA Registrar ID 3806, and its website lists more than 500 domain zones. NiceNIC's catalog lists 2,500+ extensions. Catalog totals are not a guarantee that every TLD is available to every registrant: check the exact extension, current availability, registry eligibility and registration term before ordering. You can compare options through NiceNIC Domain Search and NiceNIC Domain Prices.
For a domain already registered at NiceNIC, Beget supports adding an externally registered domain to its hosting account. Its instructions are available in Beget's guide to connecting a domain registered with another registrar (Russian) and its Domains and Subdomains manual (Russian).
2. Before You Connect the Domain
Prepare these details first:
- Confirm the exact domain and TLD. Check availability, registration term, price and any registry-specific eligibility or local-contact requirement. Some extensions may offer an approved local-contact or Trustee service, but it is not available or suitable for every TLD. A domain can appear available in a search but still require registrant information or documents.
- Check your Beget account and hosting status. Confirm that the control panel can add or link an external domain and that the target hosting service or VPS is available. If Beget still marks your account as being restored, follow its current recovery instructions before changing live DNS.
- Find the correct Beget website directory or server IP. For shared hosting, identify the site directory to which the domain should be linked. For a VPS, obtain the public IP address and confirm that the web server is configured to accept the new hostname.
- Record the existing DNS zone. Save A, AAAA, CNAME, MX, TXT, SRV and verification records that are in use. Do not assume an automatic import will capture every record.
-
Check DNSSEC. If the domain currently has a DS record at the parent registry, confirm how the new DNS provider will handle DNSSEC. A stale DS record that no longer matches the authoritative DNS keys can cause validating resolvers to return
SERVFAIL. Coordinate the DS change before switching providers; do not copy or remove DS values blindly. Follow NiceNIC's DNSSEC Setup and Troubleshooting Guide where applicable. - Plan for email and SSL. Identify whether email is hosted at Beget or elsewhere, and check which certificate type you need. Beget's standard Let's Encrypt and wildcard certificate flows have different DNS requirements.
3. Three Ways to Connect a NiceNIC Domain to Beget
Choose one DNS architecture and manage the live records at the provider whose nameservers are authoritative for the domain. Records entered in the NiceNIC DNS panel do not control live DNS if the domain is delegated to Beget or Cloudflare.
Method A: Use Beget's Nameservers
This is usually the simplest arrangement for Beget shared hosting when you want Beget to manage the DNS zone.
Beget’s published nameserver set is:
ns1.beget.com
ns2.beget.com
ns1.beget.pro
ns2.beget.pro
Follow these steps:
Step 1 — Add the domain to Beget first.
Sign in to your Beget control panel. Open the domain section, add the already-registered domain as an external domain, and link it to the correct website or directory. Do not start a registrar transfer if your goal is only to connect the domain to hosting.
Step 2 — Record existing DNS and check DNSSEC.
Before changing nameservers, preserve the current records, especially MX, SPF, DKIM, DMARC and service-verification records. If the old DNS zone is DNSSEC-signed, coordinate the DS transition with the registrar and the new DNS provider. A nameserver change alone does not guarantee a valid DNSSEC chain.
Step 3 — Change nameservers at NiceNIC.
Open the domain in your NiceNIC account and replace the current nameserver set with all four Beget nameservers shown above. Use the exact list assigned or confirmed by Beget for your account. See NiceNIC's Nameserver Update Guide.
Step 4 — Check the DNS zone at Beget.
Once Beget is authoritative, manage the domain’s A, MX, TXT and CNAME records in the Beget DNS section. If you use Beget mail, use the exact mail records shown in your Beget account. If you use Google Workspace, Microsoft 365, Zoho or another mail provider, copy that provider’s required records into the Beget zone.
Step 5 — Issue and test SSL.
Beget's current recovery FAQ says that for its standard Let's Encrypt certificate, the domain and www should point by A records to the IP address of the hosting account. The same FAQ states that Beget's own Let's Encrypt wildcard certificate is validated through DNS and requires the domain to use Beget nameservers. Confirm the current procedure in Beget's Let's Encrypt guide and its SSL troubleshooting instructions.
Method B: Keep NiceNIC DNS and Point A Records to Beget
Use this setup when you manage a Beget VPS, want to keep DNS at NiceNIC, or need to split website, email and other subdomains across different providers.
Step 1 — Add and link the domain in Beget.
Add the external domain to your Beget account and link it to the intended website directory. For a VPS, configure the web server’s virtual host or site configuration to respond to the domain.
Step 2 — Obtain the correct server IP.
Copy the public IPv4 address assigned to your Beget hosting account or VPS. Do not use an example IP from a tutorial.
Step 3 — Create the website records in NiceNIC DNS.
Keep the domain on the applicable NiceNIC nameservers. In the NiceNIC DNS panel, create the records Beget requires. A typical IPv4 setup is:
@ (root domain)
www
Only add an AAAA record if Beget has supplied and configured an IPv6 address for your hosting service. An old or incorrect AAAA record can send some visitors to the wrong server even when the A record is correct.
Use NiceNIC's DNS Records Guide to manage the zone. Enter only the host portion in the subdomain field, and copy the exact values required by Beget.
Step 4 — Add email records separately.
If you use Beget mail, copy the MX and any required SPF, DKIM and DMARC records from your Beget account. If your email is hosted elsewhere, retain that provider’s MX and authentication records. Do not replace existing mail records with guessed values.
Step 5 — Issue SSL and verify the site.
Beget’s current standard Let’s Encrypt instructions require the domain and www to resolve by A record to the hosting IP. Beget’s own wildcard certificate requires Beget nameservers for DNS validation. If you keep NiceNIC DNS and need a wildcard certificate, confirm an alternative supported certificate-validation method with Beget rather than assuming the panel can issue its wildcard certificate through external DNS.
Method C: Use Cloudflare Free DNS and CDN with Beget as the Origin
This arrangement is useful when you want Cloudflare’s eligible CDN and proxy features in front of a website hosted on Beget.
- Add the domain to your Cloudflare account and create the DNS zone.
- Copy the nameservers assigned to that specific Cloudflare zone.
- At NiceNIC, change the domain's nameservers to the Cloudflare pair.
-
In Cloudflare DNS, point the root domain and
wwwto the Beget server IP using the record types required by your setup. - Enable proxying only for eligible web records. Keep mail-related hostnames and records such as MX and TXT configured appropriately; mail hostnames should normally be DNS-only.
- Choose a Cloudflare SSL/TLS mode that matches the certificate installed on the Beget origin. Use Full (strict) only when the origin presents a valid certificate for the hostname.
Cloudflare’s edge certificate and the certificate installed on your Beget origin serve different parts of the connection. Do not assume that enabling Cloudflare Universal SSL automatically installs a valid certificate on Beget.
Also note that Beget's own wildcard Let's Encrypt flow requires Beget nameservers. If Cloudflare is authoritative, use a certificate method supported by your Cloudflare/origin configuration or ask Beget which alternative it supports. See NiceNIC's Cloudflare DNS Setup Guide.
4. Update Nameservers Through the NiceNIC Domain API
If you manage multiple domains or automate customer onboarding, NiceNIC Domain API can update nameserver delegation. API access is available to active Market and Reseller accounts; API access itself is free, while live domain operations are charged according to the account’s applicable pricing.
For the four Beget nameservers, the documented change_dns operation can be called as follows:
curl “https://api.nicenic.net/v2/?category=domain&action=change_dns&domain=example.com&dns1=ns1.beget.com&dns2=ns2.beget.com&dns3=ns1.beget.pro&dns4=ns2.beget.pro”
-H “Authorization: YOUR_USERNAME:YOUR_API_SECRET”
-H “Content-Type: application/json”
Replace example.com, YOUR_USERNAME and YOUR_API_SECRET with your own values. Keep the API secret on your server; do not expose it in browser-side JavaScript or public repositories.
Important: Treat the nameserver request as the complete intended nameserver set. Include every nameserver that should remain; do not submit only two values if you intend to keep four. Check the current delegation before updating it, and verify the result after the request. See NiceNIC's Update Nameservers API Documentation and Domain API Quick Start.
5. Verify DNS, Website, Email and SSL
After changing nameservers or records, check the public DNS answers and test the actual services. DNS cache expiry and registry processing vary; do not promise a fixed propagation time.
Example commands:
dig NS example.com +short
dig A example.com +short
dig A www.example.com +short
dig MX example.com +short
Use the results to confirm that the domain is delegated to the intended provider and that website and mail records point to the correct destinations.
www does not
www A/CNAME record
www record at the authoritative DNS provider
www does not resolve to the Beget hosting IP, or validation is still pending
SERVFAIL
Beget's recovery FAQ also explains how to resolve a domain that is not linked to a website directory and how to check SSL issuance. See Beget's current recovery FAQ. If the account still displays a recovery status, follow Beget's instructions before repeatedly changing DNS settings.
6. Register and Fund Your Domain at NiceNIC
NiceNIC offers more than 2,500 domain extensions, including generic TLDs and country-code domains. Availability, registration terms and registrant eligibility vary by extension. Check the exact domain before funding your account, particularly when choosing a restricted ccTLD or an extension that requires supporting information.
Start with NiceNIC Domain Search or Bulk Domain Search. Compare registration, renewal and transfer prices on the NiceNIC Domain Price List.
Cryptocurrency and Other Funding Options
NiceNIC cryptocurrency payments fund your account balance. Once the payment is confirmed and the balance is credited, you can use the available funds for eligible registrations, renewals, transfers and other services. Funding the account and placing a domain order are separate steps.
Always use the exact asset, network, destination address and amount shown in your current NiceNIC payment instructions. Do not reuse an old wallet address. Online crypto payments are credited after provider confirmation; confirmation time depends on the selected route and network. See NiceNIC Payment Options and Can You Register a Domain with Crypto?.
.COM Price Snapshot
The following NiceNIC prices were checked on November 17, 2026 for eligible standard, non-premium .COM registrations. Promotional first-year rates run through December 31, 2026 (UTC) and include applicable ICANN fees.
Reseller credit is usable account balance, not an additional annual membership fee. Future renewals are charged at the price applicable when the renewal is processed. Eligible standard .COM registrations and renewals include Free Lifetime WHOIS Privacy at no additional privacy-service fee, subject to the TLD's rules. Privacy does not remove the requirement to provide accurate registrant information. Check the current .COM pricing page before ordering.
7. Bulk Registration, API and Hosting-Reseller Workflows
If you manage several Beget-hosted websites, campaign landing pages or client domains, you can separate the registrar workflow from the hosting workflow:
- Bulk domain checks: Use NiceNIC Bulk Domain Search to check multiple names before registration.
- Domain API: Active Market and Reseller accounts can use the NiceNIC Domain API without a separate API access fee. Registration, renewal and transfer orders still incur the applicable domain charges.
- Sandbox testing: Validate authentication, request formatting and response handling in the non-billable API Sandbox before using production credentials.
- WHMCS: Hosting providers that sell domains through their billing portal can review the NiceNIC WHMCS Registrar Module, which publishes compatibility guidance for WHMCS 9.0.
- AI-assisted checks: Compatible ChatGPT or Claude clients can use supported account-authorized tools through the NiceNIC Remote MCP Server to check domain availability, account pricing and portfolio information. MCP is optional; it does not replace the Beget hosting control panel or DNS configuration steps above.
- Reseller pricing: If your monthly registration or renewal volume justifies a different price tier, review the NiceNIC Reseller Program. API access and reseller pricing are separate.
A practical rollout is to register one test domain, connect it to a non-critical Beget site, verify DNS, SSL and email, and then repeat the process for the rest of the portfolio. Do not automate a bulk nameserver change until you have confirmed the complete intended nameserver list for every domain. NiceNIC's Domain Abuse Transparency Center provides separate operational information for businesses reviewing registrar governance.
8. Frequently Asked Questions
Can I register a domain at NiceNIC and keep my existing Beget hosting?
Yes. Register an eligible domain at NiceNIC, add it to your Beget hosting account, link it to the correct website or server, and configure DNS. You do not need to transfer your hosting subscription or move your website files and database solely because the registrar is different.
Is Beget also an ICANN-accredited registrar?
Yes. IANA lists Beget LLC under Registrar ID 3806. NiceNIC is listed under IANA Registrar ID 3765. This article presents NiceNIC as an additional registrar option for customers comparing extension availability, pricing, payment routes or domain-management workflows—not as a replacement required for Beget hosting.
Which Beget nameservers should I use?
Beget’s published nameservers are ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro. Confirm the current list in Beget’s instructions or your control panel before changing a live domain.
Should I use Beget nameservers or keep NiceNIC DNS?
Beget nameservers are usually simpler for shared hosting when you want Beget to manage the DNS zone and Beget email. Keeping NiceNIC DNS can suit a VPS or a setup where you manage website, email and other services separately. In either case, make DNS changes at the provider whose nameservers are authoritative.
Can I use Beget's wildcard Let's Encrypt certificate with NiceNIC DNS or Cloudflare DNS?
Beget’s current FAQ says its own wildcard Let’s Encrypt certificate uses DNS validation and requires Beget nameservers. If you keep NiceNIC or Cloudflare nameservers, do not assume Beget’s panel can issue that wildcard certificate through the same process. Confirm an alternative certificate method with Beget.
Is Beget currently accepting new domain registrations?
Beget's recovery FAQ marked current as of November 17, 2026 says new domain registrations are temporarily suspended. This is a dated, temporary service status, not a permanent limitation. Check Beget's latest FAQ before relying on it; if the notice has changed, follow the updated instructions instead.
Do I need a Reseller account to use the NiceNIC API?
No. NiceNIC Domain API is available to active Market and Reseller accounts. API access is free; account level determines applicable domain pricing, and live registration, renewal or transfer orders are charged separately.
Connect Your Domain Without Moving Your Hosting
You can keep the Beget hosting environment your team already uses while registering an eligible domain through NiceNIC. The important steps are to add the domain to Beget, choose the right authoritative DNS provider, preserve email and DNSSEC settings, and verify the website and SSL certificate after the change.
Start by checking NiceNIC Domain Search, comparing registration and renewal prices, and reviewing NiceNIC Payment Options. For multiple domains or client projects, explore the Domain API and Reseller Program.
If you are connecting a larger portfolio or need help choosing between Beget NS, NiceNIC DNS and Cloudflare, contact the NiceNIC Support Team or Official NiceNIC Telegram with your target extensions and hosting setup.
Primary Sources
- IANA Registrar IDs — Official registrar records for NiceNIC (3765) and Beget LLC (3806).
- Beget — Domain Management Manual — Adding an externally registered domain and linking it to a website (Russian).
- Beget — Connect a Domain Registered with Another Registrar — External domain setup (Russian).
- Beget — Nameserver Change Instructions — Beget's four authoritative nameservers (Russian).
- Beget — Current Recovery FAQ — Current service notices, domain registration status, nameserver restrictions and SSL guidance (Russian).
- Beget — Free Let's Encrypt SSL — Standard and wildcard certificate options.
- NiceNIC Domain Search — Available extensions and registration options.
- NiceNIC Domain Prices — Registration, renewal and transfer pricing.
- NiceNIC Trust Center — Registrar legal entity, IANA identity and policy references.
- NiceNIC Nameserver Update Guide — Registrar-side nameserver changes.
- NiceNIC DNSSEC Setup and Troubleshooting — DS records and DNSSEC configuration pitfalls.
- NiceNIC Trustee Services — Extension-dependent local-contact and trustee arrangements.
- NiceNIC WHOIS Privacy Eligibility — Free privacy on eligible domains and registry-specific limits.
- NiceNIC DNS Records Guide — DNS record configuration and supported record types.
- NiceNIC Update Nameservers API — Programmatic nameserver delegation.
- NiceNIC Payment Options — Current funding methods and payment fees.
- NiceNIC Crypto Registration Guide — Supported assets, networks and payment workflow.
- NiceNIC API Sandbox — Non-billable integration testing.
- NiceNIC WHMCS Module — Hosting billing integration and published compatibility.
- NiceNIC Remote MCP Server — Supported AI-client domain queries and account tools.







