Hola.
Aqui tienes mi configuracion.
dhcpd.conf esta hecho con YaST pero corregido a mano, ya que habia una entrada
incorrecta, creo que la de netbios-node-type, que pone netbios.-note-type (en
9.0)
bueno. te añado comentarios sobre el propio fichero de configuracion.
admin@pamplona:~> cat /etc/dhcpd.conf
#
# This file was generated by YaST2.
#
# If you update it manually, YaST2 component for DHCP server
# configuration will rewrite it next time you use it.
#
# Creation time: Fri Jul 30 16:14:55 CEST 2004
#
autorizative;
ddns-update-style interim;
# activa las dos siguientes entradas si quieres actualizar el servidor dns con
los datos de los equipos asignados (nombre + ip)
ddns-updates on;
ignore client-updates;
# desactiva las dos lineas anteriores y activa las dos lineas siguientes para
no actualizar dns (recomendado primero probar que funcione el dhcp solo y
luego activar la actualizacion dns)
#ddns-update-style none;
#ddns-updates off;
# tiempo de concesion de la ip (en segundos)
default-lease-time 86400;
log-facility local7;
# tiempo maximo de cesion de una ip
max-lease-time 604800;
# datos de red a pasar a los equipos dominio, servidor wins, tipo de
autentificacion wins, servidor dns, gateway por defecto.
option domain-name "midominio.es";
option netbios-name-servers 192.168.2.115, 192.168.5.116;
option netbios-node-type 8;
option domain-name-servers 192.168.2.254;
option routers 192.168.2.113;
# esto es una llave para la comunicacion con el servidor dns
# generated by genDDNSKey.sh on Wed Jul 28 19:40:30 CEST 2004
key DHCP_UPDATER {
algorithm hmac-md5;
secret
"M+IetUcjLqZTcjZb/GYdJCraddHvFoevvUXI654TPe1sIaNcl9GyvX0hJEB/Xi7sBJCKRjQyOha
ibSB9gOvSGA==";
};
# doy de alta las zonas dns que voy a actualizar y les indico con que llave
zone midominio.es. {
primary 127.0.0.1;
key DHCP_UPDATER;
}
zone 2.168.192.in-addr.arpa. {
primary 127.0.0.1;
key DHCP_UPDATER;
}
# ahora declaro las subredes y los rangos de direcciones dejo de la 100 a la
130 y de la 241 a la 254 sin asignar
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.1 192.168.2.99;
range 192.168.2.131 192.168.2.240;
}
# declaro los equipos de ip fija con su MAC
host sumtec4 {
fixed-address 192.168.2.115;
hardware ethernet 00:10:5A:D0:FC:DF;
}
# incluso impresoras de red
host GP605 {
fixed-address 192.168.2.102;
hardware ethernet 00:C0:85:2C:1A:D2;
}
***************************
Configuracion dns named.conf
esta configurado a mano. pero partiendo de la configuracion base del YaST2
pamplona:/home/Administrador # cat /etc/named.conf
# Copyright (c) 2001-2003 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/bind9/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind9/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; };
#listen-on port 53 { 127.0.0.1; 192.168.4.113; };
# 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; };
#listen-on-v6 { none; };
# 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;
};
# 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.
# aqui declaro la misma llave que en el dhcpd.conf
# generated by genDDNSKey.sh on Wed Jul 28 19:40:30 CEST 2004
key DHCP_UPDATER {
algorithm hmac-md5;
secret
"M+IetUcjLqZTcjZb/GYdJCraddHvFoevvUXI654TPe1sIaNcl9GyvX0hJEB/Xi7sBJCKRjQyOha
ibSB9gOvSGA==";
};
# digo para cada zona en que fichero esta y con que llave se permiten las
actualizaciones
server 127.0.0.1 {
keys { DHCP_UPDATER ;};
};
zone "." in {
type hint;
file "root.hint";
};
zone "localhost" in {
type master;
file "localhost.zone";
};
# zona de midominio (cambio el nombre real ;-). pz es un directorio dentro
de /var/lib/named/
zone "midominio.es" {
notify no;
type master;
file "pz/midominio.es";
allow-update { key DHCP_UPDATER; };
};
# zona de resolucion inversa, no la actualizo porque no tengo autoridad, tengo
una sola ip de esa zona
zone "125.98.213.in-addr.arpa" IN {
type master;
file "pz/213.98.125";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
# zona de resolucion inversa del dominio local. esta si la actualizo.
zone "2.168.192.in-addr.arpa" in {
type master;
file "pz/192.168.2.zone";
allow-update { key DHCP_UPDATER; };
};
# tambien tengo otras subredes que no se gestionan con dhcp pero mantengo sus
zonas a mano, tanto directas como inversas.
zone "3.168.192.in-addr.arpa" in {
type master;
file "pz/192.168.3.zone";
};
zone "1.168.192.in-addr.arpa" in {
type master;
file "pz/192.168.1.zone";
};
zone "5.168.192.in-addr.arpa" in {
type master;
file "pz/192.168.5.zone";
};
zone "4.168.192.in-addr.arpa" in {
type master;
file "pz/192.168.4.zone";
};
# Include the meta include file generated by SuSEconfig.named. 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.
*********************************
Y aqui te va de ejemplo los ficeros de definicion de zonas.
primero de resolucion directa
pamplona:/home/Administrador # cat /var/lib/named/pz/midominio.es
$ORIGIN .
$TTL 172800 ; 2 days
midominio.es IN SOA midominio.es. root.midominio.es. (
200410320 ; serial
28800 ; refresh (8 hours)
7200 ; retry (2 hours)
604800 ; expire (1 week)
86400 ; minimum (1 day)
)
NS ns.midominio.es.
MX 10 mail.midominio.es.
$ORIGIN midominio.es.
$TTL 43200 ; 12 hours
berlin A 192.168.2.237
TXT "3151801748c0626a00bcc1643063541dff"
berna A 192.168.2.38
TXT "319a1190a843b2751ca7d61aec8e049a7f"
brujas A 192.168.2.41
TXT "315618ddf1155df0de00d7514131488130"
cairo A 192.168.2.48
TXT "3197b72110706d437c831c4eab1e7d50d5"
$TTL 172800 ; 2 days
dns1 A 192.168.2.254
$TTL 43200 ; 12 hours
dorea A 192.168.2.32
TXT "31023a12b434fcb922905656ae407c3e81"
dublin A 192.168.2.236
TXT "31730b1cc3eb5e82fdd55db97090272d56"
edimburgo A 192.168.2.224
TXT "31e65c991ea73b4ba6bed163348737f4c4"
$TTL 172800 ; 2 days
$TTL 43200 ; 12 hours
flamenco A 192.168.2.238
TXT "31c0a39e75ea5486d4770b02f7b0a8c768"
florencia A 192.168.2.44
TXT "31e93b6213da4d93d0cdd11118a99180cd"
helsinki A 192.168.2.51
TXT "31979927a18635ed37c705ec4dadf9c121"
kobe A 192.168.2.60
TXT "313b4ce296027727609189b38e215a1190"
$TTL 172800 ; 2 days
localhost A 127.0.0.1
$TTL 43200 ; 12 hours
londres A 192.168.2.190
TXT "31bcb886eacf8940e082a08276d37de64f"
$TTL 172800 ; 2 days
mail A 192.168.4.113
$TTL 43200 ; 12 hours
mexico A 192.168.2.239
TXT "31633f28372978347d0091ec696aff3afa"
milan A 192.168.2.25
TXT "319d427648f7d9d82b2e439d6f5d14bebf"
$TTL 172800 ; 2 days
monaco A 192.168.1.4
$TTL 43200 ; 12 hours
moscu A 192.168.2.23
TXT "31f410a921b1fe4300ed4b5c018400072d"
niza A 192.168.2.27
TXT "31e646a3ebc678d15e50b2cf5a11752615"
$TTL 172800 ; 2 days
ns A 192.168.2.254
$TTL 43200 ; 12 hours
nuevayork A 192.168.2.40
TXT "31ad2a0d682329e89edfa5d2faba6d8756"
$TTL 172800 ; 2 days
orlando A 192.168.1.10
$TTL 43200 ; 12 hours
Oscar A 192.168.2.227
TXT "31c2825c6b33ea1ed16f60b21855268d90"
oslo A 192.168.2.18
TXT "3126aa4c2302c46959dfea0127b2595be8"
oxford A 192.168.2.33
TXT "31f079afefff88b2668f995081fc0a96b0"
pekin A 192.168.2.47
TXT "3121a896e2b60efbaa1a196eb35f75ac4c"
rio A 192.168.2.221
TXT "31817108f8465718f8d44bc15e956f73b4"
ROMA2 A 192.168.2.240
TXT "312e61365958c1e36e6e7266b923d2fdd4"
$TTL 172800 ; 2 days
web A 192.168.4.113
$TTL 43200 ; 12 hours
valencia A 192.168.2.29
TXT "3140e60e5ab7088e2145c48bf2b1f0ff19"
venecia A 192.168.2.20
TXT "315c679bac4c5a4ed37a37b83acc4702e5"
verona A 192.168.2.24
TXT "312ca1635ca943e74fdef2c950e1667888"
viena A 192.168.2.229
TXT "31f5b41d49fafa9744b352fa2ee569457d"
$TTL 172800 ; 2 days
www A 192.168.4.113
# y esta de resolucion inversa.
pamplona:/home/Administrador # cat /var/lib/named/pz/192.168.2.zone
$ORIGIN .
$TTL 604800 ; 1 week
2.168.192.in-addr.arpa IN SOA pamplona.midominio.es. root.midominio.es. (
1538 ; serial
172800 ; refresh (2 days)
14400 ; retry (4 hours)
3628800 ; expire (6 weeks)
604800 ; minimum (1 week)
)
NS pamplona.midominio.es.
$ORIGIN 2.168.192.in-addr.arpa.
$TTL 43200 ; 12 hours
18 PTR oslo.midominio.es.
189 PTR dublin.midominio.es.
190 PTR londres.midominio.es.
20 PTR venecia.midominio.es.
221 PTR rio.midominio.es.
224 PTR edimburgo.midominio.es.
227 PTR Oscar.midominio.es.
229 PTR viena.midominio.es.
23 PTR moscu.midominio.es.
236 PTR dublin.midominio.es.
237 PTR berlin.midominio.es.
238 PTR flamenco.midominio.es.
239 PTR mexico.midominio.es.
24 PTR verona.midominio.es.
240 PTR ROMA2.midominio.es.
25 PTR milan.midominio.es.
$TTL 604800 ; 1 week
254 PTR pamplona.midominio.es.
$TTL 43200 ; 12 hours
27 PTR niza.midominio.es.
29 PTR valencia.midominio.es.
32 PTR dorea.midominio.es.
33 PTR oxford.midominio.es.
38 PTR berna.midominio.es.
40 PTR nuevayork.midominio.es.
41 PTR brujas.midominio.es.
44 PTR florencia.midominio.es.
47 PTR pekin.midominio.es.
48 PTR cairo.midominio.es.
51 PTR helsinki.midominio.es.
60 PTR kobe.midominio.es.
pamplona:/home/Administrador #
en cualquiera de los dos ficheros de zona puedes combinar entradas fijas y
manuales con entradas dinamicas gestionadas por el dhcpd.
El Lunes, 6 de Diciembre de 2004 02:25, miguel gmail escribió:
Hola,
estoy configurando un servidor dhcp, pero no consigo que arranque.
El fichero de configuracion, creado con yast, es el siguiente:
#
# This file was generated by YaST2.
#
# If you update it manually, YaST2 component for DHCP server
# configuration will rewrite it next time you use it.
#
# Creation time: Fri Dec 3 22:12:32 GMT 2004
#
ddns-update-style none;
ddns-updates off;
default-lease-time 600;
log-facility local7;
max-lease-time 7200;
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
}
Ademas, especifique en yast eth1 como la tarjeta que provee de ip
dinamica, en la red 192.168.0.0/24 (es correcta esa denominacion??).
Tengo las siguientes dudas:
1. Donde se haria a pelo la configuracion de eth1 como la tarjeta de
red donde corre dhcpd? (en dhcpd.conf no hay nada al respecto).
2. El servidor dhcp parece que arranca bien, no devuelve ningun error,
pero los clientes no consiguen IP dinamica. Estos son un WXP y un SL
9.2 (en la misma maquina). Que mas falta??
La conexion a internet con una ip estatica tipo 192.168.0.2 funciona
perfectamente en ambos pc's.
--
Saludos,
miguel
--
Un Saludo.
Carlos Lorenzo Matés