ComTech: IT Support Stirling
TwitterFacebookGoogle

How to set up a DNS Server on Debian 6.0 “Squeeze”

Today we are going to set up and configure a DNS Server on Debian 6.0 “Squeeze”.  We will be using the bind9 package which does not come by default so we will need to install it. Open up a terminal and type:

sudo apt-get install bind9

There are four files which we we need to configure.  Lets take the first.  In a terminal type:

sudo nano /etc/bind/named.conf.local

I have used nano to open up the file but use whichever text editor you are happy with. Insert the following code into the file:

——————————————————————————————————————————–

# This is the zone definition. replace example.com with your domain name
zone “comtech.com” {
type master;
file “/etc/bind/zones/comtech.com.db”;
};

# This is the zone definition for reverse DNS. replace 0.168.192 with your network address in reverse notation – e.g my network address is 192.168.0
zone “1.168.192.in-addr.arpa” {
type master;
file “/etc/bind/zones/rev.0.168.192.in-addr.arpa”;
};

——————————————————————————————————————————–


Replace comtech.com with the name of your DNS domain (this is not the same as an active directory domain but rather a name for your DNS zone).

Next up we shall configure the options file. In the terminal type:

sudo nano /etc/bind/named.conf.options

Within this file we need to modify the forwarder with the address of your ISP’s DNS servers. So modify the file adding the following:

——————————————————————————————————————————–

forwarders {

194.72.0.114;
194.74.65.69;
};

——————————————————————————————————————————–

Replace the addresses above with the addresses of your ISP’s DNS servers.

Now we need to add the zones file:

sudo mkdir /etc/bind/zones

Now we need to configure it by typing:

sudo nano /etc/bind/zones/comtech.com.db (replace comtech.com with your DNS domain).

To configure the file you will need to add the following:

——————————————————————————————————————————–

// replace example.com with your domain name. do not forget the . after the domain name!
// Also, replace ns1 with the name of your DNS server
comtech.com. IN SOA chris-server.comtech.com.
// Do not modify the following lines!
2006081401
28800
3600
604800
38400

)

// Replace the following line as necessary:
// ns1 = DNS Server name
// mta = mail server name
// example.com = domain name
comtech.com. IN NS chris-server.comtech.com.
comtech.com. IN MX 10 mta.example.com.

// Replace the IP address with the right IP addresses.
www IN A 192.168.1.4
mta IN A 192.168.0.3
chris-server IN A 192.168.1.4

——————————————————————————————————————————–

In the above code replace the following:

comtech.com with your DNS domain name,

192.168.1.4 with your static DNS server address,

chris-server.comtech.com with your computers hostname.dns-domain,

mta is your mail server (if you have one). If you do modify the IP address to show this.

Next we have to create the reverse DNS zone file:

sudo nano /etc/bind/zones/rev.1.168.192.in-addr.arpa

Add the following code:

——————————————————————————————————————————–

//replace example.com with your domain name, ns1 with your DNS server name.
// The number before IN PTR example.com is the machine address of the DNS server
@ IN SOA chris-server.comtech.com admin.comtech.com. (
2006081401;
28800;
604800;
604800;
86400
)

IN NS chris-server.comtech.com.
1 IN PTR comtech.com

——————————————————————————————————————————–

All that is left to do is restart bind:

sudo service bind9 restart

Don’t forget to test the new configuration:

dig comtech.com

About the Author

Hi I am Chris Wakefield the owner of ComTech IT Support. I provide Windows and Linux based IT Support, laptop repairs and computer repairs to both business and personal clients in and around Stirling.

For a list of what I can offer you why not visit my website www.comtech247.net where you will find a list of my services, testimonials, blog and much more.

How to set up a DHCP server on Debian 6.0 “Squeeze”

Today I will show you how to set up a DHCP server on Debian 6.0.  The main package you will need is called isc-dhcp-server which is not installed by default so open up a terminal and type:

sudo apt-get install isc-dhcp-server

There are two main files we will need to configure, these being /etc/default/isc-dhcp-server and /etc/dhcp/dhcpd.conf.

Lets take /etc/default/isc-dhcp-server first.  Open up a terminal and using your favourite text editor type:

sudo nano /etc/default/isc-dhcp-server

You should get the following:

———————————————————————————————–

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. “eth0 eth1?.
INTERFACES=”eth0″

————————————————————————————————–

Replace eth0 above with the name of your network interface that you want the server to lease addresses on.  Save the file and exit.


Now lets take the /etc/dhcp/dhcpd.conf file next.  Open up a terminal and type:

sudo nano /etc/dhcp/dhcpd.conf

which should give you the output below.

————————————————————————————————-

#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages (‘none’, since DHCP v2 didn’t
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks…
option domain-name “example.org”;
option domain-name-servers ns1.example.org, ns2.example.org;

option domain-name “comtech.com”;
default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.150 10.0.0.253;
option routers 10.0.0.2;
option subnet-mask 255.255.255.0;

option broadcast-address 10.0.0.254;
option domain-name-servers 10.0.0.1, 10.0.0.2;

option ntp-servers 10.0.0.1;
option netbios-name-servers 10.0.0.1;
option netbios-node-type 8;
}

# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;

#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don’t really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name “internal.example.org”;
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename “vmunix.passacaglia”;
# server-name “toccata.fugue.com”;
#}

# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class “foo” {
# match if substring (option vendor-class-identifier, 0, 4) = “SUNW”;
#}

#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of “foo”;
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of “foo”;
# range 10.0.29.10 10.0.29.230;
# }
#}

————————————————————————————————

This needs a little bit of explaining.

1. Everything in bold needs adding to the file.  Adjust the network settings according to your network requirements.

2. The option domain name is your dns zone name.  For example mine is set to comtech.com.

3. Range should be the range of ip addresses that you want the server to give out to clients.

Now restart the dhcp service by typing:

sudo service isc-dhcp-server restart

That is your server configured however it is always best to double check so open up a terminal and type:

sudo netstat -uap

This should show you the following information (please be aware that your system might be slightly different).

————————————————————————————————

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

udp 0 0 *:55827 *:* 916/avahi-daemon: r
udp 0 0 server01.lo:domain *:* 1273/named
udp 0 0 server01:domain *:* 1273/named
udp 0 0 *:bootps *:* 4525/dhcpd
udp 0 0 *:17500 *:* 1768/dropbox
udp 0 0 *:54407 *:* 4539/VirtualBox
udp 0 0 10.0.0.255:netbios-ns *:* 1016/nmbd
udp 0 0 server01:netbios-ns *:* 1016/nmbd
udp 0 0 *:netbios-ns *:* 1016/nmbd
udp 0 0 10.0.0.255:netbios-dgm *:* 1016/nmbd
udp 0 0 server01:netbios-dgm *:* 1016/nmbd
udp 0 0 *:netbios-dgm *:* 1016/nmbd
udp 0 0 *:mdns *:* 916/avahi-daemon: r
udp6 0 0 [::]:domain [::]:* 1273/named
udp6 0 0 [::]:51853 [::]:* 916/avahi-daemon: r
udp6 0 0 [::]:mdns [::]:* 916/avahi-daemon: r

————————————————————————————————

This shows that the dhcp service is working

About the Author

Hi I am Chris Wakefield the owner of ComTech IT Support. I provide Windows and Linux based IT Support, laptop repairs and computer repairs to both business and personal clients in and around Stirling.

For a list of what I can offer you why not visit my website www.comtech247.net where you will find a list of my services, testimonials, blog and much more.

CyberChimps
Follow

Get every new post delivered to your Inbox

Join other followers

WordPress SEO fine-tune by Meta SEO Pack from Poradnik Webmastera
WP Like Button Plugin by Free WordPress Templates