+ Responder ao Tópico



  1. #1

    Padrão DNS NO Fedora 1

    Olá pessoal estou com muitas dificuldades pra configurar um servidor dns pra testes!!!

    qdo executo service named start ele da a mensgem [OK] porem nao funciona

    qdo executo o comando
    named -g ele dá a seguinte mensagem:

    [[email protected] named]# named -g
    May 21 13:31:15.603 starting BIND 9.2.2-P3 -g
    May 21 13:31:15.605 using 1 CPU
    May 21 13:31:15.612 loading configuration from '/etc/named.conf'
    May 21 13:31:15.650 no IPv6 interfaces found
    May 21 13:31:15.651 listening on IPv4 interface lo, 127.0.0.1#53
    May 21 13:31:15.653 binding TCP socket: address in use
    May 21 13:31:15.653 listening on IPv4 interface eth0, 192.168.0.1#53
    May 21 13:31:15.654 binding TCP socket: address in use
    May 21 13:31:15.661 /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: address in use
    May 21 13:31:15.662 ignoring config file logging statement due to -g option
    May 21 13:31:15.663 couldn't open pid file '/var/run/named/named.pid': Permission denied
    May 21 13:31:15.663 exiting (due to early fatal error)
    [[email protected] named]#

    já dei permisao de execucao na pasta chmod -R 755 /var/run/named/
    mas tb nao funcionou!!!pq ele está dando essa mensagem de erro???

    aki está o log /var/log/messages

    May 21 13:38:20 laboratorio named: início de named succeeded
    May 21 12:38:20 laboratorio named[2797]: starting BIND 9.2.2-P3 -u named -t /var/named/chroot
    May 21 12:38:20 laboratorio named[2797]: using 1 CPU
    May 21 12:38:21 laboratorio named[2797]: loading configuration from '/etc/named.conf'
    May 21 12:38:21 laboratorio named[2797]: no IPv6 interfaces found
    May 21 12:38:21 laboratorio named[2797]: listening on IPv4 interface lo, 127.0.0.1#53
    May 21 12:38:21 laboratorio named[2797]: listening on IPv4 interface eth0, 192.168.0.1#53
    May 21 12:38:21 laboratorio named[2797]: command channel listening on 127.0.0.1#953
    May 21 12:38:21 laboratorio named[2797]: running

    aki está as configuracoes de alguns arquivos

    [[email protected] root]# rpm -qa | grep bind
    bind-9.2.2.P3-9
    ypbind-1.12-3
    bind-utils-9.2.2.P3-9
    redhat-config-bind-2.0.0-18
    bind-chroot-9.2.2.P3-9
    [[email protected] root]#


    [[email protected] root]# cat /etc/host.conf
    order hosts,bind
    [[email protected] root]#


    [[email protected] root]# cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1 laboratorio.com.br laboratorio localhost.localdomain localhost
    192.168.0.1 laboratorio.alcimar.com.br alcimar.com.br
    [[email protected] root]#

    [[email protected] root]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
    # VIA Technologies|VT6105 [Rhine-III]
    DEVICE=eth0
    BOOTPROTO=static
    BROADCAST=192.168.0.255
    HWADDR=00:E0:7D:F2:BA8
    IPADDR=192.168.0.1
    NETMASK=255.255.255.0
    NETWORK=192.168.0.0
    ONBOOT=yes
    TYPE=Ethernet
    [[email protected] root]#

    aki está os arquivos do named todos em /var/named/ com execao do named.conf que está em /etc/named.conf

    named.conf

    // generated by named-bootconf.pl

    options {
    directory "/var/named";
    /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below. Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
    // query-source address * port 53;
    };

    //
    // a caching only nameserver config
    //
    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };
    zone "." IN {
    type hint;
    file "named.ca";
    };

    zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

    zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };

    zone "alcimar.com.br" IN {
    type master;
    file "alcimar.com.br";
    allow-update { none; };
    };

    zone "0.168.192.in-addr.arpa" IN {
    type master;
    file "alcimar.com.br.rev";
    allow-update { none; };
    };

    include "/etc/rndc.key";

    aki esta o /var/named/alcimar.com.br

    $TTL 86400
    $ORIGIN alcimar.com.br.
    @ 1D IN SOA laboratorio.alcimar.com.br. root.alcimar.com.br (
    42 ; serial (d. adams)
    3H ; refresh
    15M ; retry
    1W ; expiry
    1D ) ; minimum

    1D IN NS laboratorio.alcimar.com.br
    1D IN A 192.168.0.1
    laboratorio.com.br IN A 192.168.0.1
    www IN CNAME laboratorio

    aki está o /var/named/alcimar.com.br.rev

    $TTL 86400
    $ORIGIN 0.168.192.in-addr.arpa.
    @ IN SOA laboratorio.alcimar.com.br. root.alcimar.com.br. (
    1997022700 ; Serial
    28800 ; Refresh
    14400 ; Retry
    3600000 ; Expire
    86400 ) ; Minimum
    IN NS laboratorio.com.br.


    aki está o /var/named/localhost.zone

    $TTL 86400
    $ORIGIN localhost.
    @ 1D IN SOA @ root (
    42 ; serial (d. adams)
    3H ; refresh
    15M ; retry
    1W ; expiry
    1D ) ; minimum

    1D IN NS @
    1D IN A 127.0.0.1

    aki está o /var/named/named.conf

    $TTL 86400
    @ IN SOA localhost. root.localhost. (
    1997022700 ; Serial
    28800 ; Refresh
    14400 ; Retry
    3600000 ; Expire
    86400 ) ; Minimum
    IN NS localhost.

    1 IN PTR localhost.



    o estou fazendo de errado???se alguem puder me ajudar agradeço mto!!!!
    ah estou usando Fedora core 1

  2. #2
    Visitante

    Padrão DNS NO Fedora 1

    Ai pessoal estou precisando mto de ajuda!!!



  3. #3

    Padrão DNS NO Fedora 1

    Ai pessoal me de uma força!!!

    ainda tentei de tudo mas ainda estou com este problema!!!
    :toim:

  4. #4
    Visitante

    Padrão DNS NO Fedora 1

    KRA to com o mesmo problema so ke no fc-2

    ja resolvi uma vez mas fazeno um monte de coisa o problema mesmo ningguem conseguiu descobri ...



  5. #5
    fpmazzi
    Visitante

    Padrão DNS NO Fedora 1

    OPS erro meu ....

    eskeci de logar, a msg acima foi minha ....

    rs ...

    valew se alguem souber o motivo por favor nos envie ...

  6. #6

    Padrão DNS NO Fedora 1

    Já viu as permissões do diretorio onde o pid é guardado pode ser apenas isso, no slackware temos problemas parecidos quando se instala o mysql pela primeira vez.



  7. #7
    fpmazzi
    Visitante

    Padrão DNS NO Fedora 1

    cra ja vi sim, dei chmod 777 para todo mundo e nao resolveu..

  8. #8

    Padrão DNS NO Fedora 1

    É pessoal tá difícil
    mas não vou desistir!!! :cry:

    Formatei e reinstalei o Fedora Core 1 novamente, mas os erros continuam!!!
    segue aki os erros apresenteados:


    [[email protected] root]# service named status
    rndc: connect failed: connection refused
    [[email protected] root]# service named stop
    Parando o named: rndc: connect failed: connection refused
    [FALHOU]
    [[email protected] root]# service named start
    Iniciando named: [ OK ]
    [[email protected] root]# service named status
    rndc: connect failed: connection refused
    [[email protected] root]#
    [[email protected] root]# tail -f /var/log/m
    maillog messages
    [[email protected] root]# tail -f /var/log/messages
    Jun 1 10:39:13 laboratorio gconfd (root-3475): Endereço "xml:readwrite:/root/.gconf" resolvido para uma fonte de configuração com permissões de escrita na posição 1
    Jun 1 10:39:13 laboratorio gconfd (root-3475): Endereço "xml:readonly:/etc/gconf/gconf.xml.defaults" resolvido para uma fonte de configuração somente para leitura na posição 2
    Jun 1 10:39:41 laboratorio named: desligar named failed
    Jun 1 09:39:45 laboratorio named[3541]: starting BIND 9.2.2-P3 -u named -t /var/named/chroot
    Jun 1 09:39:45 laboratorio named[3541]: using 1 CPU
    Jun 1 09:39:45 laboratorio named[3541]: loading configuration from '/etc/named.conf'
    Jun 1 10:39:45 laboratorio named: início de named succeeded
    Jun 1 09:39:45 laboratorio named[3541]: /etc/named.conf:41: missing ';' before 'allow-update'
    Jun 1 09:39:45 laboratorio named[3541]: loading configuration: failure
    Jun 1 09:39:45 laboratorio named[3541]: exiting (due to fatal error)

    [[email protected] root]# named -g
    Jun 01 10:41:00.582 starting BIND 9.2.2-P3 -g
    Jun 01 10:41:00.583 using 1 CPU
    Jun 01 10:41:00.587 loading configuration from '/etc/named.conf'
    Jun 01 10:41:00.615 /etc/named.conf:41: missing ';' before 'allow-update'
    Jun 01 10:41:00.615 loading configuration: failure
    Jun 01 10:41:00.615 exiting (due to fatal error)
    [[email protected] root]#

    por que está dando esses erros???

    Obs o bind esta rodando em chroot!!!!

    segue arquivos de configuracao:

    named.conf

    // generated by named-bootconf.pl

    options {
    directory "/var/named";
    /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below. Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
    // query-source address * port 53;
    };

    //
    // a caching only nameserver config
    //
    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };
    zone "." IN {
    type hint;
    file "named.ca";
    };

    zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

    zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };

    zone "thelast.com.br" IN {
    type master;
    file "thelast.com.br"
    allow-update { none; };
    };

    zone "0.168.192.in-addr.arpa" IN {
    type master;
    file "0.168.192";
    allow-update { none; };
    };
    include "/etc/rndc.key";
    ####################################
    named.local

    $TTL 86400
    @ IN SOA localhost. root.localhost. (
    1997022700 ; Serial
    28800 ; Refresh
    14400 ; Retry
    3600000 ; Expire
    86400 ) ; Minimum
    IN NS localhost.

    1 IN PTR localhost.

    ###############################
    localhost.zone

    $TTL 86400
    $ORIGIN localhost.
    @ 1D IN SOA @ root (
    42 ; serial (d. adams)
    3H ; refresh
    15M ; retry
    1W ; expiry
    1D ) ; minimum

    1D IN NS @
    1D IN A 127.0.0.1
    #############################################
    thelast.com.br

    $TTL 86400
    @ IN SOA laboratorio.thelast.com.br. root.thelast.com.br. (
    2004101101 ; Serial
    28800 ; Refresh
    14400 ; Retry
    3600000 ; Expire
    86400 ) ; Minimum
    ;
    www IN CNAME laboratorio
    fp IN CNAME laboratorio
    pop IN CNAME laboratorio
    smtp IN CNAME laboratorio
    @ IN MX 5 laboratorio.thelast.com.br.
    @ IN NS 10
    laboratorio IN A 192.168.0.1

    ##############################################

    0.168.192

    $TTL 86400
    @ IN SOA laboratorio.thelast.com.br. root.thelast.com.br. (
    2004101101 ; Serial
    28800 ; Refresh
    14400 ; Retry
    3600000 ; Expire
    86400 ) ; Minimum
    @ IN NS laboratoio.thelast.com.br.

    1 IN PTR localhost.
    #############################################
    resolv.conf

    search thelast.com.br
    nameserver 192.168.0.1

    #######################################
    rndc.conf

    /*
    * Copyright (C) 2000, 2001 Internet Software Consortium.
    *
    * Permission to use, copy, modify, and distribute this software for any
    * purpose with or without fee is hereby granted, provided that the above
    * copyright notice and this permission notice appear in all copies.
    *
    * THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM
    * DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
    * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
    * INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,
    * INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
    * FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
    * NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
    * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
    */

    /* $Id: rndc.conf,v 1.7 2001/01/09 21:40:45 bwelling Exp $ */

    /*
    * Sample rndc configuration file.
    */

    options {
    default-server localhost;
    default-key "rndckey";
    };

    server localhost {
    key "rndckey";
    };

    include "/etc/rndc.key";

    ###############################################
    rndc.key

    key "rndckey" {
    algorithm hmac-md5;
    secret "YMJSt2YEg0RFcNRk8I3V9oH3HjuujvqNqNM2aBpiWXQtXBCVrr7ZCCLuO6Bu";
    };

    ##############################################

    Obs: Os arquivos named.local; localhost.zone; thelast.com.br; 0.168.192 estão no diretorio /var/named/chroot/var/named/
    E os arquivos named.conf; rndc.conf e rndc.key estão no diretorio /var/named/chroot/etc/

    Quer puder dar uma força ai agredeço pois já faz quase um mes que tentando configurar isto mas ainda nao consegui!!!



  9. #9
    Super_Diaulas
    Visitante

    Padrão DNS NO Fedora 1

    Jun 01 10:41:00.587 loading configuration from '/etc/named.conf'
    Jun 01 10:41:00.615 /etc/named.conf:41: missing ';' before 'allow-update'
    Jun 01 10:41:00.615 loading configuration: failure
    Jun 01 10:41:00.615 exiting (due to fatal error)

    Pode ver que está faltando ; no seu arquivo named.conf
    antes do item allw-update

    corrige isso e posta aqui de novo

  10. #10
    robsonzornitta
    Visitante

    Padrão eh o seguinte!!

    pelo que eu vih ai em cima nos arquivos tah faltandu o allow-update e tambem definir a "key" que consta no arquivo rndc.key no named.conf

    fai o seguinte posta pra mim aqui:

    faixa de ip, dominio a ser criadu pra teste, e apelidos como www ftp etc.

    pra mim montar os arquivos de exemplos pra queim tiver cum duvidas!!!
    :good:



  11. #11
    fpmazzi
    Visitante

    Padrão DNS NO Fedora 1

    Citação Postado originalmente por thelast
    zone "thelast.com.br" IN {
    type master;
    file "thelast.com.br"
    allow-update { none; };
    };
    no item onde indica o file esta faltando um ; apos o nome do arquivo.

    abraços....

  12. #12
    fpmazzi
    Visitante

    Padrão DNS NO Fedora 1

    OBS MOÇADA.: moçada eu percebi ke muita gente ta tendo este tipo de problema, inclusive eu, aki em ksa depois de muita luta resolvi, nao sei como, pq volto o a funfar o BIND do nada, sera ke nao eh prob. do BIND ou do FC-x

    ?????

    :toim: :toim: :tiro: