>Если честно времени нет со следующей недели отпуск ;-))
>А дел блин как всегда .... просмотр man named ничего не дал
>
такие отговорки выглядят гораздо оскорбительнее чем когда просто
на три буквы посылают, у них подтекст:
"вы тут ни хера не делаете, а меня дел по горло и некогда _плевые_
технологии изучать"
>кстати на ftp://rs.internic.net/domain не нашел root.cache
[unix1]~ > ftp ftp://rs.internic.net/domain/
Connected to rs.internic.net.
220-**********************************************************
220-***** *****
220-***** InterNIC Public FTP Server *****
220-***** *****
220-***** Login with username "anonymous" *****
220-***** You may change directories to the following: *****
220-***** *****
220-***** domain - Root Domain Zone Files *****
220-***** *****
220-***** Unauthorized access to this system may *****
220-***** result in criminal prosecution. *****
220-***** *****
220-***** All sessions established with this server are *****
220-***** monitored and logged. Disconnect now if you do *****
220-***** not consent to having your actions monitored *****
220-***** and logged. *****
220-***** *****
220-**********************************************************
220-
220 FTP server ready.
331 Guest login ok, send your complete e-mail address as password.
230 User ftp logged in. Access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Type set to I.
250 CWD command successful.
250 CWD command successful.
ftp> pass off
Passive mode off.
ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for directory listing.
total 632
-rw-r--r-- 1 9998 213 909 Jul 3 09:02 INTERNIC_ROOT_ZONE.signatures
-rw-r--r-- 1 9998 213 696 Jul 3 08:36 arpa.zone.gz
-rw-r--r-- 1 9998 213 75 Jul 3 09:02 arpa.zone.gz.md5
-rw-r--r-- 1 9998 213 72 Jul 3 09:02 arpa.zone.gz.sig
-rw-r--r-- 1 9998 213 176235 Jul 3 08:36 edu.zone.gz
-rw-r--r-- 1 9998 213 74 Jul 3 09:02 edu.zone.gz.md5
-rw-r--r-- 1 9998 213 72 Jul 3 09:02 edu.zone.gz.sig
-rw-r--r-- 1 9998 213 29798 Jul 3 08:36 gov.zone.gz
-rw-r--r-- 1 9998 213 74 Jul 3 09:02 gov.zone.gz.md5
-rw-r--r-- 1 9998 213 72 Jul 3 09:02 gov.zone.gz.sig
-rw-r--r-- 1 9998 213 1920 Jul 3 08:36 inaddr.zone.gz
-rw-r--r-- 1 9998 213 77 Jul 3 09:02 inaddr.zone.gz.md5
-rw-r--r-- 1 9998 213 72 Jul 3 09:02 inaddr.zone.gz.sig
-rw-r--r-- 1 9998 213 2769 Aug 1 2000 named.ca
-rw-r--r-- 1 9998 213 33 Jun 24 2001 named.ca.md5
-rw-r--r-- 1 9998 213 174 Jun 24 2001 named.ca.pgp
-rw-r--r-- 1 9998 213 2769 Aug 1 2000 named.cache
-rw-r--r-- 1 9998 213 33 Jun 24 2001 named.cache.md5
-rw-r--r-- 1 9998 213 174 Jun 24 2001 named.cache.pgp
-rw-r--r-- 1 9998 213 2769 Aug 1 2000 named.root
-rw-r--r-- 1 9998 213 33 Jun 24 2001 named.root.md5
-rw-r--r-- 1 9998 213 174 Jun 24 2001 named.root.pgp
-rw-r--r-- 1 9998 213 13999 Jul 3 08:36 root.zone.gz
-rw-r--r-- 1 9998 213 75 Jul 3 09:02 root.zone.gz.md5
-rw-r--r-- 1 9998 213 72 Jul 3 09:02 root.zone.gz.sig
226 Transfer complete.
ftp>
ftp> bye
[unix1]~ > date
среда, 3 июля 2002 г. 17:27:14 (MSD)
[unix1]~ >
FAQ:
<quote>
Question 2.19. What is the cache file
Date: Fri Dec 6 01:15:22 EST 1996
From the "Name Server Operations Guide"
6.3. Cache Initialization
6.3.1. root.cache
The name server needs to know the servers that
are the authoritative name servers for the root
domain of the network. To do this we have to prime
the name server's cache with the addresses of these
higher authorities. The location of this file is
specified in the boot file. ...
-----------------------------------------------------------------------------
Question 2.20. Obtaining the latest cache file
Date: Fri Dec 6 01:15:22 EST 1996
If you have a version of dig running, you may obtain the information with
the command
dig @a.root-servers.net. . ns
A perl script to handle some possible problems when using this method
from behind a firewall and that can also be used to periodically obtain
the latest cache file was posted to comp.protocols.tcp-ip.domains during
early October, 1996. It was posted with the subject "Keeping db.cache
current". It is available at
http://www.intac.com/~cdp/cptd-faq/current_db_cache.txt.
The latest cache file may also be obtained from the InterNIC via ftp or
gopher:
; 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
-----------------------------------------------------------------------------
Question 2.21. Selecting a nameserver/root cache
Date: Mon Aug 5 22:54:11 EDT 1996
Exactly how is the a root server selected from the root cache? Does the
resolver attempt to pick the closest host or is it random or is it via
sortlist-type workings? If the root server selected is not available (for
whatever reason), will the the query fail instead of attempting another
root server in the list ?
Every recursive BIND name server (that is, one which is willing to go out
and find something for you if you ask it something it doesn't know) will
remember the measured round trip time to each server it sends queries to.
If it has a choice of several servers for some domain (like "." for
example) it will use the one whose measured RTT is lowest.
Since the measured RTT of all NS RRs starts at zero (0), every one gets
tried one time. Once all have responded, all RTT's will be nonzero, and
the "fastest server" will get all queries henceforth, until it slows down
for some reason.
To promote dispersion and good record keeping, BIND will penalize the RTT
by a little bit each time a server is reused, and it will penalize the RTT
a _lot_ if it ever has to retransmit a query. For a server to stay "#1",
it has to keep on answering quickly and consistently.
Note that this is something BIND does that the DNS Specification does not
mention at all. So other servers, those not based on BIND, might behave
very differently.
на все это надо не больше 5'и минут чтобы дошло что то что хотелось
есть одно и тоже, важно только правильно конфиги прописать, с умом
а не передирая их не перенося один к одному с одного сервера на другой
для совершенно разных целей.
Токо без обид, ибо сегодня прям нонсенс какой-то - ну не хотим мы
знать технологии, чисто M$ подход - передрать, запустить - а там
посмотрим что выйдет...