分类: LINUX
2010-01-12 10:43:30
一般来说linux下查询域名解析有两种选择,nslookup或者dig,而在使用上我觉得dig更加方便顺手。
如果是在debian下的话,只要装上dnsutils这个包就可以使用dig命令了。
最基本的使用方式就是
dig
即查询域名的A记录,查询的dns服务器将采用系统配置的服务器,即/etc/resovle.conf 中的。
如果要查询其他类型的记录,比如MX,CNAME,NS,PTR等,只需将类型加在命令后面即可
dig mx
dig ns
此外,如果你是一个系统管理员,部署好了一台dns服务器之后想对它进行解析测试,就必须要显式指定待测试的dns服务器地址了,例如
dig @202.106.0.20 a
默认情况下dig将采用udp协议进行查询,如果要采用tcp方式,可以加上 +tcp参数
dig a +tcp
另外一个重要的功能是+trace参数,使用这个参数之后将显示从根域逐级查询的过程
dig a +trace
比如,对本站域名 A记录的trace查询可以看到根域.,顶级域.cn,以及linuxers.cn的域名权威服务器的地址及其各自的返回结果,这样对于追踪dns解析中的问题有很大的帮助。
leconte@localhost:~$ dig a +trace
; <<>> DiG 9.5.1-P3 <<>> a +trace
;; global options: printcmd
. 215857 IN NS E.ROOT-SERVERS.NET.
. 215857 IN NS B.ROOT-SERVERS.NET.
. 215857 IN NS J.ROOT-SERVERS.NET.
. 215857 IN NS K.ROOT-SERVERS.NET.
. 215857 IN NS L.ROOT-SERVERS.NET.
. 215857 IN NS F.ROOT-SERVERS.NET.
. 215857 IN NS G.ROOT-SERVERS.NET.
. 215857 IN NS I.ROOT-SERVERS.NET.
. 215857 IN NS M.ROOT-SERVERS.NET.
. 215857 IN NS A.ROOT-SERVERS.NET.
. 215857 IN NS C.ROOT-SERVERS.NET.
. 215857 IN NS H.ROOT-SERVERS.NET.
. 215857 IN NS D.ROOT-SERVERS.NET.
;; Received 228 bytes from 192.168.127.2#53(192.168.127.2) in 12 ms
cn. 172800 IN NS a.dns.cn.
cn. 172800 IN NS b.dns.cn.
cn. 172800 IN NS c.dns.cn.
cn. 172800 IN NS d.dns.cn.
cn. 172800 IN NS e.dns.cn.
cn. 172800 IN NS ns.cernet.net.
;; Received 298 bytes from 199.7.83.42#53(L.ROOT-SERVERS.NET) in 496 ms
linuxers.cn. 21600 IN NS ns1.dnspood.net.
linuxers.cn. 21600 IN NS ns2.dnspood.net.
;; Received 80 bytes from 202.112.0.44#53(ns.cernet.net) in 12 ms
. 600 IN A 218.240.42.72
;; Received 49 bytes from 222.186.26.115#53(ns2.dnspood.net) in 1132 ms
今天刚好是百度出问题时候。
关于dig的更进一步的使用方式请参考
dig (domain information groper) is a flexible tool for interrogating DNS name servers. It performs DNS lookups and displays the answers that are returned from the name server(s) that were queried. Most DNS administrators use dig
to troubleshoot DNS problems because of its flexibility, ease of use and clarity of output. Other lookup tools tend to have less functionality than dig.Although digis normally used with command-line arguments, it also has a batch mode of operation for reading lookup requests from a file. A brief summary of its command-line arguments and options is printed when the -h option is given. Unlike earlier versions, the BIND 9 implementation of dig allows multiple lookups to be issued from the command line.
Unless it is told to query a specific name server, dig will try each of the servers listed in /etc/resolv.conf.
When no command line arguments or options are given, dig will perform an NS query for "." (the root).
It is possible to set per-user defaults for dig via ${HOME}/.digrc. This file is read and any options in it are applied before the command line arguments.
The IN and CH class names overlap with the IN and CH top level domains names. Either use the -t and -c options to specify the type and class, use the -q the specify the domain name, or use "IN." and "CH." when looking up these top level domains.
A typical invocation of dig looks like:
dig @server name type
where:
server
name
type
The
-b
option sets the source IP address of the query to
address. This must be a valid address on one of the host's
network interfaces or "0.0.0.0" or "::". An optional port may be
specified by appending "#
The default query class (IN for internet) is overridden by the -c option. class is any valid class, such as HS for Hesiod records or CH for Chaosnet records.
The -f option makes dig operate in batch mode by reading a list of lookup requests to process from the file filename. The file contains a number of queries, one per line. Each entry in the file should be organized in the same way they would be presented as queries to dig using the command-line interface.
The -m option enables memory usage debugging.
If a non-standard port number is to be queried, the -p option is used. port# is the port number that digwill send its queries instead of the standard DNS port number 53. This option would be used to test a name server that has been configured to listen for queries on a non-standard port number.
The -4 option forces dig to only use IPv4 query transport. The -6 option forces dig to only use IPv6 query transport.
The -t option sets the query type to type. It can be any valid query type which is supported in BIND 9. The default query type is "A", unless the -xoption is supplied to indicate a reverse lookup. A zone transfer can be requested by specifying a type of AXFR. When an incremental zone transfer (IXFR) is required, typeis set to ixfr=N. The incremental zone transfer will contain the changes made to the zone since the serial number in the zone's SOA record was N.
The -q option sets the query name to name. This useful do distinguish the name from other arguments.
Reverse lookups --- mapping addresses to names --- are simplified by the -x option. addris an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 address. When this option is used, there is no need to provide the name, class and type arguments. digautomatically performs a lookup for a name like 11.12.13.10.in-addr.arpa and sets the query type and class to PTR and IN respectively. By default, IPv6 addresses are looked up using nibble format under the IP6.ARPA domain. To use the older RFC1886 method using the IP6.INT domain specify the -i option. Bit string labels (RFC2874) are now experimental and are not attempted.
To sign the DNS queries sent by dig and their responses using transaction signatures (TSIG), specify a TSIG key file using the -k option. You can also specify the TSIG key itself on the command line using the -y option; hmac is the type of the TSIG, default HMAC-MD5, name is the name of the TSIG key and key is the actual key. The key is a base-64 encoded string, typically generated by (8). Caution should be taken when using the -y option on multi-user systems as the key can be visible in the output from (1) or in the shell's history file. When using TSIG authentication with dig, the name server that is queried needs to know the key and algorithm that is being used. In BIND, this is done by providing appropriate key and server statements in named.conf.
digprovides a number of query options which affect the way in which lookups are made and the results displayed. Some of these set or reset flag bits in the query header, some determine which sections of the answer get printed, and others determine the timeout and retry strategies.
Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded by the string no to negate the meaning of that keyword. Other keywords assign values to options like the timeout interval. They have the form +keyword=value. The query options are:
+[no]tcp
+[no]vc
+[no]ignore
+domain=somename
+[no]search
+[no]showsearch
+[no]defname
+[no]aaonly
+[no]aaflag
+[no]adflag
+[no]cdflag
+[no]cl
+[no]ttlid
+[no]recurse
+[no]nssearch
+[no]trace
+[no]cmd
+[no]short
+[no]identify
+[no]comments
+[no]stats
+[no]qr
+[no]question
+[no]answer
+[no]authority
+[no]additional
+[no]all
+time=T
+tries=T
+retry=T
+ndots=D
+bufsize=B
+edns=#
+[no]multiline
+[no]fail
+[no]besteffort
+[no]dnssec
+[no]sigchase
+trusted-key=####
If not specified dig will look for /etc/trusted-key.key then trusted-key.key in the current directory.
Requires dig be compiled with -DDIG_SIGCHASE.
+[no]topdown
+[no]nsid
The BIND 9 implementation of dig supports specifying multiple queries on the command line (in addition to supporting the -f batch file option). Each of those queries can be supplied with its own set of flags, options and query options.
In this case, each queryargument represent an individual query in the command-line syntax described above. Each consists of any of the standard options and flags, the name to be looked up, an optional query type and class and any query options that should be applied to that query.
A global set of query options, which should be applied to all queries, can also be supplied. These global query options must precede the first tuple of name, class, type, options, flags, and query options supplied on the command line. Any global query options (except the +[no]cmd option) can be overridden by a query-specific set of query options. For example:
dig +qr any -x 127.0.0.1 isc.org ns +noqr
shows how dig could be used from the command line to make three lookups: an ANY query for , a reverse lookup of 127.0.0.1 and a query for the NS records of isc.org. A global query option of +qr is applied, so that dig shows the initial query it made for each lookup. The final query has a local query option of +noqr which means that dig will not print the initial query when it looks up the NS records for isc.org.
If dig has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. digappropriately converts character encoding of domain name before sending a request to DNS server or displaying a reply from the server. If you'd like to turn off the IDN support for some reason, defines the IDN_DISABLE environment variable. The IDN support is disabled if the variable is set when dig runs.
/etc/resolv.conf
${HOME}/.digrc
(1), (8), (8), RFC1035.
There are probably too many query options.