Note: This are reference values to assess the system size. In reality, more parameters define real workload and affect required resources differently. Refer to Hardware Configuration Requirements to plan the actual required capacity.
|
Server Names |
LINDNS01, LINDNS02 |
|
|
Description |
DNS Server on Linux |
|
|
Density |
60,000 DNS zones / 300,000 DNS resource records per server |
|
|
Quantity |
Minimum 2 are required. |
|
|
OS |
|
|
|
Software |
To be installed by customer:
|
|
|
CPU |
2 core (2.4 GHz or higher) |
|
|
RAM |
7 GB |
|
|
Disk |
2 x 36 GB, SCSI, RAID 1 |
|
|
Azure Type |
DS2 v2 |
|
|
NICs |
FrontNet, BackNet |
|
Important:
- Some top-level domain (TLD) zones may have specific network requirements for name servers. For example, name servers of the .DE and .FR TLD zones must be placed on the different subnets. Make sure that TLD zone requirements are satisfied before the CloudBlue Commerce name servers will have been deployed.
- We recommend that you place CloudBlue Commerce name servers on different sub-nets.
- It is a recommended DNS practice to have separate DNS servers for resolving and hosting. CloudBlue Commerce DNS Servers are not purposed for resolving internal or external hosts, they are only for hosting CloudBlue Commerce domains/zones. So, you should have your own DNS servers for resolving (Resolver DNS Servers).