BioliZards.be

DreamOn Technical Blog

Category: Homelab

HomeLab: DNS step 2: Setting up a BIND slave DNS server on SLES

DNS will be a major service in our network and must be up and running 100% To accomplish this we will install a secondary DNS server (slave).

The purpose of a slave name server is to share the load with the master server, or handle the entire load if the master server is down. A slave name server loads its data over the network from another name server usually the master name server, but it can load from another slave name server too.
This process is called a zone transfer.

For the installation of a slave dns we need a second virtual machine:

  • 1 vCPU
  • 512 MB Ram
  • Harddisk – 10GB
  • Network to your operational lan (ip: 172.30.1.3)
  • OS SLES 11 (64-bit)
We need to install the bind package on this server to, and do an initial configuration of the server. Continue reading

HomeLab: DNS step 1: Setting up a BIND master DNS server on SLES

I’m building my redundant DNS server setup. DNS is short for Domain Name System.

Very basically explained DNS translates domain names into IP addresses and vice versa.

You can find more information about DNS on wikipedia article:
http://en.wikipedia.org/wiki/Domain_Name_System

I’ll be installing my DNS server on a SUSE Linux Enterprise Server (SLES) hosted on a vmware virtual environment. The DNS software I’ll be using is BIND (Berkeley Internet Name Domain).
I’m choosing to use BIND because there is a lot of information out there about BIND and it is the de facto standard DNS server software if you are running a Unix-like OS.

These are the features I want:

  • Run a DNS to resolve internal and external domain names into IP addresses and vice versa.
    (the internal domain name will be biolizards.local, the ip range will be 172.30.0.0/16)
  • Make my DNS server Redundant against server outage

I will split this guide in 2 posts:

DNS step 1: Setting up a BIND master DNS server on SLES

DNS step 2: Setting up a BIND slave DNS server on SLES

Continue reading

Homelab: Router Step 2: pfsense basic install


This is a follow up post for Installing pfsense router on ESXi

if you mist the first post you can read it here.

Step 2 : Configure a basic pfsense
The default ip for pfsense on the lan side is 192.168.1.1
I’m going to change this because I want it to be 172.30.1.1/16
I’m also going to enable DHCP on the lan side
After that I will do a initial config with the wizard Continue reading

Homelab: Router Step 1: Installing pfsense router on ESXi

As you might have read on my homelab page I’m starting to rebuild my test environment from scratch
(I like to call it my homelab).

To start off I’ll be installing pfsense as a temporary router.


pfSense is a free, open source customized distribution of FreeBSD tailored for use as a firewall and router. In addition to being a powerful, flexible firewalling and routing platform, it includes a long list of related features and a package system allowing further expandability without adding bloat and potential security vulnerabilities to the base distribution. More information can be found on the pfsense website

Since I’m building my homelab on a ESXi server I’ll need to create a virtual server with following specifications:

Before we start installing we must download the installation iso.
Since version 2.0-rc3 is available I will install that one.
You can download it here: http://blog.pfsense.org/?p=589.
I downloaded this version pfSense-2.0-RC3-amd64-20110621-2308.iso Continue reading

© 2017 BioliZards.be

Theme by Anders NorenUp ↑