Problems resolution names.

[Rafael Cruz M.]

oooppppssss..... where can I check it ???

I just have configured this ...

#####################################################################
options {
                  directory  "/var/named";
                  pid-file   "/var/named/named.pid";
                  named-xfer "/usr/sbin/named-xfer";

                  transfers-in     10;
                  forward only;
                  fake-iquery yes;
                  pollfd-chunk-size 20;

        //#ident "@(#)cmd-inet:var/named/named.boot 1.2"
        //
        //boot file for name server
        //
        //type domain source file or host
        //

};


zone "cetro-crece.org.mx" in {
        type master;
        file "/var/named/named.db";
};

 zone "0.0.127.in-addr.arpa" in {
        type master;
        file "/var/named/named.local";
};

 zone "147.38.200.in-addr.arpa" in {
        type master;
        file "/var/named/200.38.147.rev";
};

 zone "." in {
        type hint;
        file "/var/named/named.ca";
};

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

And the named.ca  file I got this

##########################################################33

;
;       This file holds the information on root name servers needed to
;       initialize cache of Internet domain name servers
;       e.g. reference this file in the cache    file
;       configuration file of BIND domain name servers.
;
;       This file is made available by InterNIC registration services
;       under anonymous FTP as
;           file                /domain/named.root
;           on server           FTP.RS.INTERNIC.NET
;       -OR- under Gopher at    RS.INTERNIC.NET
;           under menu          InterNIC Registration Services NSI
;              submenu          InterNIC Registration Archives
;           file                named.root
;
;       last update:    Nov 8, 1995
;       related version of root zone:   1995110800
;
;
; formerly NS.INTERNIC.NET
;
.                        3600000  IN  NS    A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET.      3600000      A     198.41.0.4
;
; formerly NS1.ISI.EDU
;
.                        3600000      NS    B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET.      3600000      A     128.9.0.107
;
; formerly C.PSI.NET
;
.                        3600000      NS    C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET.      3600000      A     192.33.4.12
;
; formerly TERP.UMD.EDU
;
.                        3600000      NS    D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET.      3600000      A     128.8.10.90
;
; formerly NS.NASA.GOV
;
.                        3600000      NS    E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET.      3600000      A     192.203.230.10
;
; formerly NS.ISC.ORG
;
.                        3600000      NS    F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET.      3600000      A     192.5.5.241
;
; formerly NS.NIC.DDN.MIL
;
.                        3600000      NS    G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET.      3600000      A     192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
.                        3600000      NS    H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET.      3600000      A     128.63.2.53
;
; formerly NIC.NORDU.NET
;
.                        3600000      NS    I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET.      3600000      A     192.36.148.17
; End of File

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

Thanks for your help !!!!!

Kevin sorry for dont send a copy of this previously



Joseph S D Yao wrote:

> On Tue, Sep 12, 2000 at 04:30:16PM -0500, Rafael Cruz M. wrote:
> > I have configured a BIND 8.1.2 and when I execute or restart the daemon
> > named the console of the server just send a message that is ready to resolv
> > names, but I have some problems because it don't resolve some domains that
> > belong to another ISP.
> >
> > What do you recomend me ???
>
> Do you have the root servers configured into a "hints" zone?
>
> --
> Joe Yao                         jsdy at cospo.osis.gov - Joseph S. D. Yao
> COSPO/OSIS Computer Support                                     EMT-B
> -----------------------------------------------------------------------
> This message is not an official statement of COSPO policies.