There are many Open Source DNS server services for Linux systems. Here we’ll discuss about installing and configuring one of the most popular DNS server services among them known as “Bind9”. We’ll use another most popular Debian based Linux server operating system distributed by Canonical which is Ubuntu 16.04 LTS Server edition.
Other good DNS implementations include the native OpenBSD DNS implementation, as well as Dan Bernstein’s tinyDNS (AKA djbdns), but these are topics for future articles. (We use djbdns on OpenBSD, internally).
Successfully installing and configuring Bind9 Server service on Ubuntu 16.04 LTS server edition require several steps. For better understanding we’ll divide the total process into two main steps as ‘Basic installs’ and ‘Securing the DNS Server’ service. Each main category could be divided into several additional steps.
Basic Installing Steps:
Securing Bind9 DNS Server Service:
For this tutorial we’ll use ‘eracks.com’ as domain and local IP address for demo and real time configurations (tested) behind the NAT network. The global & dedicated Systems could be configured just by replacing with your own domain and real IP assigned from your ISP. If you need further assistance please contact our eRacks Systems’ experts. Also, you could buy securely configured “DNS Server” as your requirements from eRacks Systems’ showRoom without any hassle. For your requirement please checkout.
For configuring DNS Servers we’ll use private IP from 192.168.88.0/24 network block where the usable Host IP Range is: 192.168.88.1 – 192.168.88.254; and Subnet Mask: 255.255.255.0. Our Router/NAT-gateway IP address is already configured as 192.168.88.1.
IP Address Block: 192.168.88.0/24 Usable Host IP Range: 192.168.88.1 - 192.168.88.254 Broadcast Address: 192.168.88.255 Total Number of Hosts: 256 Number of Usable Hosts: 254 Subnet Mask: 255.255.255.0 Wildcard Mask: 0.0.0.255
Options | Primary/Master DNS Server | Secondary/Slave DNS Server | Client/Host Server |
Host Name | dnsmaster | dnsslave | hostserver |
Domain | eracks.com | eracks.com | eracks.com |
IP Address | IPv4: 192.168.88.17 IPv6: ::8817 |
IPv4: 192.168.88.250 IPv6: ::8250 |
IPv4: 192.168.88.17 IPv6: ::8221 |
FQDN | dnsmaster.eracks.com | dnsslave.eracks.com | hostserver.eracks.com |
Enough talk – Let’s see how it’s done!
Get your Own Open Source DNS Server as pre-configured as ‘plug & Play’ from eRacks Systems’ ShowRoom.
For learn how to install a fresh copy of Ubuntu 16.04 LTS Server OS on a server system visit this link.
After installing, login the server directly or using SSH tunnel with IP address with user with root privileges.
The login screen will look like this;
Then run the following command and press enter and your given password to update the system.
For avoiding “sudo” command, we’ll configure the server as ‘root’ user. To do so, type the following command and press enter.
Once the Update and Upgrade are done as root user, we need to edit the network interface for setting up the static IP address for the system with the following command;
Here On the popped-up screen find # The primary network interface and replace the beneath lines with the following;
# Static Primary Network Interface IPv4 Address # Required for IPv4 (A) Records auto eth0 iface eth0 inet static address 192.168.88.17 netmask 255.255.255.0 network 192.168.88.0 broadcast 192.168.88.255 gateway 192.168.88.1 dns-nameservers 8.8.8.8 8.8.4.4 dns-domain eracks.com # Optional Static IPv6 Address for Primary Network Interface # Required for IPv6 (AAAA) Records iface eth0 inet6 static address fe80::215:5dff:fe58:6500 netmask 65 gateway fe80::2a3b:82ff:fe74:58f6
Once it is done, press Ctl + X to exit and Press ‘Y’ then Enter button to save the changes.
Next, we need to set up the hostname for this server. Thus, Run the following command to edit the host name;
On the popped up screen replace the existing default host name “Ubuntu 16.04 LTS” with “dnsmaster” (since we’ll be setting the hostname as “dnsmaster“) then Press control + X to exit. And Press ‘Y’ then Enter button to save the changes. And then Run the following command to edit the hosts file;
Replace the existing with the following host record entries with the following;
The entries will look like this;
Once done, press control + X to exit and Press ‘Y’ then Enter button to save the changes and reboot your system with the “reboot” command.
After rebooting and login to the server we’ll see that the default host name “ubuntu” is replaced with hostname “dnsmaster”. To get assure we could check the hostname and FQDN with the following commands respectively;
Once these are done the system is ready for installing the Bind9 DNS Server Service. And we could proceed to the next steps.
Note:We’ll login as as root user from the start.
Before installing ‘Bind9’ DNS Server on this server we need to make sure all the packages are up to date. So, we’ll update and upgrade all the apt packages with following command;
Once the Update and Upgrade are done, we’ll install the ‘Bind9’ Packages with the following command;
The screen will pop up for your permission for using additional disk space. For approval, press “Y” and then Enter button for installing the packages. The installation process will take a few whiles.
When the installation is done the system is ready for configuring Caching-only name server with Bind9 DNS Server service package. For configuring Caching-only name server run the following command.
On the popped-up screen find & uncomment the forwarders & set the forwarders as follows with google public DNS IP address & or with your ISP’s DNS IP address.
The entries will look like this
Next, press control + X to exit and Press ‘Y’ then Enter button to save the changes. And restart the Bind9 DNS Service with the following command.
For testing the Caching-only name server we need to run the dig command as follows;
If everything is okay, the command will dig up the following records;
Before proceeding further, first we need to make sure the Ubuntu server is up-to-date. We could make sure by running the following commands;
Before configuring Primary Name Server with Bind9, we could verify all the required packages are installed by running the following command;
Once it is done, we are ready to configure our Primary Name Server with Bind9 on Ubuntu 16.04 LTS Server. And All configuration files be will be available under /etc/bind/ directory. To do so, we need to edit ‘named.conf.local’ file first, and make entry for our domain zone.
So, we’ll run the following command line for setting up our domain’s forward look up zone.
Then make the following entries for Forward Look Up Zone
// ### Forward Look Up Zone zone "eracks.com" { type master; file "/etc/bind/forward.eracks.com"; allow-transfer {none;}; };
Reverse, look up zone is also recorded here. So, we’ll add the reverse look up zone with the first there part of the IP address in reverse way by ending with “.in-addr.arpa”. The zone name it’ll look like “88.168.192.in-addr.arpa” this. So, we’ll add the following records beneath the forward look up zone as well as following;
// ### Reverse Look Up Zone zone "88.168.192.in-addr.arpa" { type master; file "/etc/bind/reverse.eracks.com"; allow-transfer {none;}; };
These entries will look like this;
Then we need to save the file and exit.
We’ve identified forward lookup zone via “file “/etc/bind/forward.eracks.com”;” and reverse lookup zone via “file “/etc/bind/reverse.eracks.com”;” on the “named.conf.local” file. Therefore, we need to create those two-database files for use as forward & reverse lookup zone under “/etc/bind/” directory.
For “forward.eracks.com” database, we’ll copy the existing “db.local” database file that is created as default with Binid9 installation under ‘/etc/bind/’ directory. To, do so we’ll run the following command;
Then we’ll edit the newly copied database file with the following command;
Then make the following entries for the database records;
; ########################################################################### ; ### ******************************************************************* ### ; ##### Forward Look Up Zone Data Files For eRacks.Com Domain ############### ; ########################################################################### $TTL 3600 $ORIGIN eracks.com. @ IN SOA dnsmaster.eracks.com. root.eracks.com. ( 2018110111 ; Serial 4800 ; Refresh 360 ; Retry 2419200 ; Expire 7200 ) ; Negative Cache TTL ; @ IN NS dnsmaster.eracks.com. @ IN NS dnsslave.eracks.com. @ IN AAAA ::8817 @ IN A 192.168.88.17 ; ################################ ; NameServer Records ; ########################################################################### dnsmaster.eracks.com. IN A 192.168.88.17 dnsmaster.eracks.com. IN AAAA ::8817 dnsslave.eracks.com. IN A 192.168.88.250 dnsslave.eracks.com. IN AAAA ::8250 ; ################################ ; Other Host Records ; ########################################################################### hostserver.eracks.com. IN A 192.168.88.221 hostserver.eracks.com. IN AAAA ::8221 ;
It’ll look like this;
Next for “reverse.eracks.com” database, we’ll copy the existing “db.127” database file that is created as default with Binid9 installation under ‘/etc/bind/’ directory as well. So, we’ll run the following command;
And edit using the following command
Entries for the database are follows
; ########################################################################### ; ### ******************************************************************* ### ; ##### Reverse Look Up Zone Data Files For eRacks.Com Domain ############### ; ########################################################################### $TTL 3600 @ IN SOA dnsmaster.eracks.com. root.eracks.com. ( 2018110111 ; Serial 4800 ; Refresh 360 ; Retry 2419200 ; Expire 7200 ) ; Negative Cache TTL ; @ IN NS dnsmaster.eracks.com. @ IN NS dnsslave.eracks.com. ; ################################ ; NameServer Records ; ########################################################################### 17.88.168.192.in-addr.arpa. IN PTR dnsmaster.eracks.com. 250.88.168.192.in-addr.arpa. IN PTR dnsslave.eracks.com. ; ################################ ; Other Host Records ; ########################################################################### 221.88.168.192.in-addr.arpa. IN PTR hostserver.eracks.com. ;
Once it is done, we’ll save the file and exit.
It’ll look like this;
After that, we’ll restart the bind9 DNS Server Service with the following command.
Note: We should be careful that all the records that finishes with letter (other than IP addresses), we need to add full-stop (“.”) at their end point to declare it is finished. Else, the bind9 will show an error.
For instant checkup, we need to set the resolver with nameserver as localhost IP 127.0.0.1 using following command;
And at the beginning of the name server lists we need to add the following line, then save and exit.
nameserver 127.0.0.1
For checkup we’ll use the “dig” command for specific host record like following
The command will dig up the host records from the local DNS Server as follow
If the configuration is correct then the above command will not show any error. or if there is any error, we need to look at log file and troubleshoot the error. For detail about bind9 troubleshooting on Ubuntu Server please visit Ubuntu’s official “DNS Troubleshooting Page” or contact eRacks Systems’ expertise for the help.
When, the bind9 shows no error, we need to set the post installation configuration for Bind9 DNS Server Service to run successfully on Ubuntu Server. To do so, we’ll run these following commands for give appropriate access permission to the Bind9 Server Service and Allow through Ubuntu Firewall (ufw).At first, we’ll enable the bind9 DNS Server Service at the system start up with the following command. So that the Bind9 always starts automatically after the system reboot.
Then for the access permission for Bind9 on ubuntu server, we’ll run the following commands;
We’ll also configure the Ubuntu firewall in order to allow Bind9 through Ubuntu firewall (ufw). For configuring ufw we’ll run the following commands one by one.
Then we’ll restart both servives Bind9 and the ufw with the following commands;
We could always restart and check status of the Bind9 DNS Server Service with following command.
If everything is alright, the Bind9 status report will show no error. Beside, we could always visit this MxToolbox website for more detail reports and troubleshooting by entering the domain.
Asif Raihan May 8th, 2018
Posted In: How-To, Linux, Open Source, servers
Tags: linux, Open Source, tutorial, ubuntu
Ubuntu 17.10, code named Artful Aardvark; I guess you already know that Artful means full of art or skill. And Aardvark is a medium-sized, burrowing, nocturnal mammal native to Africa. Colloquially, it is called African Ant Eater.
Nowadays Ubuntu become the world’s most popular desktop Linux operating system, and with its latest short-term support release, it’s clear Canonical want to keep a firm grip on the title.
As release with Artful Aardvark (Ubuntu 17.10) in October 19, 2017 Canonical continues Ubuntu’s proud tradition of integrating the latest and greatest open source technology into a high-quality, easy-to-use Linux distribution. Ubuntu 17.10 Artful Aardvark marks an all-new chapter in Ubuntu’s already rich history. As always, the team has been hard at work through this cycle, introducing new features and fixing bugs.
This is the first version of Ubuntu to use GNOME Shell as the default desktop. ‘The HUD, global menu, and other Unity features are no longer included’. By choosing to drop Unity most of Ubuntu’s home-grown usability efforts also fall by the wayside.
In Unity’s place comes a bespoke version of GNOME Shell that is ‘customized’ to resemble something that’s superficially close to the Unity desktop layout. The Ubuntu 17.10 desktop uses a two-panel layout: a full-height vertical dock sits on the left-hand side of the screen, while a ‘top bar’ is stripped across the top.
The top bar plays host a new type of app menu, a calendar applet/message tray, app indicators, and a unified status menu for managing network, volume, Bluetooth and user sessions.
The new Ubuntu Dock is both a task manager and an application launcher. It shows icons for open and running software windows as well as ‘pinned’ launchers for user’s favorite apps.
The dock is also global; it displays icons/applications from all workspaces regardless of which one user is actually viewing.
Both the Ubuntu Dock and the top bar are semi-transparent, which adds nice visual presence. When a window touches either element the “dynamic transparency” feature kicks in to render both dock and top bar darker, making panel label contents more legible in the foreground.
The main “desktop” area remains a usable space on which user can place icons, folders and files.
Though there’s no longer a true global app menu, but the majority of apps place a small menu in the top bar bearing the name of the app in focus. These app menus contain a solitary ‘quit’ button at the least, or a full complement of options at most.
Workspaces are a common feature found on most modern desktop operating systems including Windows 10, so it’s a good thing that Ubuntu hasn’t ditched them. User can easily move windows between workspaces by clicking on a window and moving it on over the workspace.
In Ubuntu 17.10 Applications are listed alphabetically, ordered into scrollable pages. User can launch an application by clicking on it, selecting it with keyboard arrow keys and pressing enter, or by touching it.
After years of ‘footnote’ releases that brought only minor tweaks, the ‘Artful Aardvark’ brings all-out with change, ready to usher in the new era. Under the hood, there have been updates to many core packages, including a new 4.13-based kernel, glibc 2.26, gcc 7.2, and much more in Ubuntu Desktop. Let’s have a brief list view on some of those updates.
Note: Install gnome-session and choose GNOME from the cog on the login screen if user would like to try a more upstream version of GNOME. If any user’ d like to also install more core apps, he’d install the vanilla-gnome-desktop met package.
Not only the Ubuntu 17.10 Desktop but also, there are significant changes into the Ubuntu 17.10 Server version too. For the Ubuntu Server 17.10, the OS Version for the printing server has been increased to announce Windows Server 2003 R2 SP2 ID mapping checks added to the testparm(1) tool. There are some ID mapping backends too, which are not allowed to be used for the default backend. Winbind will no longer start if an invalid backend is configured as the default backend. The others are as follows,
Qemu has been updated to the 2.10 release. Since the last version was 2.8.
Among many other changes there is one that might need follow on activity by the user/admin: Image locking is added and enabled by default. This generally makes execution much safer, but can break some old use cases that now explicitly have to opt-in to ignore/share the locks by tools and subcommands using the –force-share option or the share-rw dqev property.
Libvirt has been updated to version 3.6.
LXD was updated to version 2.18. Some of the top new features of LXD 2.18 are:
Ubuntu 17.10 includes the latest release of DPDK that has stable updates: 17.05.2. This made it possible to integrate Open vSwitch 2.8.
Open vSwitch has been updated to 2.8. Though user need to specify dpdk devices via dpdk-devargs.
The DNS server BIND9 was updated to include the new Key Signing Key (KSK) that was published on July 11, 2017. Starting on October 11, 2017, that key will sign the root zone key, which in turn is used to sign the actual root zones.
The cloud-init version was updated to 17.1. Notable new features for cloud-init are as follows,
The Curtin version is updated to ‘0.1.0~bzr519-0ubuntu1’. New features are:
Samba is updated to version 4.6.7. Important changes in the 4.6.x series are:
There are many other changes too. We recommend that all users read the release notes, which document caveats, workarounds for known issues, as well as more in-depth Release Notes.
Users of Ubuntu 17.04 will be offered an automatic upgrade to 17.10. As always, upgrades to the latest version of Ubuntu are entirely free of charge.
Remember, here at eRacks, we offer pre-installed Ubuntu 17.10 Artful Aardvark with our new systems either directly from the OS dropdown, or by custom quote.
Asif Raihan October 25th, 2017
Posted In: Debian, Linux, Open Source, servers, ubuntu
Tags: linux, New products, Open Source, OS, ubuntu
8TB WD Red and RedPro drives are now available in the dropdowns on all eRacks NAS Systems, and are available on select other eRacks systems, and of course all eRacks systems by custom quote –
If you don’t see it on the system you want, just ask & we’ll quote you!
j
joe December 3rd, 2016
Posted In: Backups, NAS24, NAS36, NAS50, NAS72, servers
This is what we’ve been saying for years now – that the best path to the cloud is to:
- Own your core / foundation infrastructure and hardware, at least one server worth, and
- Architect it properly with DRY DevOps best-practices and repeatability, to scale into the cloud as needed to meet spot demand
Here’s the reference:
The Hybrid Cloud Helps Midsize Companies CompeteThis e-book is based on insights and recommendations by the Ventana Research, benchmark research report, “Business Technology Insights: Six Key Trends in Optimizing IT for Competitive Advantage.”
Source: The Hybrid Cloud Helps Midsize Companies Compete: Networkworld White Paper
joe December 23rd, 2015
Posted In: How-To, servers, Uncategorized
Tags: Best-Practices, Cloud, DevOps, Hybrid Cloud
Many of you may know this already, but:
This may seem like an obvious thing to say, but it still needs to be said.
Why?
About 4-5 times a week, we get emails like the one at the end of this page –
Offering “Clean pull” components for low prices in large lots – At best, these would be considered “Refurb” components, but are really just plain used. They have a much shorter (or no) warranty period than new components – they’re also often factory seconds or grey market parts, sold sideways to dodgy suppliers so that they can build systems cheaper.
We do not use these suppliers.
So again, we always use 100% new and factory-fresh components in our new-system builds – (on occasion we sell our B-Stock systems, which are clearly marked as such, and what they are – reconditioned, etc).
Some of the additional ways it is possible to cut corners on building and assembling IT equipment, in addition to used or refurbished parts, is to use factory lot-ends, factory seconds, factory defects with a “Workaroundable” defect – this is how Dell got their start – they would buy large lots of, say, NIC cards (This was before motherboards came with them onboard!), with a known defect, and write (and pre-install) the Windows driver for it – almost always unbeknownst to the end-user, or disclaimed in fine print in the EULA that the customer is forced to accept.
In this market, with plenty of storage servers, with large numbers of 3.5″ hard disk drives, this is especially tempting for some box-builders to use components such as these – again, we do not do this, and *always* purchase new parts only, from reputable, nationally-known suppliers of components and computer parts for our servers, especially such as hard disks, etc.
We consistently see product out there in the marketplace which is built with these dodgy components, and have many times been asked by our new customers to help them bring these products up to spec with new parts, and re-test and burn-in to ensure reliability and a fighting chance at a full product lifetime.
Best,
Joe
Joseph Wolff
Founder and CTO
eRacks Open Source Systems
Here is the example email:
Clean Pull HDD offer ( Lot# ST4815) 90 days warranty Payment Bank wire only EXW- CA USA Seagate ST3120025ACE 120GB IDE 3.5" Qty 820 pcs take all deal @ 5.00 each Seagate ST3120026AS 120GB 7200RPM SATA 3.5" Qty 1700 pcs MOQ 500 pcs + @ $ 9.00 each Seagate ST3320310CS 320GB SATA 3.5" Qty 2400 pcs MOQ 1000 pcs + @ $ 13.50 each Seagate ST3320311CS 320GB SATA 3.5" Qty 1400 pcs MOQ 1000 pcs + @ $ 13.50 each WD WD2500AAVS 250GB SATA 3.5" Qty 4000 pcs MOQ 1000 pcs + @ $ 12.00 each WD WD3200AAJS 320GB SATA 3.5" Qty 4500 pcs MOQ 1000 pcs + @ $ 14.00 each WD WD2500AAVS 250GB SATA 3.5" Qty 4700 pcs MOQ 1000 pcs + @ $ 12.00 each Axxxxx Global XXX Enterprises,INC909-360-9993email: axxxx@xxxenterprises.net email: xxxenterprisesusa@gmail.com Walnut, CA 91789 USA www.enterprises.net Call/Email to us for large qty discount . AGS WTS /WTB : We carry a wide range of products. Please contact us for your other requirements........ Hard drive ( Pull/refurb/New) , CPU ( Pull/New), Laptop/Tablets ( Refurbished/New) Memory, Monitors,Keyborad , Mice ,Networking Products ,Printer, ETC
joe November 15th, 2015
Posted In: Backups, New products, servers, Storage
Tags: Archive Drives, HDD, New products
eRacks/NAS50 Half Petabytes of Data Storage Server / Cloud Storage
We were extremely excited to announce the forthcoming release of 500 Terabyte (half Petabyte) storage space upgrade on our flagship product eRacks/NAS50 cloud data storage servers last week. The new model, to be released shortly, will incorporate 50 HGST 10 Terabyte HelioSeal™ hard drives. While the new model is not released yet, we are accepting pre-orders from customers. The current capacity, now available, of the eRacks/NAS50 is 400Terabytes in total, with currently-available 8Terabyte drives.
The new unit is rackmount and holds 50 removable drive bays. The 9U unit is suitable for any cloud storage application as well as NAS/Local LAN. eRacks/NAS50™ is also a great solution for media libraries and other applications which require massive amounts of data storage capacity, you just have to make you are also backed up by the best data management services. Visit https://blog.couchbase.com/fuzzy-matching/ and get more information!
Our new servers are truly a remarkable Petascale solution. The HGST 10 Terabyte HelioSeal™ drives that come with eRacks/NAS50 use two technologies that greatly add to the value that this server carries with it, including other server services from sites as https://www.servermania.com/kb/articles/what-are-the-requirements-for-ubuntu-server/ for ubuntu projects.
The first is referred to as the HelioSeal™ technology. The HGST hard drives using this technology replace the air inside of the drive with helium. This would make the drive much lighter as well as allowing the disks to be much thinner. Due to the helium inside, the thinness of disks will not cause any disruptive turbulence effects. This will allow us to have more disks inside each drive which in turn means more data space. Additionally, helium drives have much lower power consumption, as much as 27%, making our NAS50 models truly a green product.
The new drives in the eRacks/NAS50 servers also make use of a technology called SMR. That is short for Shingled Magnetic Recording. This technology by itself adds another 25 to 100 percent storage capacity to HGST hard drives.
We are proud of our new eRacks/NAS50 and are ready to take pre-orders. We are prepared to customize the unit per your instructions with all Open-Source software necessary so your order will reach you completely pre-installed.
Please contact us for pre-orders or any questions you may have.
eRacks Open Source Systems
Phone: (714) 758-5423
Fax: (631) 392-9842
http://www.eRacks.com
eMail: info@eracks.com
Ron September 12th, 2015
Posted In: NAS50, New products, News, Open Source, servers, Upgrades
Tags: 500TB-class, 8TB, Archive Drives, Cloud Computing, Cloud Storage Server, HDD, HelioSeal. HGST, Hybrid Cloud, Internet, linux, NAS50, Open Source, Private Cloud, Rackmount, seagate, SMR, Storage Server
We can’t help it with our innovations. Our NAS36 servers offered almost 200 Terabytes of data space already. That is considered quite high for a mid-range data storage server. But we just decided to jump even higher and exchange the standard 6-terabyte disks into 8-terabyte ones. That mean our NAS36 model storage servers are now able to hold 288 terabytes of data in total.
The new NAS36 model with higher data capacity brings even more value to our customers not just because of the storage space it provides but also for its price. Yes, we have decided to slash the prices down below $25,000. That is going to bring considerable saving to our customers. [UPDATE Sep 2015: current price for maxed-out 288TB config with Seagate Archive 8TB drives is just under $22,000]
We are proud to announce this latest upgrade as we continue to provide petascale data storage servers at affordable prices.
We remain dedicated to open-source systems. We also remain committed to delivering pre-installed, pre-configured systems to our customers.
The NAS36 servers are rack-mount servers. We designed the 4U unit specially to hold large number of drives in a very limited space. That leaves ample amount of space for other necessary accessories inside your data center rack.
The 36 drives in the unit are all Seagate Archive Drives, mounted on a single backplane and controlled by a RAID controller. The unit holds 24 drives in front and 12 in the back making the unit case quite compact.
eRacks Systems is a leading provider of high-capacity, petascale data storage server solutions to companies and enterprises requiring massive amounts of storage data.
Our servers are suitable for application and web security on the cloud as well as Near-Line Storage. They are also configurable for NAS (Network Attached Storage) applications.
For a great storage solution at a considerable low price, contact us. We are available through email, phone and our website.
Ron August 19th, 2015
Posted In: NAS36, New products, Open Source, servers, Upgrades
Tags: 288TB-class, 8TB, Archive Drives, Cloud Computing, Cloud Storage Server, HDD, Hybrid Cloud, Internet, linux, NAS36, Open Source, Private Cloud, Rackmount, seagate, Storage Server