📄 00000012.htm
字号:
underscore) characters are not legal. Note that hostnames include the owners of A and MX records and .in-addr.arpa <BR>PTR records, and the data fields of MX and .in-addr.arpa PTR records: in other words, almost all currently used DNS <BR>entries! The current releases of the BIND name server software enforce these restrictions. 20-Nov-1997, 10-Apr-1996 <BR> <BR>Checking if a domain is registered already <BR> <BR>Based on a question by Plato <<A HREF="mailto:gking@GroupZ.net>">gking@GroupZ.net></A> <BR> <BR>To check if a domain has been registered, there are a couple of approaches. <BR> <BR>Brute force search of DNS zone file <BR> If the relevant zone file corresponding to the domain can be obtained, standard text searching tools can be used to <BR> check the file for the domain or variants. This procedure is flexible and quick once the file has been obtained since <BR> it is performed off line. The zones ARPA, COM, EDU, GOV, INADDR.ARPA, MIL, NET, and ORG are available at <BR> the InterNIC. Other zones may be available via ftp, but will usually need to be downloaded using the zone transfer <BR> mechanism of DNS. If a server is configured to disallow zone transfers, it may not be possible to easily obtain a <BR> copy of the zone file. <BR>WHOIS lookups <BR> If the domain being sought is in one of the InterNIC maintained zones, information about the domain will be stored <BR> in the InterNIC WHOIS database. A standard whois client can be used to query this database, currently located at <BR> rs.internic.net. In the absence of a client, rs.internic.net also offers telnet access to the database. For some <BR> domains, information is kept in WHOIS-like services like RWHOIS or in domain-specific WHOIS registries. <BR>Checking the DNS <BR> Using DNS query tools like dig or nslookup with query types NS, MX or A, information about the existence of a <BR> domain name can be obtained. This is the most general method, although it requires an exact guess to be made <BR> both of the type of records associated with the domain name and the name itself. Using a query type ANY can <BR> sometimes be effective, but can also result in misleading answers. <BR> <BR>Setting up a resolver <BR> <BR>Based on a question by Aidan N.R. Low <<A HREF="mailto:aidan@MIT.EDU>">aidan@MIT.EDU></A> <BR> <BR>Setting up the client side of DNS depends on the operating environment of the client. For a Unix machine, the resolver is <BR>configured through a text file, usually /etc/resolv.conf which commonly contains the IP address of the name server or <BR>servers which will be used to do the actual work. An adequate resolv.conf file contains just the one line <BR> <BR>nameserver x.y.z.w <BR> <BR>where x.y.z.w is the IP address of a suitable name server. Often this will be a server provided by the Internet service <BR>provider. It is a bad idea to point resolvers to name servers controlled by organisations with which there is no <BR>organisational relationship: the name server could be configured to return bogus information, especially if permission was <BR>not sought first for using the server. <BR> <BR>For PC type resolvers there is usually a network configuration option which specifies the same information as resolv.conf. <BR>Each network stack tends to have its own set of configuration information. However, on MacOS, there are moves towards <BR>central network configuration. <BR> <BR>For SunOS 4.x, the resolver is by default not set up to use DNS. The standard operating procedure to get SunOS to use <BR>DNS is in the comp.sys.sun FAQ, last I looked these were questions 1 and 2. In short, <BR> <BR> add the DNS trapdoor to NIS, or <BR> rebuild libc.a using resolv+ or the BIND 4.9.3 resolver routines. <BR> <BR>Of these, the BIND 4.9.3 option is recommended. <BR> <BR>Solaris 2.x is also not set up to use DNS by default. In the file /etc/nsswitch.conf there is a line <BR> <BR>hosts: files <BR> <BR>which needs to be changed to <BR> <BR>hosts: files dns <BR> <BR>for the machine to use DNS. <BR> <BR>Given a choice of servers, which one is queried? <BR> <BR>Based on a question by Mark A. Dohm <<A HREF="mailto:mark.dohm@teldta.com>">mark.dohm@teldta.com></A> and answer by Paul A Vixie <<A HREF="mailto:paul@vix.com>">paul@vix.com></A> <BR> <BR>Every recursive BIND name server (that is, one which is willing to go out and find something if asked something it doesn't <BR>know) will remember the measured round trip time (RTT) to each server it sends queries to. If it has a choice of several <BR>servers for some domain (like "." for example) it will use the one whose measured RTT is lowest. <BR> <BR>Since the measured RTT of all NS RRs starts at zero (0), every one is tried once. Once all have responded, all RTT's will <BR>be nonzero, and the "fastest server" will get all queries henceforth, until it slows down for some reason. <BR> <BR>To promote dispersion and good recordkeeping, BIND will penalize the RTT by a little bit each time a server is reused, <BR>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 <BR>answering quickly and consistently. <BR> <BR>Note that this is something BIND does that the DNS Specification does not mention at all. So other servers, those not <BR>based on BIND, might behave very differently. <BR> <BR>Transferring zones from a server running Microsoft NT Server 4.0 <BR> <BR>Based on an answer by Stuart Kwan <<A HREF="mailto:skwan@microsoft.com>">skwan@microsoft.com></A> <BR> <BR>If Microsoft's DNS server is integrated with WINS, it needs to be explicitly configured to interoperate with non-Microsoft <BR>name servers. Microsoft represents WINS information in the DNS using a nonstandard resource record type. This can <BR>cause a name server to fail when attempting a zone transfer from a Microsoft server. Older BIND servers may actually <BR>terminate when receiving such resource records in a zone transfer. <BR> <BR>To correct the problem, ensure that the option "Zone Properties -> WINS Lookup -> Settings only affect local server" is <BR>set for each such zone on the Microsoft server. <BR> <BR> <BR> <BR> <BR><A HREF="mailto:andras@is.co.za">andras@is.co.za</A> / The Internet Solution <BR> <BR>-- <BR> 白马带著她一步步的回到中原。白马已经老了,只能慢慢的走, <BR>但终是能回到中原的。江南有杨柳、桃花,有燕子、金鱼…… <BR>汉人中有的是英俊勇武的少年,倜傥潇洒的少年……但这个美 <BR>丽的姑娘就像古高昌国人那样固执: <BR> <BR> 「那都是很好很好的,可是我偏不喜欢。」 <BR> <BR>※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 159.226.21.172] <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -