Scribd
Upload
36 views3 pages

Requisitos Previos.: DNS Bind

1. The document provides instructions for installing and configuring BIND (Berkeley Internet Name Domain), an open-source implementation of the Domain Name System (DNS) protocol. It includes downloading BIND, compiling it from source, configuring zones and name servers, and testing the DNS server. 2. Key steps are downloading and extracting BIND, configuring options and zones in /etc/named.conf, starting the named process, and verifying it is running by checking logs and performing a DNS lookup to resolve a domain name. 3. For client machines to use the new DNS server, their /etc/resolv.conf file needs to be edited to point to the IP address of the

Uploaded by

Dassaef Torres
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
36 views3 pages

Requisitos Previos.: DNS Bind

1. The document provides instructions for installing and configuring BIND (Berkeley Internet Name Domain), an open-source implementation of the Domain Name System (DNS) protocol. It includes downloading BIND, compiling it from source, configuring zones and name servers, and testing the DNS server. 2. Key steps are downloading and extracting BIND, configuring options and zones in /etc/named.conf, starting the named process, and verifying it is running by checking logs and performing a DNS lookup to resolve a domain name. 3. For client machines to use the new DNS server, their /etc/resolv.conf file needs to be edited to point to the IP address of the

Uploaded by

Dassaef Torres
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

DNS Bind

Indispensable haber cumplido con los requisitos previos. http://www.isc.org/ ftp://ftp.isc.org/isc/bind9/9.2.3/bind-9.2.3.tar.gz gunzip -dc <bind-versin.tar.gz> | tar xvf cd <bind-versin> export PATH=$PATH:/usr/ccs/bin export CC=gcc ./configure make make install Bajar el archivo de los ROOT name servers ftp://ftp.internic.org/domain/named.root Crear el directorio para los archivos del DNS mkdir -p /etc/named Copiar el archivo named.root que bajamos de internet a este directorio cp named.root /etc/named Generar el archivo /etc/named.conf como mnimo con lo siguiente: options { directory "/etc/named"; pid-file "named.pid"; };

zone "0.0.127.in-addr.arpa" { type master; file "127.0.0.revzone"; notify no; }; zone "." { type hint; file "named.root"; }; Ejecutar el binario que se gener /usr/local/sbin/named Para verificar que este funcionando

1.- Revisar el /var/adm/messages grep named /var/adm/messages Mar 6 15:23:58 hosts named[27918]: [ID 873579 Mar 6 15:23:58 hosts named[27918]: [ID 873579 /etc/rndc.key: file not found Mar 6 15:23:58 hosts named[27918]: [ID 873579 command channel 127.0.0.1#953: file not found Mar 6 15:23:58 hosts named[27918]: [ID 873579 /etc/rndc.key: file not found Mar 6 15:23:58 hosts named[27918]: [ID 873579 command channel ::1#953: file not found Mar 6 15:23:58 hosts named[27918]: [ID 873579 addr.arpa/IN: loading master file 127.0.0.revzon e: file not found 2.- Hacer una consulta al dns recin instalado nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. > server 127.0.0.1 Default server: 127.0.0.1 Address: 127.0.0.1#53 > www.oracle.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: www.oracle.com Address: 148.87.9.44 > dig @127.0.0.1 oracle.com ; <<>> DiG 9.2.3 <<>> @127.0.0.1 oracle.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19720 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;oracle.com. IN A ;; ANSWER SECTION: oracle.com. 7200 IN A 148.87.9.44 daemon.notice] starting BIND 9.2.3 daemon.error] none:0: open: daemon.notice] couldn't add daemon.error] none:0: open: daemon.notice] couldn't add daemon.error] zone 0.0.127.in-

;; AUTHORITY SECTION: oracle.com. 10640 IN NS oracle.com. 10640 IN NS oracle.com. 10640 IN NS oracle.com. 10640 IN NS

udns2.ultradns.net. ns1.oracle.com. ns4.oracle.com. udns1.ultradns.net.

;; ADDITIONAL SECTION: ns1.oracle.com. 10640 IN A 148.87.1.20 ns4.oracle.com. 10640 IN A 148.87.112.100 udns1.ultradns.net. 172640 IN A 204.69.234.1 udns2.ultradns.net. 172640 IN A 204.74.101.1 ;; ;; ;; ;; Query time: 129 msec SERVER: 127.0.0.1#53(127.0.0.1) WHEN: Thu Mar 4 20:42:13 2004 MSG SIZE rcvd: 196

Para que una mquina use el nuevo DNS. Editar el /etc/resolv.conf nameserver ip.del.servidor <-------- DNS primario nameserver 148.202.1.29 <-------- DNS secundario (usado solo si el 1rio no contesta) nameserver 148.202.3.5 <-------- DNS N

You might also like