📄 00000012.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>发信人: reden (鱼 ~ 梦娜丽莎的微笑 流星的故事), 信区: Linux <BR>标 题: DNS Tricks and Tips <BR>发信站: BBS 水木清华站 (Wed Nov 25 01:51:41 1998) <BR> <BR>DNS Tricks and Tips <BR> <BR>Here are some common tricks and some tips for common problems. <BR> <BR> <BR> Generating cache file with dig <BR> Recovering from an SOA typo <BR> Ultrix needs primaries in host file <BR> SLIP and BIND <BR> What is a Lame Delegation? <BR> Terminology: domain, zone, label <BR> CNAMEs as RR targets <BR> Local dummy zones <BR> Legal characters in hostnames <BR> Checking if a domain is registered already <BR> Setting up a resolver <BR> Given a choice of servers, which one is queried? <BR> Transferring zones from a server running Microsoft NT Server 4.0 <BR> <BR> <BR> <BR>Generating cache file with dig <BR> <BR>From Paul A Vixie <<A HREF="mailto:paul@vix.com>">paul@vix.com></A> and Ruediger Volk <<A HREF="mailto:rv@zeus.NIC.DTAG.DE>">rv@zeus.NIC.DTAG.DE></A> <BR> <BR>Anyone with DiG installed (which includes anyone running BIND 4.9 or better) can generate a new cache file by typing <BR> <BR> % dig <A HREF="mailto:@a.root-servers.net.">@a.root-servers.net.</A> . ns >root.cache <BR> <BR>Check this file by hand before installing it, of course. <BR> <BR>Recovering from an SOA typo <BR> <BR>From Steve Hubert <<A HREF="mailto:hubert@cac.washington.edu>">hubert@cac.washington.edu></A> <BR> <BR>It's only hard to recover from a typo if you're running an old BIND. If your secondaries are 4.9 or later, then you should <BR>just need two serial number changes to get back in sync: <BR> <BR> Let all the secondaries catch up to your typo serial number. <BR> Reset it to (2^31 - a little bit) more than the typo and wait for all the secondaries to catch up again. You may have <BR> to wrap the serial number back to zero in this or the next step. <BR> Set it to the correct value and wait for all the secondaries to catch up. <BR> <BR>Also refer to RFC 1982. <BR> <BR>Ultrix needs primaries in host file <BR> <BR>From William Gianopoulos <<A HREF="mailto:wag@swl.msd.ray.com>">wag@swl.msd.ray.com></A> <BR> <BR>With the stock Ultrix 4.3 name server (and possibly other releases), all primary nameservers must be in the /etc/hosts file. <BR>Look out for the indicative "address of primary server not in local db:" message in the logs. <BR> <BR>SLIP and DNS <BR> <BR>Based on a message from Cricket Liu <<A HREF="mailto:cricket@hp.com>">cricket@hp.com></A> <BR> <BR>Cricket Liu recommends not running a name server at the site that connects via SLIP, but instead pointing the resolver at <BR>a single name server on the upstream side of the SLIP link. If the SLIP link isn't up, the resolver doesn't have a route to <BR>the server, and since there's only one name server in resolv.conf, the resolver quickly backs off to using /etc/hosts. This <BR>assumes a reasonable resolver, of course. <BR> <BR>What is a Lame Delegation? <BR> <BR>From Bryan Beecher <<A HREF="mailto:Bryan.Beecher@umich.edu>">Bryan.Beecher@umich.edu></A> <BR> <BR>A lame delegation is an instance when a nameserver has been listed as authoritative for a domain, but does not seem to <BR>be performing authoritative service for that domain. That is, the nameserver appears to be answering out of its cache <BR>instead of out of its data. Note that even a server which is performing secondary service for a domain is still an <BR>authoritative server, and should be returning authoritative data. <BR> <BR>Terminology: domain, zone, label <BR> <BR>Based on a message from Paul Mockapetris <<A HREF="mailto:pvm@ISI.EDU>">pvm@ISI.EDU></A> <BR> <BR> A domain is a complete subtree. In the DNS tree, a domain is everything under a particular point in the tree. <BR> Domains relate to the naming structure itself, not the way things are distributed. <BR> A zone is a pruned domain. Pruning occurs when zones are delegated. Zones relate to the way the database is <BR> partitioned and distributed. <BR> A label is one component of a domain name. Labels need only be unique at a particular point in the tree, not in a <BR> zone: it is acceptable to have both NAME.dom.ain and NAME.sub.dom.ain both in the zone dom.ain. <BR> <BR>CNAMEs as RR targets <BR> <BR>From RFC 1034, Domain Concepts and Facilities <BR> <BR>Section 3.6.2, `Aliases and canonical names': <BR> <BR>Domain names in RRs which point at another name should always point at the primary name and not the alias. In other <BR>words, the names which are on the right hand side of a resource record (RR targets) should not be on the left hand side <BR>of a CNAME resource record. Depending on how smart the resolver software is CNAME targets may work fine, but <BR>depending on correct behaviour in resolvers all around the world is guaranteed to fail somewhere. <BR> <BR>Local dummy zones <BR> <BR>Based on a message from Dave Barr <<A HREF="mailto:barr@math.psu.edu>">barr@math.psu.edu></A> <BR> <BR>To stop the DNS from doing a lookup when the request is to localhost, run a local caching-only nameserver which is set <BR>up to be a primary for "localhost" as well as "127.in-addr.arpa" and include the necessary DNS data in those zones to <BR>resolve the respective names/addresses. Then point your /etc/resolv.conf to your local machine. To be extra safe from <BR>DNS corruption set the server up as a primary for "255.in-addr.arpa" and "0.in-addr.arpa" also. <BR> <BR>Legal characters in hostnames <BR> <BR>Domain names can contain almost any characters. However, host names and mail domain names have restrictions which <BR>only allow the use of characters `a-z', `A-Z', `0-9', and `-' (dash or minus sign). The `/' and `_' (divide or slash and <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -