Your Bytemark account joins all your services together. Every account has the following information:
- Your chosen unique account name, e.g. ‘bob2000’
- A legal owner e.g. “Bobs Bidets PLC”
- A name for each server you have hosted with us
- A billing contact (who receives invoices & pays bills)
- A technical contact (in case of network or server trouble)
- A cloud account, which can have cloud servers.
We issue invoices monthly in advance, to be paid by credit card. You can contact support to pay by invoice, or annually.
You can access your past invoices, update your credit card details and make payment for outstanding invoices through the Bytemark Panel.
Account Access Controls
You can ask us to give other users access to your account or to your cloud servers:
- You may nominate a single technical contact, who can manage domains, add a payment card, and view your contact details, but cannot view your invoices, or manage cloud servers.
- You may nominate any number of cloud account administrators, who can create, manage, and delete server groups and servers, but cannot view or manage your domains or contact information.
- Each cloud account administrator’s access can be restricted to a single server, or to a group of servers.
- You can, of course, nominate your technical contact as a cloud account administrator.
Account privacy
As per our privacy statement we do not reveal any information about your account or server infrastructure except to the nominated contacts.
Please note that if you do not specify a name for each new server, your account’s DNS name will be used and that will be available as the default in the Reverse DNS record. In this instance, someone might be able to find out about the existence of a particular server and account name if they perform a Reverse DNS lookup on your website name and you have not modified your default rDNS record.
For example, “Bob” creates a new server with the name ‘foo’ in the ‘default’ group of the ‘bob2000’ account. This server could be given an IP address of ‘1.2.3.4’ and Bytemark would automatically create a record of foo.default.bob2000.uk0.bigv.io -> 1.2.3.4. Bytemark would also set up a Reverse DNS (rDNS) record of 1.2.3.4 -> foo.default.bob2000.uk0.bigv.io
If ‘mysite.com’ is hosted on foo.default.bob2000.uk0.bigv.io and Bob doesn’t change Bytemark’s default rDNS record anyone could perform the following commands to view the server and account name:
$ dig mysite.com
=> 1.2.3.4
$ dig -x 1.2.3.4
=> foo.default.bob2000.uk0.bigv.io