question about resolution

Chris sdqfsd at qdvqsd.cv
Wed May 25 06:35:28 UTC 2005


Ok thanks both


"Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
news:d70if3$355$1 at sf1.isc.org...
> I seem to recall that BIND 8 complained when the real root server
> information differed from what was in the hints file (see item #421 in
> the BIND 8 "CHANGES" file: "warn when the root hints do not match
> reality"), but I haven't seen any error messages to that effect for a
> while, so I guess folks found that too annoying and for BIND 9 they
> removed that error message.
>
> I suppose you could run a script periodically that would validate your
> hints file against what the root servers are actually returning, or
> against the "official" hints file available via anonymous FTP from
> ftp.internic.net (pathname /domain/db.cache).
>
>
>                                                          - Kevin
>
> Chris wrote:
>
> >Hi Kevin,
> >
> >Thanks for replying.
> >
> >May i resume the operation because there is one thing i still don't
> >understand:
> >
> >first, the local name server checks its zone db file to determine whether
it
> >contains the name www.skynet.be .
> >Second, if not found, the local name server passes the query to one of
the
> >DNS root servers, which sends back a referral to the "be" name server.
> >
> >My question:
> >How does the local name server passe the query to one of the DNS root
> >servers? I know there is a file "cache.dns" but where come that
information
> >from, and, suppose the IP of one of those root servers changes, how can
the
> >local name server be awared of it?
> >
> >Thanks
> >
> >"Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
> >news:d6tp69$2qug$1 at sf1.isc.org...
> >
> >
> >>Chris wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>Suppose the DNS-server of domain mydomain.xy and it receives a request
> >>>
> >>>
> >for
> >
> >
> >>>example www.skynet.be.
> >>>
> >>>
> >>>
> >>It doesn't matter whether it's the "DNS-server of domain mydomain.xy" or
> >>not: the authoritative-nameserver and iterative-resolver roles are
> >>logically distinct. In fact, many authoritative nameservers don't do any
> >>iterative resolution at all (and this is actually the recommended way to
> >>run authoritative nameservers).
> >>
> >>
> >>
> >>>What will it do to resolve that address, or with other words, how can
> >>>
> >>>
> >that
> >
> >
> >>>DNS-server know the IP of the Toplevelservers (like .us, .com, .be ..)?
> >>>
> >>>
> >>>
> >>Typically, an iterative resolver is configured with a "hints" file that
> >>it consults on startup in order to fetch the root-nameserver
> >>information. Once it has the root-nameserver information, it can resolve
> >>anything else in the namespace by working down the delegation tree.
> >>
> >>
> >>                                                         - Kevin
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >
> >
>
>
>




More information about the bind-users mailing list