eRacks Systems Tech Blog

Open Source Experts Since 1999

Ubuntu 19.04, aka “Disco Dingo“, is now available on all eRacks systems.

Ubuntu 19.04 (Disco Dingo)

Canonical – The company behind Ubuntu published its regular (non-LTS) version as Ubuntu 19.04 (Disco Dingo) on April 18, 2019. The first Ubuntu 19.04 beta released on March 28. Other milestones during “Disco Dingo” development included feature freeze on February 21, 2019, UI freeze on March 14, 2019, and kernel freeze on April 1, 2019.

Up until this version, the codename of each Ubuntu release is traditionally made up of an adjective and an animal, both beginning with the same letter. But that’s only partly true this time – The word “Disco is actually both a noun and a verb rather than adjective. A disco is a type of club or party at which people dance to music, often under lights.

A “Dingo” is a type of feral dog native to Australia and known for its sand-colored coat. Dingo dogs hunt alone or in cooperative packs. Inspired by the nature of the Dingo (which often sulks off when humans are around) the word has become informal Australian slang meaning ‘cowardly’, e.g., ‘he dingoes his way out of the date’.

Ubuntu 19.04 Disco Dingo is only the second Ubuntu release to use the letter ‘D’, following Ubuntu 6.06 “Dapper Drake” (released back in the land before time, aka 2006).

Since Ubuntu 19.04 (Disco Dingo) is a non-LTS version (not a Long Term Support version), it will be supported for 9 months until January 2020. If you need Long Term Support, it is recommended you use Ubuntu 18.04 LTS instead.

This article for Ubuntu 19.04 (Disco Dingo) provides an overview of the release and documents the known issues with Ubuntu 19.04 and its flavors.

Since the release of Ubuntu 19.04, everyone is talking about its Desktop Version. We’re going to do something a little different. We’re going to start with the Ubuntu 19.04 Server version first. Let’s what’s new:

Ubuntu 19.04 (Disco Dingo) Server Updates.

Every time Canonical releases a new version, it brings many new and noticeable changes. Each new version improves the previous one and strives to provide better user experiences.

Canonical made many changes on Ubuntu 19.04 (Disco Dingo) Server – the following are notable:

QEMU

In Ubuntu 19.04, QEMU was updated to the 3.1 release.

Migrations from former versions are supported just as usual. When upgrading it is always recommended to upgrade the machine types allowing guests to fully benefit from all the improvements and fixes of the most recent version.

Qemu now has virglrenderer enabled which allows to create a virtual 3D GPU inside qemu virtual machines. That is inferior to GPU pass-through, but can be handy if the platform used lacks the capability for classic PCI pass through as well as more modern mediated devices.

For more details, see the QEMU 3.1 change log.

LIBVIRT

Among many other changes worth to mention is the ability to have GL enabled graphics as well as mediated devices to be configured while still being guarded by custom apparmor profiles generated per guest. This is required for the use of GPU based mediated devices as well as VirGL (mentioned above in the QEMU section). For bringing these changes libvirt was updated to version 5.0.

DPDK

Ubuntu includes 18.11.x the latest stable release branch of DPDK. The very latest (non-stable) version being 19.02 was not chosen for downstream projects of DPDK (like Open vSwitch) not being compatible.

DPDK dependencies were reorganized into more or less common/tested components. Due to that most DPDK installations will now have a smaller installation footprint and less potentially active code to care about.

For more details see the release notes.

SAMBA

Samba was updated to version 4.10.x, and one of the big changes here is python3 support. In Disco, samba and its dependencies are all python3 only now, with the exception of tdb. tdb still builds a python2 package, namely python-tdb, but all the others, including samba itself, are python3 only.

Open-VM-Tools

To run well integrated as VMware guest Ubuntu 19.04 comes with the latest open-vm-tools version 10.3.10. Details about the changes can be found in the upstream changelog

Raspberry Pi

