Ya reinicie el bind como 15 veces y tambien reinicie
rep-mgr.local.domain.com (192.168.1.30), este es el resultado de nslookup:
1) Seteando el servidor a 192.168.1.2 (por si acaso)
[root@rep-mgr ~]# nslookup
> server 192.168.1.2
Default server: 192.168.1.2
Address: 192.168.1.2#53
> rep-mgr.local.domain.com
Server: 192.168.1.2
Address: 192.168.1.2#53
** server can't find rep-mgr.local.domain.com: NXDOMAIN
>
2) Por defecto
[root@rep-mgr ~]# nslookup
> rep-mgr.local.domain.com
Server: 192.168.1.2
Address: 192.168.1.2#53
** server can't find rep-mgr.local.domain.com: NXDOMAIN
>
Ing. Reynier Pérez Mira
Cel: +58 424.180.5609 / +58 416.921.7406
Correo: reynie...@gmail.com / reynie...@hotmail.com
2011/12/27 Miguel González Castaños <miguel_3_gonza...@yahoo.es>
> Reinicia el servicio de bind y de red. De todas maneras porque no
> ejecutas nslookup?
>
> Miguel
>
>
>
> On 27/12/2011 14:03, reynie...@gmail.com wrote:
>
> Hola Miguel, le puse un comentario a esa linea o sea a nameserver
> 10.13.0.3 e igual me sigue apuntando a los mismos servidores :-( (una
> pregunta: debo reiniciar algun servicio para que tome los cambios o
> simplemente con poner un comentario #nameserver 10.13.0.3 basta?) Lo de
> rep-mgr.soltiven.com fue un error mio en realidad el dig lo hice a:
>
> [root@rep-mgr bacula]# dig rep-mgr.local.domain.com
>
> ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.1 <<>>
> rep-mgr.local.domain .com
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39916
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;rep-mgr.local.domain .com. IN A
>
> ;; AUTHORITY SECTION:
> com. 5 IN SOA a.gtld-servers.net.
> nstld.verisign-grs.com. 1324990335 1800 900 604800 411
>
> ;; Query time: 2 msec
> ;; SERVER: 192.168.1.2#53(192.168.1.2)
> ;; WHEN: Tue Dec 27 08:31:12 2011
> ;; MSG SIZE rcvd: 111
>
> Sigo sin entender que sucede porque ya he buscado por Google y he
> probado cuanta solucion a dado la gente :-(
>
> Saludos
>
> Ing. Reynier Pérez Mira
> Cel: +58 424.180.5609 / +58 416.921.7406
> Correo: reynie...@gmail.com / reynie...@hotmail.com
>
>
>
> 2011/12/27 Miguel González Castaños <miguel_3_gonza...@yahoo.es>
>
>> El hecho de que en /etc/resolv.conf tengas la entrada
>>
>> nameserver 10.13.0.3
>>
>> probablemente este reenviando la peticion de DNS al servidor de DNS que
>> tienes en la maquina host donde instalaste VMware.
>>
>> Si quitas esa linea podrás mandar la resolución local, pero solo
>> resolveras localdomain. El dominio soltiven.com no lo tienes en tu DNS
>> local. Por eso cuando pides que resuelva, reenvia la peticion al servidor
>> de DNS 10.13.0.3
>>
>> Si quieres que rep-mgr.soltiven.com te resuelva a rep-mgr.localdomain,
>> tendrás que añadir una entrada en /etc/hosts o en el servidor de DNS local.
>>
>> Miguel
>>
>>
>>
>> On 27/12/2011 13:48, reynie...@gmail.com wrote:
>>
>>> Hola a todos, estoy tratando de configurar un DNS para hacer pruebas
>>> pero
>>> debo estar haciendo algo mal porque no me resuelve bien los NS. Tengo dos
>>> VM dentro de Vmware Workstation y cada una de ellas tiene dos interfaces
>>> de
>>> red: eth0 (que tiene la misma subred que mi tarjeta fisica, la de mi
>>> compturadora o sea la 10.13.13.x) y eth1 (que es un NAT para que las VM
>>> se
>>> vean entre ellas cuya subred es 192.168.1.x). La VM que finge como DNS
>>> tiene IP 192.168.1.2 y este es el named.conf:
>>>
>>> options {
>>> listen-on port 53 { 192.168.1.2; };
>>> listen-on-v6 port 53 { ::1; };
>>> directory "/var/named";
>>> dump-file "/var/named/data/cache_dump.db";
>>> statistics-file "/var/named/data/named_stats.txt";
>>> memstatistics-file "/var/named/data/named_mem_stats.txt";
>>> recursion yes;
>>> };
>>>
>>> logging {
>>> channel default_debug {
>>> file "data/named.run";
>>> severity dynamic;
>>> };
>>> };
>>>
>>> zone "." IN {
>>> type hint;
>>> file "named.ca";
>>> };
>>>
>>> zone "local.domain.com" {
>>> type master;
>>> file "/var/named/local.domain.com.hosts";
>>> };
>>>
>>> Y el fichero local.domain.com.hosts contiene lo siguiente:
>>>
>>> $ttl 38400
>>> local.domain.com. IN SOA ns.local.domain.com.
>>> ad...@local.domain.com. (
>>> 1324940087
>>> 10800
>>> 3600
>>> 604800
>>> 38400 )
>>> local.domain.com. IN NS ns.local.domain.com.
>>> rep-mgr.local.domain .com. IN A 192.168.1.30
>>> squid.local.domain .com. IN A 192.168.1.10
>>> ns.local.domain .com. IN A 192.168.1.2
>>> bacula.local.domain .com. IN CNAME rep-mgr
>>>
>>> Todo esta correctamente configurado porque el DNS (Bind) inicia
>>> correctamente. Ahora bien el tema esta en que si desde la VM
>>> rep-mgr.local.domain.com hago un
>>>
>>> [root@rep-mgr bacula]# dig rep-mgr.soltiven.com
>>>
>>> ;<<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.1<<>> rep-mgr.soltiven.com
>>> ;; global options: +cmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48443
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>>>
>>> ;; QUESTION SECTION:
>>> ;rep-mgr.soltiven.com. IN A
>>>
>>> ;; AUTHORITY SECTION:
>>> com. 5 IN SOA a.gtld-servers.net.
>>> nstld.verisign-grs.com. 1324989377 1800 900 604800 612
>>>
>>> ;; Query time: 1 msec
>>> ;; SERVER: 192.168.1.2#53(192.168.1.2)
>>> ;; WHEN: Tue Dec 27 08:11:50 2011
>>> ;; MSG SIZE rcvd: 111
>>>
>>> Me responden unos servidores a.gtld-servers.net. nstld.verisign-grs.com.
>>> que no se de donde salen. El fichero /etc/hosts de ese servidor tiene
>>> esto:
>>> 127.0.0.1 localhost localhost.localdomain localhost4
>>> localhost4.localdomain4
>>> ::1 localhost localhost.localdomain localhost6
>>> localhost6.localdomain6
>>> 192.168.1.2 ns.local.domain.com
>>>
>>> Y el fichero /etc/resolv.conf
>>> domain local.domain.com
>>> search local.domain.com
>>> nameserver 192.168.1.2
>>> nameserver 10.13.0.3
>>>
>>> Donde esta el error? Alguna ayuda?
>>> Saludos y gracias por adelantado
>>>
>>> Ing. Reynier Pérez Mira
>>> Cel: +58 424.180.5609 <%2B58%20424.180.5609> / +58
>>> 416.921.7406<%2B58%20416.921.7406>
>>> Correo: reynie...@gmail.com / reynie...@hotmail.com
>>> _______________________________________________
>>> CentOS-es mailing list
>>> CentOS-es@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos-es
>>>
>>>
>>
>> This message and any attachments are intended for the use of the
>> addressee or addressees only. The unauthorised disclosure, use,
>> dissemination or copying (either in whole or in part) of its content is not
>> permitted. If you received this message in error, please notify the sender
>> and delete it from your system. Emails can be altered and their integrity
>> cannot be guaranteed by the sender.
>>
>> Please consider the environment before printing this email.
>>
>>
>
> This message and any attachments are intended for the use of the addressee or
> addressees only. The unauthorised disclosure, use, dissemination or copying
> (either in whole or in part) of its content is not permitted. If you received
> this message in error, please notify the sender and delete it from your
> system. Emails can be altered and their integrity cannot be guaranteed by the
> sender.
>
> Please consider the environment before printing this email.
>
>
_______________________________________________
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es
