[email protected] escribió:
> [email protected] escribió:
>>> [email protected] escribió:
>>>> saludos mi tropa
>>>> tengo un bind en mi red con vistas para:
>>>> red lan 172.16.1.0/24
>>>> red wan 192.168.159.160/28
>>>>
>>>> hasta ahi rula todo ok
>>>>
>>>> ahora tengo otra wan además de la existente 192.168.161.176/28 y
cuando
>>>> digo wan, dos enlaces frame relay
>>>>
>>>>
>>>> mi problema es el siguiente
>>>> dns en la wan1
>>>> 192.168.159.162
>>>>
>>>> consultando dns
>>>> admin:~# nslookup mx.vcl.rimed.cu 192.168.159.162
>>>> Server: 192.168.159.162
>>>> Address: 192.168.159.162#53
>>>>
>>>> mx.vcl.rimed.cu canonical name = vclserver1.vcl.rimed.cu.
>>>> Name: vclserver1.vcl.rimed.cu
>>>> Address: 192.168.159.164
>>>>
>>>>
>>>> SIN PROBLEMA ALGUNO
>>>>
>>>> dns en la wan nueva
>>>> 192.168.161.182
>>>>
>>>> consultando dns
>>>> admin:~# nslookup mx.vcl.rimed.cu 192.168.161.182
>>>> Server: 192.168.161.182
>>>> Address: 192.168.161.182#53
>>>>
>>>> mx.vcl.rimed.cu canonical name = vclserver1.vcl.rimed.cu.
>>>> Name: vclserver1.vcl.rimed.cu
>>>> Address: 192.168.159.164
>>>>
>>>>
>>>> EN VEZ DE RESPONDER PARA LA WAN 161, RESPONDE NUEVAMENTE A LA WAN 159
>>>> he configurado las vistas
>>>>
>>>> vclserver:/etc/bind# cat named.conf.local
>>>> acl "lan" { 172.16.1.0/24; };
>>>> acl "servidores-lan" { 172.16.1.0/28; };
>>>> acl "servidores-wan" { 192.168.159.160/28; 192.168.161.176/28;
>>>> 200.55.156.165/32; 200.55.156.170/32; 192.168.159.181/32;
>>>> 192.168.159.114/32; };
>>>>
>>>> view "vlan" {
>>>> match-clients { lan; !any; };
>>>> allow-recursion { servidores-lan; };
>>>>
>>>> zone "vcl.rimed.cu" IN {
>>>> type master;
>>>> file "vcl.rimed.cu.lan.zone";
>>>> allow-transfer { 172.16.1.4; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>>
>>>> zone "1.16.172.in-addr.arpa" IN {
>>>> type master;
>>>> file "172.16.1.in-addr.arpa";
>>>> allow-transfer { 172.16.1.4; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>> #include "/etc/bind/subdominios";
>>>> };
>>>>
>>>> view "vwan" {
>>>> match-clients { any; !lan; };
>>>> allow-recursion { any; };
>>>>
>>>> zone "vcl.rimed.cu" IN {
>>>> type master;
>>>> file "vcl.rimed.cu.wan.zone";
>>>> allow-transfer { 192.168.159.164; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>>
>>>> zone "160/28.159.168.192.in-addr.arpa" IN {
>>>> type master;
>>>> file "192.168.159.in-addr.arpa";
>>>> allow-transfer { 192.168.159.164; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>> };
>>>>
>>>>
>>>> view "vwan2" {
>>>> match-clients { any; !lan; };
>>>> allow-recursion { any; };
>>>>
>>>> zone "vcl.rimed.cu" IN {
>>>> type master;
>>>> file "vcl.rimed.cu.wan2.zone";
>>>> allow-transfer { 192.168.161.184; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>>
>>>> zone "176/28.161.168.192.in-addr.arpa" IN {
>>>> type master;
>>>> file "192.168.161.in-addr.arpa";
>>>> allow-transfer { 192.168.161.184; };
>>>> allow-update { none; };
>>>> notify yes;
>>>> };
>>>> };
>> creo haber resuelto el problema ya
>>
>> vclserver:/etc/bind# nslookup mx.vcl.rimed.cu 172.16.1.2
>> Server: 172.16.1.2
>> Address: 172.16.1.2#53
>>
>> mx.vcl.rimed.cu canonical name = vclserver1.vcl.rimed.cu.
>> Name: vclserver1.vcl.rimed.cu
>> Address: 172.16.1.4
>>
>> vclserver:/etc/bind# nslookup mx.vcl.rimed.cu 192.168.159.162
>> Server: 192.168.159.162
>> Address: 192.168.159.162#53
>>
>> mx.vcl.rimed.cu canonical name = vclserver1.vcl.rimed.cu.
>> Name: vclserver1.vcl.rimed.cu
>> Address: 192.168.159.164
>>
>> vclserver:/etc/bind# nslookup mx.vcl.rimed.cu 192.168.161.182
>> Server: 192.168.161.182
>> Address: 192.168.161.182#53
>>
>> mx.vcl.rimed.cu canonical name = vclserver1.vcl.rimed.cu.
>> Name: vclserver1.vcl.rimed.cu
>> Address: 192.168.161.184
>>
>>
>> si preguntas por 172 responde 172
>> si lo haces por 159 responde 159
>> si lo haces por 161 responde por 161
>>
>> como me quedó el bind, muestro
>>
>> defini en el bind cada red por separado
>>
>> acl "lan" { 172.16.1.0/24; };
>> acl "wan" { 192.168.159.160/28; };
>> acl "wan2" { 192.168.161.176/28; };
>> acl "servidores-lan" { 172.16.1.0/28; };
>> acl "servidores-wan" { 192.168.159.160/28; 200.55.156.165/32;
>> 200.55.156.170/32; 192.168.159.181/32; 192.168.159.114/32; };
>> acl "servidores-wan2" { 192.168.161.176/28; 200.55.156.165/32;
>> 200.55.156.170/32; 192.168.159.181/32; 192.168.159.114/32; };
>>
>> view "vlan" {
>> match-clients { lan; !any; };
>> allow-recursion { servidores-lan; };
>>
>> zone "vcl.rimed.cu" IN {
>> type master;
>> file "vcl.rimed.cu.lan.zone";
>> allow-transfer { 172.16.1.4; };
>> allow-update { none; };
>> notify yes;
>> };
>>
>> zone "1.16.172.in-addr.arpa" IN {
>> type master;
>> file "172.16.1.in-addr.arpa";
>> allow-transfer { 172.16.1.4; };
>> allow-update { none; };
>> notify yes;
>> };
>> };
>>
>> view "vwan" {
>> match-clients { wan; !lan; !wan2; };
>> allow-recursion { servidores-wan; };
>>
>> zone "vcl.rimed.cu" IN {
>> type master;
>> file "vcl.rimed.cu.wan.zone";
>> allow-transfer { 192.168.159.164; };
>> allow-update { none; };
>> notify yes;
>> };
>>
>> zone "160/28.159.168.192.in-addr.arpa" IN {
>> type master;
>> file "192.168.159.in-addr.arpa";
>> allow-transfer { 192.168.159.164; };
>> allow-update { none; };
>> notify yes;
>> };
>>
>> };
>>
>> view "vwan2" {
>> match-clients { wan2; !lan; !wan; };
>> allow-recursion { servidores-wan2; };
>>
>> zone "vcl.rimed.cu" IN {
>> type master;
>> file "vcl.rimed.cu.wan2.zone";
>> allow-transfer { 192.168.161.184; };
>> allow-update { none; };
>> notify yes;
>> };
>>
>> zone "176/28.161.168.192.in-addr.arpa" IN {
>> type master;
>> file "192.168.161.in-addr.arpa";
>> allow-transfer { 192.168.161.184; };
>> allow-update { none; };
>> notify yes;
>> };
>>
>> };
>>
>>
> bueno, cuadno creí que ya todo estaba resuelto me encuentro que no
> resuelve por 127.0.0.1 por lo tanto toda la navegacion dice que no
> encuentra dns
>
con la ayuda de leer, y la de unos amigos ya tengo todo resuelto
me faltaban estas vistas locales en el bind dentro de cada zona y
terminé separando cada rango en una vista independiente
acl "lan" { 172.16.1.0/24; };
acl "wan" { 192.168.159.160/28; };
acl "wan2" { 192.168.161.176/28; };
acl "servidores-lan" { 172.16.1.0/28; };
acl "servidores-wan" { 192.168.159.160/28; 200.55.156.165/32;
200.55.156.170/32; 192.168.159.181/32; 192.168.159.114/32; };
acl "servidores-wan2" { 192.168.161.176/28; 200.55.156.165/32;
200.55.156.170/32; 192.168.159.181/32; 192.168.159.114/32; };
view "vlan" {
match-clients { lan; !any; };
allow-recursion { servidores-lan; };
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
zone "vcl.rimed.cu" IN {
type master;
file "vcl.rimed.cu.lan.zone";
allow-transfer { 172.16.1.4; };
allow-update { none; };
notify yes;
};
zone "1.16.172.in-addr.arpa" IN {
type master;
file "172.16.1.in-addr.arpa";
allow-transfer { 172.16.1.4; };
allow-update { none; };
notify yes;
};
#include "/etc/bind/subdominios";
};
view "vwan" {
match-clients { wan; !lan; !wan2; };
allow-recursion { servidores-wan; };
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
zone "vcl.rimed.cu" IN {
type master;
file "vcl.rimed.cu.wan.zone";
allow-transfer { 192.168.159.164; };
allow-update { none; };
notify yes;
};
zone "160/28.159.168.192.in-addr.arpa" IN {
type master;
file "192.168.159.in-addr.arpa";
allow-transfer { 192.168.159.164; };
allow-update { none; };
notify yes;
};
};
view "vwan2" {
match-clients { wan2; !lan; !wan; };
allow-recursion { servidores-wan2; };
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
zone "vcl.rimed.cu" IN {
type master;
file "vcl.rimed.cu.wan2.zone";
allow-transfer { 192.168.161.184; };
allow-update { none; };
notify yes;
};
zone "176/28.161.168.192.in-addr.arpa" IN {
type master;
file "192.168.161.in-addr.arpa";
allow-transfer { 192.168.161.184; };
allow-update { none; };
notify yes;
};
};
--
whilo
________________________________
Lic. Wilfredo Martínez Consuegra
Administrador de Red
RIMED Villa Clara
Ministerio de Educación
Phone: (53)(42) 20 1077
Jabber: [email protected]
--
Visite nuestra web en Internet
http://www.ispvc.rimed.cu
"50 Años de Educación en Revolución"
--
XI Encuentro Internacional de Economistas sobre Globalización y Problemas del
Desarrollo 2 al 6 de marzo de 2009
http://www.anec.cu/
--
Este mensaje ha sido analizado por MailScanner
en busca de virus y otros contenidos peligrosos,
y se considera que está limpio.
_______________________________________________
Cancelar suscripción
https://listas.softwarelibre.cu/mailman/listinfo/linux-l
Buscar en el archivo
http://listas.softwarelibre.cu/buscar/linux-l