Ubuntu 19.04 comes with an easy way of enabling Bluetooth support on the raspi3 Ubuntu-server preinstalled images. Install the Pi-Bluetooth package (now available in multiverse) with ‘sudo apt install pi-bluetooth’.

Please note that supported Pi devices which have Bluetooth (at the time of writing, the Raspberry Pi 3B, 3B+, and 3A+) can have either serial console or Bluetooth support enabled at any given time (not both). With the Pi-Bluetooth package installed, edit it at ‘/boot/firmware/config.txt’ and set ‘enable_uart=1’ to enable serial console, or ‘enable_uart=0’ to enable Bluetooth. The change will take effect after the next reboot.

Open vSwitch

Open vSwitch has been updated to 2.11. This updated Open vSwitch version has support for the kernel versions 4.16.x and 4.17.x. Also the following features can be found on this version.

  • “mod-table” command can now change OpenFlow table names.
  • The environment variable OVS_SYSLOG_METHOD, if set, is now used as the default syslog method.
  • The environment variable OVS_CTL_TIMEOUT, if set, is now used as the default timeout for control utilities.
  • OVN-SB schema changed: duplicated IP with same Encapsulation type is not allowed any more. Please refer to Documentation/intro/install/ovn-upgrades.rst for the instructions in case there are problems encountered when upgrading from an earlier version.
  • New support for IPSEC encrypted tunnels between hypervisors.
  • ovn-ctl: allow passing user:group ids to the OVN daemons.
  • IPAM/MACAM add the capability to dynamically assign just L2 addresses
  • IPAM/MACAM add the capability to specify a static ip address and get the L2 one and it is allocated dynamically using the following syntax: ‘ovn-nbctl lsp-set-addresses <port> “dynamic <IP>”.’

Please read the Open vSwitch release notes for more detail.

OpenStack Stein

Ubuntu 19.04 includes the latest OpenStack release, Stein, including the following components:

  • OpenStack Identity – Keystone.
  • OpenStack Imaging – Glance.
  • OpenStack Block Storage – Cinder.
  • OpenStack Compute – Nova.
  • OpenStack Networking – Neutron.
  • OpenStack Telemetry – Ceilometer, Aodh, Gnocchi, and Panko.
  • OpenStack Orchestration – Heat.
  • OpenStack Dashboard – Horizon.
  • OpenStack Object Storage – Swift.
  • OpenStack Database as a Service – Trove.
  • OpenStack DNS as a Service – Designate.
  • OpenStack Bare-metal – Ironic.
  • OpenStack Filesystem – Manila.
  • OpenStack Key Manager – Barbican.

Please refer to the OpenStack Stein release notes for full details of this release of OpenStack.

WARNING: Upgrading an OpenStack deployment is a non-trivial process and care should be taken to plan and test upgrade procedures which will be specific to each OpenStack deployment. For Upgrading successfully please make sure you read the OpenStack Charm Release Notes for how to deploy Ubuntu OpenStack using Juju. Or simply contact eRacks Systemsexperts for help.

There are many other changes on newly released Ubuntu 19.04 non-LTS Server. Please read the Ubuntu 19.04 (Disco Dingo) non-LTS Server release note for more details.

 

 

 

Ubuntu 19.04 (Disco Dingo) Desktop (And Kernel) updates.

Linux Kernel 5.0.0-8 “Shy Crocodile”

The Linux Kernel had its number bumped to 5.0.0-8 by Linus Torvalds, but not because of particularly noteworthy code changes. Usually, a significant number jump like this would echo an equally significant code or functionality change, but that isn’t the case. In an email to the Linux Kernel Mailing List, he explained:

The numbering change is not indicative of anything special. If you want to have an official reason, it’s that I ran out of fingers and toes to count on, so 4.21 became 5.0.

Torvalds went on to give a breakdown of the code changes in Linux 5.0:

This new kernel should be faster, too, as work was done to speed up the anti-Spectre and Meltdown code.

GNOME desktop 3.32

Ubuntu 19.04 ships with the latest GNOME desktop 3.32. This brings performance improvements, a host of bug fixes and some important new features. Beyond the visual changes, GNOME itself is faster and uses fewer GPU resources thanks to work done by both Canonical and the upstream GNOME team.

Of course, there’s a new wallpaper in latest GNOME desktop 3.32. But the first thing you’ll probably notice is a new icon on the desktop for your home directory. If you don’t like it, you can install GNOME Tweaks and use it to hide the home directory icon.

In keeping with modern “flat” design, the desktop’s top bar and launcher have solid-black backgrounds. The application menus have been moved back to each application’s window. They no longer appear in the toolbar. That’s a change in GNOME and not a design decision from Canonical. Some applications always kept their menus in their own application windows, which made the experience inconsistent. There were also some long-standing issues that were tough to fix. Now, that whole initiative has been canned in favor of a traditional menu placement—each applications menu is in the application’s own window.

Fractional Display Scaling (Possibly)

GNOME 3.32 includes support for fractional scaling, which is of interest to people with high DPI (Dots Per Inch) displays.

Unfortunately, in the modified version of GNOME supplied with Ubuntu, the fractional scaling settings are either hidden or not accessible to us. Eventually, a tool might allow access to these settings—or another means of accessing those settings will emerge from the user community. After all, they’re in GNOME.

Live patch for Reboot-Free Kernel Updates

Canonical introduced Live patch in Ubuntu 18.04 LTS, only to remove it again in 18.10. It’s now back, complete with this new tab in Software & Updates.

Livepatch

 

Ubuntu 19.04’s Software and Updates app has a new tab called Live-patch. This new feature is intended to allow critical kernel patches to be applied without rebooting. For people using Ubuntu at home, on machines that get powered off frequently, requiring a power cycle to install a kernel update isn’t a hardship. If your Ubuntu computer is providing an external service or is hosting a website, it becomes trickier to try to schedule in the reboots.

New Icons and Visual Tweaks

The Yaru icon set has had a refresh, and new icons have been added to cater for more third-party applications. This icon set looks more coherent and slick. There’s evidence of attention being paid to the user interface all over. Files has had a facelift, and it looks crisp and feels responsive. That’s not a surprise.

Icons

 

Even the Terminal window has been polished up. The GNOME Terminal application has a new title bar with a prominent “New Tab” button and search icon.

The System menu has a new cogwheel Settings icon that replaces the old “crossed wrench and screwdriver” icon.

Application Permission Controls

GNOME’s Settings app now lets you control various application permissions. You can even choose whether or not each application can show notifications.

Application

 

Night Light Improvements

The Night Light feature changes the hue of your computer’s display, reducing the amount of blue in the display illumination as the sun sets. You can now configure the schedule for the Night Light yourself. You can also select the color temperature—or “warmth”—of the display when Night Light is activated.

Light

 

Updated Sound Controls

The Sound controls have been revamped. You don’t get more functionality than before, but the controls are laid out more conveniently and logically.

Sound

 

Raspberry Pi Touch Support

The bulk of the driver work in the kernel has been to graphics drivers, with enhanced support for displays ranging in size and capability—from the AMD FreeSync NVIDIA RTX Turing to the Raspberry Pi Touch Display. The Debian-derived Raspbian Linux already supported the Raspberry Pi Touch Display, but now you have the choice of using native Ubuntu with your Pi Touch.

There are many other changes as well. Some of them are mentioned below:

  • Tracker is now included by default. This allows the desktop to keep track of recently used files and improves searching.
  • Right click handling is now “area” by default. This allows both two-finger right clicking and clicking in the bottom right corner of the touchpad
  • alt-tab handling now switches windows by default. Switching applications by default can be done with super-tab
  • Preview order of windows in the dock is now static and based on the order in which the windows were added
  • IWD can now be enabled for use with Network Manager. IWD is a new alternative to wpa supplicant and is in testing for consideration in the future.
  • Installing Ubuntu Desktop on vmware will now automatically install the open-vm-tools package to improve integration.
  • The Yaru theme has seen further refinement and updates and includes a new icon theme.
  • Safe Graphics Mode. A new option is added to the Grub menu which will boot with “NOMODESET” on. This may help you resolve issues on certain graphics cards and allow you to boot and install any propriatary drivers needed by your system.
  • The latest releases of Firefox (66.0) and LibreOffice (6.2.2) are available and installed by default.

 

 

Some of the Common New features and Updated Packages in both Ubuntu 19.04 (Disco Dingo) non-LTS Desktop and Server Version.

Linux kernel 🐧

Both Ubuntu 19.04 (Disco Dingo) non-LTS Desktop and Server are based on the Linux release series 5.0. It includes support for AMD Radeon RX Vega M graphics processor, complete support for the Raspberry Pi 3B and the 3B+, Qualcomm Snapdragon 845, many USB 3.2 and Type-C improvements, Intel Cannonlake graphics, significant power-savings improvements, P State driver support for Skylake X servers, POWER memory protection keys support, KVM support for AMD Secure Encrypted Virtualization, enablement of Shared Memory Communications remote and direct (SMC-R/D), Open for Business (OFB), and zcrypt on IBM Z among with many other improvements since the v4.15 kernel shipped in 18.04 LTS.

Toolchain Upgrades 🛠️

Ubuntu 19.04 comes with refreshed state-of-the-art toolchain including new upstream releases of glibc 2.29, ☕ OpenJDK 11, boost 1.67, rustc 1.31, and updated GCC 8.3, optional GCC 9, 🐍 Python 3.7.3 as default, 💎 ruby 2.5.5, php 7.2.15, 🐪 perl 5.28.1, golang 1.10.4. There are new improvements on the cross-compilers front as well with POWER and AArch64 toolchain enabled to cross-compile for ARM, S390X and RISCV64 targets.

 

There are many other changes on newly released Ubuntu 19.04 non-LTS verson. Please read the Ubuntu 19.04 (Disco Dingo) non-LTS release note for more or Disco Dingo Release Notes.

Get your system with Ubuntu 19.04 (Disco Dingo) as pre-installed from eRacks Systems’ show room with Quote request. Or download Ubuntu 19.04 (Disco Dingo) directly from below.

 

April 24th, 2019

Posted In: Linux, Open Source, Operating Systems, ubuntu

Tags: , , ,

Leave a Comment

Ubuntu 18.10, aka ‘Cosmic Cuttlefish’, is available now on all eRacks systems.

 

cosmic_cuttlefish

 

Ubuntu 18.10 ‘Cosmic Cuttlefish’ supported with 9 months of security updates, bug fixes and select app upgrades. Users of it will be able to upgrade to Ubuntu 19.04 when it’s released in April, 2019.

When the release of a new version as Ubuntu 18.10 ‘Cosmic Cuttlefish’, the first question arrives in mind, “What are updated comparing with the current Ubuntu 18.04 LTS version?”

Linux Kernel

 

The most important update in ‘Cosmic Cuttlefish’ is, it has updated Linux Kernel. Ubuntu 18.10 has Linux Kernel 4.18. This Kernel version has some improvements for AMD and Nvidia GPU, USB Type-C and Thunderbolt, and performance optimizations in CPUfreq among several other features.

 

Another important thing is having faster installation and boot with new compression algorithms. Working with new compression algorithms like LZ4 and ztsd, ‘Cosmic Cuttlefish’ is supposed to have around 10% faster boot. The installation will be slightly faster as well. Which is definitely the good news for all Ubuntu users.

 

As always Ubuntu 18.10 will have this new GNOME version. Most of the visual and under the hood changes in GNOME 3.30 will be seen in Ubuntu 18.10 as well.

 

GNOME 3.30

 

Taking cue from Fedora 28, Canonical is also working to improve battery life for laptops. Linux kernel has options to switch HDD controllers, USB controllers and other such devices to a low power state when not in use. This lowers the overall power consumption and thus improves the battery life.

