(You must already be logged in to Gitlab or you’ll hit a 404)
Your Bytemark account joins all your services together. Every account has the following information:
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 and update your credit card details through our control panel.
You will need to contact support if you would like to:
Our team can talk you through these processes and ensure the proper security checks are carried out.
You can create and manage accounts through https://panel.bytemark.co.uk/ Here you can see:
You can ask us to give other users access to your account or to your cloud servers:
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 ‘18.104.22.168’ and Bytemark would automatically create a record of
foo.default.bob2000.uk0.bigv.io -> 22.214.171.124. Bytemark would also set up a Reverse DNS (rDNS) record of
126.96.36.199 -> 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 => 188.8.131.52 $ dig -x 184.108.40.206 => foo.default.bob2000.uk0.bigv.io