DNS Publico

Salve galera.
Estou montando um servidor DNS para a empresa para fornecer hospedagem e também devo usar para server dns do provedor junto.
Tenho uma duvida. Criei um dominio no registro.br, tenho o bind rodando, e agora surge a duvida de para configurar esse dns é só colocar o ip do server dns no registro.br ou se também tenho que configurar algo em meu bind.

Agradeço a atenção.

Você deve configurar o seu bind, criar as zonas referentes ao seu dominio e setar os ip´s no registro.br lembrando que precisa ter pelo menos 2 ip´s válidos para registra esse dominio no registro.br e para isso precisa de um segundo servidor dns SLAVE, busque aqui no fórum tem muita coisa a respeito, mas é por ai.

Configurei meu named, porem quado mando o checkdns do registro.br acaba dando erro como "Dominio Desconhecido"

Abaixo esta meu named.conf

Código :

---

include "/etc/rndc.key";
 
controls {
        inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};
 
 
options
{
    /* make named use port 53 for the source of all queries, to allow
         * firewalls to block all ports except 53:
         */
    query-source    port 53;
 
    // Put files that named is allowed to write in the data/ directory:
    directory "/var/named"; // the default
    dump-file             "data/cache_dump.db";
    statistics-file     "data/named_stats.txt";
    memstatistics-file     "data/named_mem_stats.txt";
};
 
logging
{
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
 *      named will try to write the 'named.run' file in the $directory (/var/named).
 *      By default, SELinux policy does not allow named to modify the /var/named directory,
 *      so put the default debug log file in data/ :
 */
    channel default_debug {
            file "data/named.run";
            severity dynamic;
    };
};
 
 
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
 
view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
 * If all you want is a caching-only nameserver, then you need only define this view:
 */
    match-clients         { localhost; };
    match-destinations    { localhost; };
    recursion yes;
 
    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };
 
[B]   zone "rn1.com.br" IN {
    type master;
    file "db/rn1.com.br";
    };
 
    zone "xxx.xxx.201.in-addr.arpa" IN {
    type master;
    file "db/rn1.rev";
    };[/B]
 
    /* these are zones that contain definitions for all the localhost
     * names and addresses, as recommended in RFC1912 - these names should
     * ONLY be served to localhost clients:
     */
    include "/var/named/named.rfc1912.zones";
};
 
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
   that connect via your directly attached LAN interfaces - "localnets" .
 */
    match-clients        { localnets; };
    match-destinations    { localnets; };
    recursion yes;
 
    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };
 
    // include "/var/named/named.rfc1912.zones";
    // you should not serve your rfc1912 names to non-localhost clients.
 
    // These are your "authoritative" internal zones, and would probably
    // also be included in the "localhost_resolver" view above :
};
 
view    "external"
{
/* This view will contain zones you want to serve only to "external" clients
 * that have addresses that are not on your directly attached LAN interface subnets:
 */
 
    recursion no;
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers
 
    // all views must contain the root hints zone:
    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };
 
    // These are your "authoritative" external zones, and would probably
    // contain entries for just your web and mail servers:
 
    // BEGIN external zone entries

---

Agora segue meu rn1.com.br que é o arquivo de configuração do dominio.

Código :

---

$TTL 43200
@       IN      SOA     ns1.rn1.com.br. hostmaster.rn1.com.br.(
      2008061645 3H 15M 1W 1D)
@       IN      NS              ns1.rn1.com.br
@       IN      NS              ns2.rn1.com.br
@       IN      MX      10      mail.rn1.com.br
 
ns1            IN       A       201.70.170.225
ns2            iN       A       201.70.170.226
rn1.com.br.    IN       A       201.70.170.228
www            IN       A       66.228.120.140

---

Alguem poderia me dizer como resolver isso?

Abração

Problema resolvido!