Ubuntu 18.04 was supposed to have a new look with the community developed Community theme. This theme could not be completed in time for the 18.04 release. But Ubuntu 18.10 has it. The ‘Cosmic Cuttlefish’ has the Yaru Community theme installed by default, giving it a ravishing fresh look.

 

Some other changes in the Ubuntu 18.10 ‘Cosmic Cuttlefish’ are as follows:

  • Support for fingerprint scanner.
  • Startup time boost and XDG Portals support for Snap applications.
  • 32-Bit support diminishing from flavors.
  • UI and UX improvements to GNOME Software (possibility).
  • DLNA support for connecting Ubuntu with DLNA supported Smart TVs, tablets and other devices.
  • A new and improved installer (less likely to be completed before 18.10 release).
  • Ubuntu Software removes dependencies while uninstalling software.
  • Ubuntu Software will show a green verified tick for Snap applications developed by the owner of the brand. The same can be found on the recently redesigned Snap store website.

 

Ubuntu 18.10 ‘Cosmic Cuttlefish’ is a modest update compared to 18.04. The vast majority of notable improvements are tucked away out of sight, ‘under the hood’. Ubuntu 18.10 feels faster than 18.04, But you can’t “see” the changes that shape Ubuntu 18.10 ‘Cosmic Cuttlefish’, you almost certainly will feel them.

October 24th, 2018

Posted In: Linux, New products, News, Open Source, Operating Systems, ubuntu

Tags: , , , , ,

Leave a Comment

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:

  1. Install fresh Ubuntu 16.04 LTS Server OS on a server.
  2. Preparing the Ubuntu 16.04 LTS Server OS for installing Bind9 DNS Server Service.
  3. Install Bind9 DNS Server Service and configure Caching-only name server.
  4. Install and configure Primary DNS server or Master DNS server.
  5. Bind9 Post installation Configurations for successful service run on Ubuntu Server.
  6. Install and configure Secondary DNS server or Slave DNS server.

Securing Bind9 DNS Server Service:

  1. Configure SPF record for securing mail server under Bind9 DNS service.
  2. Configure DKIM record for securing mail server under Bind9 DNS service.
  3. Configure DNSSEC signing on Bind9 DNS Server Services.
  4. Configure DMARC Record for securing mail server under Bind9 DNS 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 SystemsshowRoom 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!

 

eRacks/DNS


Get your Own Open Source DNS Server as pre-configured as ‘plug & Play’ from eRacks Systems’ ShowRoom.

 

 

 

Step 1: Install fresh Ubuntu 16.04 LTS Server OS on a server.

For learn how to install a fresh copy of Ubuntu 16.04 LTS Server OS on a server system visit this link.

Step 2: Preparing the Ubuntu 16.04 LTS Server OS for installing Bind9 DNS Server Service.

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.

administrator@ubuntu:~$ sudo apt-get update

 

For avoiding “sudo” command, we’ll configure the server as ‘root’ user. To do so, type the following command and press enter.

administrator@ubuntu:~$ sudo -s

 

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;

root@ubuntu:~$ nano /etc/network/interfaces

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;

root@ubuntu:~$ nano /etc/hostname

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;

root@ubuntu:~$ nano /etc/hosts

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;

root@dnsmaster:~$ hostname
root@dnsmaster:~$ hostname -f

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.

 

Step3: Install Bind9 DNS Server Service and configure Caching-only name server.

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;

root@dnsmaster:~$ apt-get update && apt-get upgrade

 

Once the Update and Upgrade are done, we’ll install the ‘Bind9’ Packages with the following command;

root@dnsmaster:~$ apt-get install bind9

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.

root@dnsmaster:~$ nano /etc/bind/named.conf.options

 

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.

root@dnsmaster:~$ systemctl restart bind9.service

 

For testing the Caching-only name server we need to run the dig command as follows;

root@dnsmaster:~$ dig google.com

If everything is okay, the command will dig up the following records;

Step4: Install and configure Primary DNS server or Master DNS server.

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;

root@dnsmaster:~$ apt-get update && apt-get upgrade

 

Before configuring Primary Name Server with Bind9, we could verify all the required packages are installed by running the following command;

root@dnsmaster:~$ apt-get install bind9 bind9utils bind9-doc

 

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.

root@dnsmaster:~$ nano /etc/bind/named.conf.local

 

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;

root@dnsmaster:~$ cp /etc/bind/db.local /etc/bind/forward.eracks.com

Then we’ll edit the newly copied database file with the following command;

root@dnsmaster:~$ nano /etc/bind/forward.eracks.com

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;

root@dnsmaster:~$ cp /etc/bind/db.127 /etc/bind/reverse.eracks.com

And edit using the following command

root@dnsmaster:~$ nano /etc/bind/reverse.eracks.com

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.

root@dnsmaster:~$ systemctl restart bind9.service
root@dnsmaster:~$ service bind9 status

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;

root@dnsmaster:~$ nano /etc/resolv.conf

 

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

root@dnsmaster:~$ dig eracks.com

 

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.

 

Step 6: Bind9 Post installation Configurations for successful service run on Ubuntu Server.

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.

root@dnsmaster:~$ systemctl enable bind9.service

 

Then for the access permission for Bind9 on ubuntu server, we’ll run the following commands;

root@dnsmaster:~$ chmod -R 755 /etc/bind
root@dnsmaster:~$ chown -R bind:bind /etc/bind

 

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.

root@dnsmaster:~$ ufw app list
root@dnsmaster:~$ ufw allow “Bind9”
root@dnsmaster:~$ ufw reload
root@dnsmaster:~$ ufw status
root@dnsmaster:~$ ufw status verbose

 

Then we’ll restart both servives Bind9 and the ufw with the following commands;

root@dnsmaster:~$ systemctl restart bind9.service
root@dnsmaster:~$ systemctl restart service.service

 

We could always restart and check status of the Bind9 DNS Server Service with following command.

root@dnsmaster:~$ service bind9 restart
root@dnsmaster:~$ service bind9 status

 

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.

May 8th, 2018

Posted In: How-To, Linux, Open Source, servers

Tags: , , ,

Leave a Comment

    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.

Artful Aardvark

‘Artful Aardvark’ (Ubuntu 17.10)

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.

Ubuntu 17.10 Debuts with An All-New Desktop

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.

Ubuntu 17.10 Desktop

Ubuntu 17.10 Desktop

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.

Ubuntu Dock

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.

Ubuntu Dock

Ubuntu Dock

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.

Activities & Workspaces

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

Activities & Workspaces

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.

Applications Overview

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.

Applications Overview

Applications Overview

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.

  • On supported systems, Wayland is now the default display server. The older display server is still available: just choose Ubuntu on Xorg from the cog on the log in screen.
  • GDM has replaced LightDM as the default display manager. The login screen now uses virtual terminal 1 instead of virtual terminal 7.
  • Printer configuration is now done in the Settings app: Choose Devices and then Printers. The tool uses the same algorithms for identifying printers and choosing drivers as the formerly used system-config-printer, and makes full use of driverless printing to support as many printers as possible.
  • The default on screen keyboard is GNOME’s Caribou instead of Onboard.
  • Calendar now supports recurring events.
  • LibreOffice has been updated to 5.4.
  • Python 2 is no longer installed by default. Python 3 has been updated to 3.6.
  • The ‘Rhythm box’ music player now uses the alternate user interface created by Ubuntu Budgie developer David Mohamed.
  • The Ubuntu GNOME flavor has been discontinued. If a user is using Ubuntu GNOME, he will be upgraded to Ubuntu.

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,

Ubuntu 17.10 Server

Ubuntu 17.10 Server

Qemu 2.10

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 3.6

Libvirt has been updated to version 3.6.

LXD 2.18

