View New Content

Welcome to Steams Community @ Play. Win. Repeat.
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Bun venit pe Steams Community @ Play. Win. Repeat.

Bun venit pe Steams Community @ Play. Win. Repeat., pentru a avea full acces la forum te rugam sa te inregistrezi.
Ai mai multe motive pentru care sa te inregistrezi:

Acces la un forum structurat in parametri profesionali
Sansa de a da sau a primi like din partea membriilor
Sansa de a face parte din echipa steams
Alaturarea unei comunitati de viitor

Inregistreaza-te gratuit, acum!

In caz ca aveti probleme cu activarea/crearea/conectarea contului de pe forum lasati-ne un mesaj aici

Guest Message by DevFuse

Server DNS

Started by alex, Jun 30 2012 02:56 AM

Please log in to reply

1 reply to this topic

#1
alex

Posted 30 June 2012 - 02:56 AM

Moderator

Founders
416 posts

Game Nick:alex
Y!M:alecsutzuu
Country:
City:București

Instalarea si configurarea unui Server DNS
Pasul 1
Instalam bind9

# apt-get install bind9 dnsutils

# /etc/init.d/bind9 stop

Pasul 2
In directorul /etc/bind vom configura urmatoarele fisiere si vom creea un director zones unde vom pune fisierele db.slashlinux.info si db.192 .

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

named.conf.local

zone "slashlinux.info" {

  type master;

  file "/etc/bind/zones/db.slashlinux.info";

  };



	zone "0.168.192.in-addr.arpa" {

  type master;

  file "/etc/bind/zones/db.192";

  };

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

named.conf.options

forwarders {

			0.0.0.0; ## IP-ul ISP-ului vostru

	   };

# mkdir /etc/bind/zones

# nano /etc/bind/zones/db.slashlinux.info

db.slashlinux.info

$TTL 86400

  $ORIGIN info.

  slashlinux	  IN	  SOA	 ns1.slashlinux.info. root.slashlinux.info.(

							 2010021700	  ; Serial

							 10800		   ; Refresh

							 3600			; Retry

							 3600000		 ; Expire

							 86400   )	   ; Minimum



		  IN	  NS			  ns1.slashlinux.info.



		  IN	  MX	  10	  mail.slashlinux.info.

		  IN	  MX	  20	  slashlinux.info.

		  IN	  A			   192.168.0.1



  $ORIGIN slashlinux.info.

  www			 IN	  A	   192.168.0.1

  mail			IN	  A	   192.168.0.1

  ns1			 IN	  A	   192.168.0.1

  root			IN	  A	   192.168.0.1

# nano /etc/bind/zones/db.192

db.192

$TTL 86400

  $ORIGIN info.

  slashlinux	  IN	  SOA	 ns1.slashlinux.info. root.slashlinux.info.(

							 2010021700	  ; Serial

							 10800		   ; Refresh

							 3600			; Retry

							 3600000		 ; Expire

							 86400   )	   ; Minimum



		  IN	  NS			  ns1.slashlinux.info.



		  IN	  MX	  10	  mail.slashlinux.info.

		  IN	  MX	  20	  slashlinux.info.

		  IN	  A			   192.168.0.1



  $ORIGIN slashlinux.info.

  www			 IN	  A	   192.168.0.1

  mail			IN	  A	   192.168.0.1

  ns1			 IN	  A	   192.168.0.1

  root			IN	  A	   192.168.0.1

Pasul 3
Restartam bind9 si verificam cu comanda dig.

# /etc/init.d/bind9 start

# rndc reload

# dig slashlinux.info

output-ul comenzii dig

; <<>> DiG 9.7.0-P1 <<>> slashlinux.info

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43972

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0



;; QUESTION SECTION:

;slashlinux.info.			   IN	  A



;; ANSWER SECTION:

slashlinux.info.		82101   IN	  A	   192.168.0.1



;; AUTHORITY SECTION:

slashlinux.info.		82101   IN	  NS	  ns1.slashlinux.info.



;; Query time: 1 msec

;; SERVER: 193.138.192.2#53(192.168.0.0)

;; WHEN: Thu Aug  4 17:09:45 2011

;; MSG SIZE  rcvd: 67