KONFIGURASI DNS LINUX SUSE 10.2

Seeting DNS Linux Suse 10.2

Contoh Kasus :

Domain : biner.com

IP server : 192.168.254.1

1. Install linux Suse 10.2

Siapkan PC untuk install linux suse, install dengan mode text.

2. Setting IP

yast -> Network Device -> Network Card -> Traditional Method with ifup -> pilih card -> edit -> Statistic Address Setup

-> Ip Address : 192.168.254.1 -> Subnet Mask : 255.255.255.0 -> Next -> Finish

3. Hostname

yast -> Network Service -> DNs and Hostname -> Hostname : server -> Domain Name : biner.com -> Finish

4. Install aplikasi

untuk DNS :

bind

DNS Server

untuk webserver:

apache

yast2-http-server

tool:

mc

5. aktifkan IP forwarding

Yast -> Network Service -> routing

aktifkan : enable IP Forwarding

6. Menjalankan bind

# /etc/init.d/named start

7. setting DNS

a. named.conf

1. vi /etc/named.conf

# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.

# All rights reserved.

#

# Author: Frank Bodammer, Lars Mueller

#

# /etc/named.conf

#

# This is a sample configuration file for the name server BIND 9. It works as

# a caching only name server without modification.

#

# A sample configuration for setting up your own domain can be found in

# /usr/share/doc/packages/bind/sample-config.

#

# A description of all available options can be found in

# /usr/share/doc/packages/bind/misc/options.

options {

# The directory statement defines the name server’s working directory

directory “/var/lib/named”;

# Write dump and statistics file to the log subdirectory. The

# pathenames are relative to the chroot jail.

dump-file “/var/log/named_dump.db”;

statistics-file “/var/log/named.stats”;

# The forwarders record contains a list of servers to which queries

# should be forwarded. Enable this line and modify the IP address to

# your provider’s name server. Up to three servers may be listed.

#forwarders { 192.0.2.1; 192.0.2.2; };

# Enable the next entry to prefer usage of the name server declared in

# the forwarders section.

#forward first;

# The listen-on record contains a list of local network interfaces to

# listen on. Optionally the port can be specified. Default is to

# listen on all interfaces found on your system. The default port is

# 53.

#listen-on port 53 { 127.0.0.1; };

# The listen-on-v6 record enables or disables listening on IPv6

# interfaces. Allowed values are ‘any’ and ‘none’ or a list of

# addresses.

listen-on-v6 { any; };

# The next three statements may be needed if a firewall stands between

# the local server and the internet.

#query-source address * port 53;

#transfer-source * port 53;

#notify-source * port 53;

# The allow-query record contains a list of networks or IP addresses

# to accept and deny queries from. The default is to allow queries

# from all hosts.

#allow-query { 127.0.0.1; };

# If notify is set to yes (default), notify messages are sent to other

# name servers when the the zone data is changed. Instead of setting

# a global ‘notify’ statement in the ‘options’ section, a separate

# ‘notify’ can be added to each zone definition.

notify no;

include “/etc/named.d/forwarders.conf”;

};

# To configure named’s logging remove the leading ‘#’ characters of the

# following examples.

#logging {

# # Log queries to a file limited to a size of 100 MB.

# channel query_logging {

# file “/var/log/named_querylog”

# versions 3 size 100M;

# print-time yes; // timestamp log entries

# };

# category queries {

# query_logging;

# };

#

# # Or log this kind alternatively to syslog.

# channel syslog_queries {

# syslog user;

# severity info;

# };

# category queries { syslog_queries; };

#

# # Log general name server errors to syslog.

# channel syslog_errors {

# syslog user;

# severity error;

# };

# category default { syslog_errors; };

#

# # Don’t log lame server messages.

# category lame-servers { null; };

#};

# The following zone definitions don’t need any modification. The first one

# is the definition of the root name servers. The second one defines

# localhost while the third defines the reverse lookup for localhost.

zone “.” in {

type hint;

file “root.hint”;

};

zone “localhost” in {

type master;

file “localhost.zone”;

};

zone “0.0.127.in-addr.arpa” in {

type master;

file “127.0.0.zone”;

};

# Include the meta include file generated by createNamedConfInclude. This

# includes all files as configured in NAMED_CONF_INCLUDE_FILES from

# /etc/sysconfig/named

include “/etc/named.conf.include”;

# You can insert further zone records for your own domains below or create

# single files in /etc/named.d/ and add the file names to

# NAMED_CONF_INCLUDE_FILES.

# See /usr/share/doc/packages/bind/README.SUSE for more details.

2. Tekan tombol Insert untuk edit file named.conf, tambahkan dibawah ini

zone “biner.com” {

type master;

file “/var/lib/named/master/biner.com.hosts”;

};

zone “254.168.192.in-addr.arpa” {

type master;

file “/var/lib/named/master/192.168.254.rev”;

};

3. simpan

tekan Esc + shift : wq

B. biner.com.hosts

1. vi /var/lib/named/master/biner.com.hosts

$ttl 38400

biner.com. IN SOA server.biner.com. server.biner.com. (

2010012302

10800

3600

604800

38400 )

biner.com. IN NS server.biner.com.

server.biner.com. IN A 192.168.254.1

biner.com. IN MX 10 mail.biner.com

C. 192.168.254.rev

1. vi /var/lib/named/master/192.168.254.rev

$ttl 38400

254.168.192.in-addr.arpa. IN SOA server.biner.com. server.biner.com. (

2010012301

10800

3600

604800

38400 )

254.168.192.in-addr.arpa. IN NS server.biner.com.

1.254.168.192.in-addr.arpa. IN PTR server.biner.com.

D. Cek DNS

1. Restart bind

# /etc/init.d/named restart

Shutting down name server BIND done

Starting name server BIND done

(jika masih belum muncul seperti di atas masih salah cek lagi penulisannya )

2. cek host

# host server.biner.com

server.biner.com has address 192.168.254.1

3. cek server

# nslookup server

Server: 127.0.0.1

Address: 127.0.0.1#53

Name: server.biner.com

Address: 192.168.254.1


sumber :

http://wahcilik.wordpress.com/