LXD was updated to version 2.18. Some of the top new features of LXD 2.18 are:

  • Native Ceph RBD support.
  • Support for cloud instance types.
  • Pre-seeding of the “lxd init” questions through yaml.
  • New client library.
  • Improved storage handling (volume resize, auto re-mapping on attach, …).
  • A lot of small improvements to the client tool.

DPDK 17.05.2

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 2.8

Open vSwitch has been updated to 2.8. Though user need to specify dpdk devices via dpdk-devargs.

New BIND9 KSK

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.

Cloud-Init

The cloud-init version was updated to 17.1. Notable new features for cloud-init are as follows,

  • Python 3.6 support.
  • Ec2 support for IPv6 instance configuration.
  • Expedited boot time through cloud-id optimization.
  • Support for netplan yaml in cloud-init.
  • Add cloud-init subcommands collect-logs, analyze and schema for developers.
  • Apport integration from cloud-init via ‘ubuntu-bug cloud-init’.
  • Significant unit test and integration test coverage improvements.

Curtin

The Curtin version is updated to ‘0.1.0~bzr519-0ubuntu1’. New features are:

  • Network configuration passthrough for ubuntu and centos.
  • More resilient UEFI/grub interaction.
  • Better support for mdadm arrays.
  • Ubuntu Core 16 Support.
  • Improved bcache support.

Samba

Samba is updated to version 4.6.7. Important changes in the 4.6.x series are:

  • Multi-process Net logon support.
  • New options for controlling TCP ports used for RPC services.
  • AD LDAP and replication performance improvements.
  • DNS improvements.

    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.

October 25th, 2017

Posted In: Debian, Linux, Open Source, servers, ubuntu

Tags: , , , ,

Leave a Comment

    Ubuntu 17.04, code named Zesty Zapus; Zesty, is an adjective for ‘great enthusiasm and energy’, while Zapus, is the genus name of a North-American mouse that is said to be the only mammal on Earth that has up to 18 teeth in total.

Zesty Zapus

Zesty Zapus

 

     Ubuntu 17.04 or Zesty Zapus final release is available from April 13, 2017 and let’s see what’s new in Zesty Zapus!

Updated Kernel

Ubuntu 17.04 Alpha 2 was released on the 26th of January and all the opt-in flavors are powered by an updated kernel, version 4.9.5.

The final Zesty Zapus includes the Linux kernel 4.10, which is known to enhance the performance of Intel Kaby Lake and AMD Ryzen systems.

Driverless Printing

We all know that printers are not that friendly with Linux. Vivaldi Snapshot 1.3.537.5 Brings Improved Proprietary Media Support on Zesty Zapus.

Ubuntu 17.04 is bringing the support for IPP Everywhere. It’s a new protocol that allows personal computers and mobile devices to find and print to networked and USB printers without using vendor-specific software.

Most of the printers sold these days already support IPP protocol. This means that you don’t need to install drivers for printer from XYZ manufacturer. You can search for it on the network and use it for printing.

Unity 8

Ubuntu users have been hearing a lot about Unity 8 for the last couple of years but so far Unity 8 is nowhere to be seen officially. Of course, there are ways you can run Unity 8 in Ubuntu releases already but the fact is that you should use them only if you are Linux-savvy.

Zesty Zapus does bring this experimental build of Unity 8. Though Unity 7 will still be the default desktop environment, you can select between Unity 7 and Unity 8 at the login screen.

Unity 8

Unity 8

Note: Unity 8 won’t be the default desktop on Ubuntu 17.04 or 17.10 or 18.04. Ubuntu Unity is dead and GNOME will be the default desktop environment starting Ubuntu 18.04.

 

Swap File Instead of Swap Partition

Canonical’s Dimitri John Ledkov announced that Ubuntu 17.04 will use Swap files by default on non-LVM installs.

He explains that, quite simply, the need for a separate swap partition that’s (at least) twice the RAM size “makes little sense” on systems where memory isn’t limited.

For a common, general, machine most of the time this swap will not be used at all. Or if said swap space is in use but is of inappropriate size, changing it in-place in retrospect is painful.

Ubuntu17.04 Zesty Zapus will use swap files by default. Sizing of swap files is different to the swap partitions and typically use no more than 5% of free disk space (or 2048MB of RAM), which is another potential benefit.

The change does not apply to those who install Ubuntu using the LVM (Logical Volume Manager) option.

What’s important here is that some form of swap is maintained, it doesn’t matter how the swap is implemented. Anyone who’s ever used or set-up a ‘no swap’ system only to then run out of memory will know it’s not a pretty experience!

More Snaps

Canonical’s Will Cooke said that “by 18.04 everything will be Snaps and Unity 8 all the way down” and Engineering director Kevin Gunn, added that, “Canonical has an aggressive internal goal to try to get a usable all-snaps based image for Unity 8 out by 17.04”. So, although Snaps wouldn’t be replacing apt anytime soon.

32-bit PowerPC Support is Dropped

You might not have realized but Ubuntu till now used to support the aging 32-bit PowerPC architecture. As Debian has decided to drop this support, naturally Ubuntu followed the suit and has decided to drop the support for 32-bit PowerPC too, starting from Ubuntu 17.04.

 

ubuntu 17.04

ubuntu 17.04

 

 

     As you may have already noticed that most of these updates discussed above are found in Desktop version. So, in general, a common question automatically comes up, ‘isn’t there any changes for the new Ubuntu 17.04 server version?’ Well, of course Ubuntu released many updates for the Ubuntu 17.04 server version as well. Ubuntu Server 17.04 also comes with these following updates,

Qemu 2.8

Qemu has been updated to the 2.8 release.

Libvirt 2.5

Libvirt has been updated to version 2.5. For administrators worth to consider is that depending on the system setup and huge page size availability the specification of a page size for huge pages in a guest xml can now be mandatory.

LXD 2.12

LXD, now at version 2.12, introduces support for GPU passthrough, including NVidia CUDA. A new storage API has also been added, allowing for the creation of multiple storage pools which can then be used to host containers or independent storage volumes. And a number of new images have been added, including support for Ubuntu Core 16.

DPDK

Ubuntu 17.04 includes the latest release of DPDK, 16.11.1.

As a tech preview DPDK is now also available for ppc64el. This includes the latest improvements made in version 16.11.1 in general, but also further improvements to enable the i40e PMD and vfio-pci scanning on spapr platforms.

OpenStack Ocata

Ubuntu 17.04 includes the latest OpenStack release. OpenStack Ocata is also provided via the Ubuntu Cloud Archive for OpenStack Ocata for Ubuntu 16.04 LTS users.

Cloud-Init

Cloud-init has been updated to be stricter when identifying the cloud platform that it is running on and searching for data sources.

 

Why You Might Want to Upgrade

One nice thing for home users is the availability of driverless printing. Driverless printing will allow users to install just about any modern IPP Everywhere or Apple AirPrint-compatible printer via USB or network without installing a printer-specific driver. This is a big plus to folks who don’t like going through the rigmarole of finding and setting up print drivers for CUPS.

Other updates to the 17.04 release include an upgrade to LibreOffice 5.3, and a week view in the calendar. Standard-issue desktop apps will also migrate to Gnome 3.24, with the exceptions to Terminal, Evolution (email client), the Nautilus file manager, and Software (app store).

If you want to roll with an updated kernel in 16.04 like the 4.10 kernel that was recently released, you can use the Linux-mainline PPA to get newer kernel packages. If you choose to go this route, do so with care and be sure to keep the kernel updated because Ubuntu doesn’t officially support kernels from the mainline PPA. Things can and will break by using an unsupported kernel.

April 23rd, 2017

Posted In: Debian, Linux, New products, News, Open Source, Operating Systems, ubuntu

Tags: , , , , ,

Leave a Comment

« Previous PageNext Page »