Dns debian

Solo disponible en BuenasTareas
  • Páginas : 7 (1709 palabras )
  • Descarga(s) : 0
  • Publicado : 4 de noviembre de 2010
Leer documento completo
Vista previa del texto
CÓMO CONFIGURAR UN SERVIDOR DNS BIND9 en Debian etch: Paso 1: Instalación En los pasos para este tutorial es necesario tener sesión como root... para esto bastaría con hacer lo siguiente: # su -lm Para instalar nuestro servidor DNS nos decidiremos por Bind9: # aptitude install bind9 bind9-doc La documentación está en: /usr/share/doc/bind9-doc Para manipular el daemon en si: # /etc/init.d/bind9Usage: /etc/init.d/bind9 {start|stop|reload|restart|force-reload} Para saber con que versión de bind estamos trabajando: # named -v Nos arroja que estamos trabajando con la versión: BIND 9.3.4-P1.1

Paso 2: Configurar en nuestros hosts nuestro nuevo servidor DNS Necesitamos agregar la dirección de nuestro servidor dns al archivo /etc/resolv.conf para que nuestra máquina utilice el servidor bindque estamos montando... para esto en modo gráfico se puede hacer de la siguiente manera: Para agregarlo en gráfico (contando con el hecho de que trabajamos en GNOME): Desktop > Administration > Networking

Para agregarlo desde consola editar el archivo /etc/resolv.conf: #gedit /etc/resolv.conf Y agregar la línea: nameserver x.x.x.x Donde x.x.x.x representa la dirección ip de nuestro servidor (nousar la de loopback por ningún motivo, ni aunque el host sea el servidor). Una explicación mas a fondo sobre el archivo resolv.conf: /etc/resolv.conf is where Linux looks to find out how it should perform DNS lookups. The format is as follows:
m oc .n i am o dr u oy ni a mo d

Pretty straight forward. The first line tells it what domain you are in. This can be omitted if you want, but I wouldrecommend using it. The second line is a search pattern. This too can be omitted, but I would also recommend using it. Without it you could not do a lookup of a hostname without typing out it's fully qualified domain name. ie.. you couldn't lookup beavis. You'd have to lookup beavis.otherdomain.com. (Unless you specified this information in your /etc/hosts file) The "nameserver" lines tell it asearch order for DNS servers. Now since we are setting up BIND on your system you will need to change this file. You'll want it to look more like the following:
x. x .x . x r ev r es e ma n 1. 0. 0 .7 2 1 r ev r es e ma n m oc .n i am o dr u oy hc r ae s m oc .n i am o dr u oy ni a mo d

Replace "yourdomain.com" with whatever domain you are using and replace the "x.x.x.x" with a backup DNS serverthat you can use. (This way if your's fails you still can perform lookups). Save this file and you should be done. What this gives you so far is the ability to lookup DNS information for the Internet. Please refer to Setting up a Primary DNS Server, Section 8.4 for information on setting up a working DNS Domain. Paso 3: Configurar nuestro servidor DNS (Crear los archivos de las Zonas) Primero unpoco de explicación antes de entrar a configuraciones, esta información se encuentra en el libro DNS and BIND, 5th edition, es en el capítulo 4... apartir de 4.2 en adelante... : To tie all the zone datafiles together, a nameserver needs a configuration file; for BIND versions 8 and 9, it is usually called named.conf. The format of the zone datafiles is common to all DNS implementations: it'scalled the master file format. The format of the configuration files, on the other hand, is specific to the nameserver implementationin this case, BIND. Version 8.2.1 of bind and higher have a different layout. All bind related configuration files are now in /etc/bind. These include the zone files. Most entries in zone datafiles are called DNS resource records. DNS lookups are case-insensitive, so youcan enter names in your zone datafiles in uppercase, lowercase, or mixed case. We tend to use all lowercase. However, even though lookups are case-insensitive, case is preserved. That way, if you add records for Titanic.movie.edu to your zone data, people looking up titanic.movie.edu will find the records, but with a capital "T" in the domain name.Resource records must start in the first column...
tracking img