You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dotster is powered by Domain.com, which means creating a zone on Domain.com also creates a zone on Dotster (and vice versa). For example, 4orty3.net uses Dotster's DNS, however ns1.domain.com will resolve all records for 4orty3.net.
Per Domain.com's Knowledge Base you can add external domains if you have an existing account or if you purchase something (like hosting). Thus, to perform a takeover on Dotster, I recommend you get an account on Domain.com (buy something cheap and cancel) then add the zones to Domain.com (which will activate the zone on Dotster).
Since Dotster also owns 000domains.com creating a zone on Dotster will active a zone automatically on 000domains.com's DNS.
No New Accounts
You cannot get new accounts on Dotster.com, but you can register a new account by buying a domain and hosting package on Domain.com.
The text was updated successfully, but these errors were encountered:
Service
DotsterStatus
No New AccountsNameserver
Explanation
Dotster is powered by Domain.com, which means creating a zone on Domain.com also creates a zone on Dotster (and vice versa). For example,
4orty3.net
uses Dotster's DNS, howeverns1.domain.com
will resolve all records for4orty3.net
.Per Domain.com's Knowledge Base you can add external domains if you have an existing account or if you purchase something (like hosting). Thus, to perform a takeover on Dotster, I recommend you get an account on Domain.com (buy something cheap and cancel) then add the zones to Domain.com (which will activate the zone on Dotster).
Since Dotster also owns
000domains.com
creating a zone on Dotster will active a zone automatically on 000domains.com's DNS.No New Accounts
You cannot get new accounts on Dotster.com, but you can register a new account by buying a domain and hosting package on Domain.com.
The text was updated successfully, but these errors were encountered: