WebNIC
Connect WebNIC to sell eligible domains and manage their contacts, DNS and additional services through WISECP.
Accessing the Screen
Open Products → Domain Names → Domain Registrars → All Modules → WebNIC: {admin}/module/registrars?module=WebNIC.
What Is on the Screen?
| Section | Purpose | Limit |
|---|---|---|
| Module Settings | Account, DNS and pricing settings | Separate live and OTE credentials |
| Import Extensions | Select extensions and profit rate | No account-domain import tab |
Prepare the Provider Account
Request a WebNIC partner account, API user and secret; authorize this server's outgoing IP. Confirm domain and DNS permissions. Use the official REST v2 reference for account setup and current quotas. PHP cURL and intl are required. Allow HTTPS to api.webnic.cc for production and oteapi.webnic.cc for OTE. Testing requires its own account credentials.
Settings
Available Actions
Connect and Check
- In Module Settings, enter credentials and check the environment, shared registrant and DNS subscription.
- Click Test Connection. It reads the extension catalogue; success does not prove funds or permission for purchases.
- Click Save Changes and reopen the form. No separate WISECP server record is required.
Import Extensions and Prices
Open Import Extensions, select extensions and a profit rate, then click Import. Existing assignments and prices may change; new extensions start inactive. The feed includes positive registration, renewal and transfer prices and supported periods. It prefers local reseller prices. The preview can show zero because its expected price format differs; compare saved amounts with WebNIC before opening sales.
Generic DNS/privacy flags do not confirm entitlement, restore fees or premium registration support. Follow the Domain Extensions guide to verify mapping and addon prices. Account domains cannot be listed for import; use the Registrar Configuration guide for service mapping.
Manage a Domain
Open the domain under Orders → Services. Registration, incoming transfer, renewal, restore, nameservers, WHOIS contacts, transfer lock and privacy are available. Incoming transfers require an authorization code; this module cannot retrieve an outgoing code. Obtain it through WebNIC's process. Releasing the lock also removes name protection. Shared WHOIS contact updates can affect other domains; the first role wins when roles share a contact.
Child nameserver listing reads the first 100 provider hosts. An empty list may be incomplete. Changing an address replaces its IP list with one address. Renaming creates a new host, then deletes the old one; deletion removes the entire host. Check dependent domains first.
The service's DNS section supports A, AAAA, CNAME, MX, TXT and SRV. Use an active provider DNS zone and appropriate nameservers. DNS edits preserve other values of the same name and type. Changing name or type deletes the old record first; save a copy before editing. TTL is at least 60 seconds.
DNSSEC manages DS records by rewriting their complete set; deleting the last record removes the set. Coordinate DNSSEC with the DNS operator. URL forwarding affects the root domain and may replace conflicting DNS records. The displayed 301/302 choice is not sent. Email forwarding supports listing, adding and deleting named aliases; editing and catch-all aliases are unavailable.
Verify a Controlled Trial
- Use OTE credentials and keep the test sales extension inactive. Read a controlled service and compare its contacts, nameservers and dates with WebNIC.
- After an authorized test order, verify the provider result and scheduled status synchronization. An accepted request may still be pending.
- Check customer controls with the intended service options, addons and permissions before enabling sales.
Important Notes
Live registration, transfer, renewal, restore, privacy and DNS subscriptions may incur charges. Cancelling the DNS addon does not unsubscribe at WebNIC. Local service suspension or cancellation does not delete the domain or stop provider billing. Check the provider before repeating an unsuccessful request.
For access errors, check OTE/live credentials, IP permissions, DNS entitlement, account funds, currency and API quotas. A pending transfer requires provider confirmation; do not assume every failure becomes a final WISECP status.
Required Permissions
Configuration requires Domain Registrars permission. Administrator and customer operations also depend on their permissions and provider access.
Related Guides
Thanks for your feedback!
Our support team is here around the clock for anything you can't find above.