dig查询dns解析

DNS基础之使用dig查询DNS解析过程 文中内容参考DNS 原理入门—阮一峰。DNS服务器怎么会知道每个域名的IP地址呢?答案是分级查询。根域名.root对于所有域名都是一样的,所以平时是省略的。 根域名的下一级,叫做"顶级域名"(top-level domain,缩写为TLD),比如:等等 再下一级叫做"次级域名"(second-level domain,缩写为SLD),比如里面的,这一级域名是用户可以注册的;... 阅读详情

一般来说linux下查询域名解析有两种选择,nslookup或者dig,而在使用上我觉得dig更加方便顺手。
如果是在debian下的话,只要装上dnsutils这个包就可以使用dig命令了。

最基本的使用方式就是

dig www.oolec.com

即查询域名的A记录,查询的dns服务器将采用系统配置的服务器,即/etc/resovle.conf 中的。

如果要查询其他类型的记录,比如MX,CNAME,NS,PTR等,只需将类型加在命令后面即可

dig www.oolec.com mx
dig www.oolec.com ns

此外,如果你是一个系统管理员,部署好了一台dns服务器之后想对它进行解析测试,就必须要显式指定待测试的dns服务器地址了,例如

dig @202.106.0.20 www.oolec.com a

默认情况下dig将采用udp协议进行查询,如果要采用tcp方式,可以加上 +tcp参数

dig www.oolec.com a +tcp

另外一个重要的功能是+trace参数,使用这个参数之后将显示从根域逐级查询的过程

dig www.oolec.com a +trace

比如,对本站域名www.linuxers.cn A记录的trace查询可以看到根域.,顶级域.cn,以及linuxers.cn的域名权威服务器的地址及其各自的返回结果,这样对于追踪dns解析中的问题有很大的帮助。

leconte@localhost:~$ dig www.linuxers.cn a +trace
 
; <<>> DiG 9.5.1-P3 <<>> www.linuxers.cn 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
 
www.linuxers.cn.        600     IN      A       218.240.42.72
;; Received 49 bytes from 222.186.26.115#53(ns2.dnspood.net) in 1132 ms
今天刚好是百度出问题时候。 

关于dig的更进一步的使用方式请参考这里


dig (1) - BIND9

(Updated: Jun 30, 2000)  

NAME

dig - DNS lookup utility  

SYNOPSIS

dig [@server] [ -b  address] [ -c  class] [ -f  filename] [ -k  filename] [ -m] [ -p  port#] [ -q  name] [ -t  type] [ -x  addr] [ -y  [hmac:]name:key] [ -4] [ -6] [name] [type] [class] [queryopt...] dig [ -h] dig [global-queryopt...] [query...]
 

DESCRIPTION

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.  

SIMPLE USAGE

A typical invocation of dig looks like:


 dig @server name type 

where:

server


is the name or IP address of the name server to query. This can be an IPv4 address in dotted-decimal notation or an IPv6 address in colon-delimited notation. When the supplied server argument is a hostname, dig resolves that name before querying that name server. If no server argument is provided, dig consults /etc/resolv.conf and queries the name servers listed there. The reply from the name server that responds is displayed.

name


is the name of the resource record that is to be looked up.

type


indicates what type of query is required --- ANY, A, MX, SIG, etc. type can be any valid query type. If no type argument is supplied, dig will perform a lookup for an A record.
 

OPTIONS

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 dnssec-keygen(8). Caution should be taken when using the -y option on multi-user systems as the key can be visible in the output from ps(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.  

QUERY OPTIONS

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


Use [do not use] TCP when querying name servers. The default behavior is to use UDP unless an AXFR or IXFR query is requested, in which case a TCP connection is used.

+[no]vc


Use [do not use] TCP when querying name servers. This alternate syntax to +[no]tcp is provided for backwards compatibility. The "vc" stands for "virtual circuit".

+[no]ignore


Ignore truncation in UDP responses instead of retrying with TCP. By default, TCP retries are performed.

+domain=somename


Set the search list to contain the single domain somename, as if specified in a domain directive in /etc/resolv.conf, and enable search list processing as if the +search option were given.

+[no]search


Use [do not use] the search list defined by the searchlist or domain directive in resolv.conf (if any). The search list is not used by default.

+[no]showsearch


Perform [do not perform] a search showing intermediate results.

+[no]defname


Deprecated, treated as a synonym for +[no]search

+[no]aaonly


Sets the "aa" flag in the query.

+[no]aaflag


A synonym for +[no]aaonly.

+[no]adflag


Set [do not set] the AD (authentic data) bit in the query. The AD bit currently has a standard meaning only in responses, not in queries, but the ability to set the bit in the query is provided for completeness.

+[no]cdflag


Set [do not set] the CD (checking disabled) bit in the query. This requests the server to not perform DNSSEC validation of responses.

+[no]cl


Display [do not display] the CLASS when printing the record.

+[no]ttlid


Display [do not display] the TTL when printing the record.

+[no]recurse


Toggle the setting of the RD (recursion desired) bit in the query. This bit is set by default, which means dig normally sends recursive queries. Recursion is automatically disabled when the +nssearch or +trace query options are used.

+[no]nssearch


When this option is set, digattempts to find the authoritative name servers for the zone containing the name being looked up and display the SOA record that each name server has for the zone.

+[no]trace


Toggle tracing of the delegation path from the root name servers for the name being looked up. Tracing is disabled by default. When tracing is enabled, digmakes iterative queries to resolve the name being looked up. It will follow referrals from the root servers, showing the answer from each server that was used to resolve the lookup.

+[no]cmd


Toggles the printing of the initial comment in the output identifying the version of dig and the query options that have been applied. This comment is printed by default.

+[no]short


Provide a terse answer. The default is to print the answer in a verbose form.

+[no]identify


Show [or do not show] the IP address and port number that supplied the answer when the +shortoption is enabled. If short form answers are requested, the default is not to show the source address and port number of the server that provided the answer.

+[no]comments


Toggle the display of comment lines in the output. The default is to print comments.

+[no]stats


This query option toggles the printing of statistics: when the query was made, the size of the reply and so on. The default behavior is to print the query statistics.

+[no]qr


Print [do not print] the query as it is sent. By default, the query is not printed.

+[no]question


Print [do not print] the question section of a query when an answer is returned. The default is to print the question section as a comment.

+[no]answer


Display [do not display] the answer section of a reply. The default is to display it.

+[no]authority


Display [do not display] the authority section of a reply. The default is to display it.

+[no]additional


Display [do not display] the additional section of a reply. The default is to display it.

+[no]all


Set or clear all display flags.

+time=T


Sets the timeout for a query to T seconds. The default timeout is 5 seconds. An attempt to set T to less than 1 will result in a query timeout of 1 second being applied.

+tries=T


Sets the number of times to try UDP queries to server to T instead of the default, 3. If T is less than or equal to zero, the number of tries is silently rounded up to 1.

+retry=T


Sets the number of times to retry UDP queries to server to T instead of the default, 2. Unlike +tries, this does not include the initial query.

+ndots=D


Set the number of dots that have to appear in name to D for it to be considered absolute. The default value is that defined using the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted as relative names and will be searched for in the domains listed in the search or domain directive in /etc/resolv.conf.

+bufsize=B


Set the UDP message buffer size advertised using EDNS0 to Bbytes. The maximum and minimum sizes of this buffer are 65535 and 0 respectively. Values outside this range are rounded up or down appropriately. Values other than zero will cause a EDNS query to be sent.

+edns=#


Specify the EDNS version to query with. Valid values are 0 to 255. Setting the EDNS version will cause a EDNS query to be sent. +noedns clears the remembered EDNS version.

+[no]multiline


Print records like the SOA records in a verbose multi-line format with human-readable comments. The default is to print each record on a single line, to facilitate machine parsing of the dig output.

+[no]fail


Do not try the next server if you receive a SERVFAIL. The default is to not try the next server which is the reverse of normal stub resolver behavior.

+[no]besteffort


Attempt to display the contents of messages which are malformed. The default is to not display malformed answers.

+[no]dnssec


Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query.

+[no]sigchase


Chase DNSSEC signature chains. Requires dig be compiled with -DDIG_SIGCHASE.

+trusted-key=####


Specifies a file containing trusted keys to be used with +sigchase. Each DNSKEY record must be on its own line.

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


When chasing DNSSEC signature chains perform a top-down validation. Requires dig be compiled with -DDIG_SIGCHASE.

+[no]nsid


Include an EDNS name server ID request when sending a query.
 

MULTIPLE QUERIES

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 www.isc.org 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 www.isc.org, 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.  

IDN SUPPORT

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.  

FILES

/etc/resolv.conf

${HOME}/.digrc  

SEE ALSO

host(1), named(8), dnssec-keygen(8), RFC1035.  

BUGS

There are probably too many query options.  

COPYRIGHT

Copyright © 2004-2008 Internet Systems Consortium, Inc. ("ISC")
Copyright © 2000-2003 Internet Software Consortium.

 

 

来自http://blog.chinaunix.net/uid-7530389-id-2050073.html

yum install dkms出现No match for argument: dkms和Error:Unable to find a match: dkms的解决方案 本文主要介绍了yum install dkms出现No match for argument: dkms和Error:Unable to find a match: dkms的解决方案,希望能对学习Linux的同学们有所帮助。 文章目录 1. 问题描述 2. 解决方案 阅读详情

相关推荐

静态分析工具COBOT与Testbed对比

Testbed为规则检查工具的代表,市场占有量非常大,但随着时间的推移,大家从规则匹配转向了用静态分析工具检查Bug,所以规则检查型工具占有量比开始时候已经减少,但仍有一些比较落后的单位还在继续采购此类工具。3、通过对开源工程的测试,进行误漏报率的对比,发现COBOT(库博)的误漏报率相比Testbed较低,因COBOT主打国内市场,在众多军工单位进行大量试用及使用,吸取了众多单位的意见和建议,更加符合国内军工单位的使用习惯及测试要求。4、此外库博在功能上还可以进行计划任务,检测队列,检测并发的功能支持。

chengoodflower的博客 2055

yum install dig报错 No match for argument: dig Error: Unable to find a match: dig解决方法

yum install dig报错。

c_hiyan的博客 655

H3C交换机Console口连接全攻略:从接线到PuTTY配置(附常见问题排查)

本文详细介绍了H3C交换机Console口的连接与配置方法,包括硬件线缆选择、驱动安装、PuTTY参数设置及常见问题排查。特别针对Console转USB线缆的兼容性和驱动安装难点提供实用建议,帮助网络工程师快速掌握串联调试技巧,解决连接中的黑屏、乱码等典型问题。

weixin_42549451的博客 674

yum 命令提示:No match for argument: xxx 错误

解决办法:安装EPEL源。系统版本:Rocky9。原因:没有配置yum源。

1万+

保姆级教程:用STM32标准库搞定TIM1的PWM输出(附完整代码和避坑点)

本文提供STM32F103高级定时器TIM1的PWM输出保姆级教程,涵盖从工程搭建到完整代码实现的详细步骤。重点解析TIM1作为高级定时器的特殊配置要点,包括时钟初始化、PWM通道设置和GPIO复用功能,并附常见问题排查指南和动态调整占空比的实用技巧,帮助开发者高效实现精准PWM控制。

weixin_30673611的博客 433

从零开始 使用OMNET++结合VEINS,INET和SUMO的联合仿真

搭建仿真的环境,导入VEINS和INET开源库,使用INET库中提供的网络协议和功能模型来模拟通信协议和网络功能,使用SUMO创建道路网络和车辆轨迹,并导出到OMNeT++中 在OMNeT++中使用VEINS通过socket和SUMO连接,借助VEINS实现的TRACI接口来设置车辆相关的行为和场景,最后在OMNET++中结合VEINS,SUMO和INET运行联合仿真实验,并分析车辆在遇到紧急情况下的通信状况和具体行为

mjmmm的博客 1万+

DNS基础之通过dig命令理解DNS域名解析中的A记录,AAAA记录,CNAME记录,MX记录,NS记录

文中内容参考DNS 原理入门—阮一峰。DNS(Domain Name System) 即域名系统。 作用就是根据域名查出 IP 地址。我们使用(Dig是一个在类Unix命令行模式下查询DNS包括NS记录,A记录,MX记录等相关信息的工具)来显示 DNS的查询过程。 ......

zxl1990_ok的博客 1万+

新手必看!无人机定高PID调参避坑指南:从理论到实战的完整流程

本文为无人机新手提供定高PID调参的完整指南,从传感器融合到抗风策略,详细解析多传感器融合、PID控制参数调试及环境干扰应对。通过实战案例和代码示例,帮助开发者快速掌握无人机定高技术,避免常见调参陷阱,提升飞行稳定性。

spark7igniter的博客 221

dig 域名信息查询

dig 域名信息查询 文章目录dig 域名信息查询前言一、dig是什么?二、使用步骤1.参数2.参数的使用3.查询域名解析记录4.把对应的解析记录解析成IP地址5.记录类型-x 的使用三、查询选项总结 前言 功能最全面最权威的DNS查询工具 一、dig是什么? dig ( domain information groper ) 作为功能最全面的DNS查询工具,具有灵活、易用、输出清晰等特点,而且其全面支持所有Class以及所有type类型的记录查询,是BIND开发者推荐的首选工具。 二、使用步骤 1.

weixin_44617541的博客 4386

【部署优化篇三】《DeepSeek边缘计算实战:把目标检测模型塞进树莓派,让AI在巴掌大的设备上“开天眼“》

谁说只有超级计算机才能跑AI?今天咱们就要在树莓派上玩转DeepSeek目标检测,让这个巴掌大的小盒子变成会‘看’世界的智能终端!本文手把手教你从零开始,把最潮的目标检测模型塞进树莓派。全程高能预警,建议准备好你的树莓派4B/5和散热风扇,咱们这就开启边缘计算的魔法之旅!

商务合作|问题讨论|交流学习 请联系作者微信,加微信请务必注明来意,博客主页有联系方式 1305

SpringBoot 插件化开发详细总结

SpringBoot 插件化开发方案总结

congge 1万+

深入解析DNS查询:从dig命令看域名解析的全过程

在互联网世界中,域名系统(DNS,Domain Name System)扮演着至关重要的角色。它负责将人类可读的域名(如 `example.com`)转换为机器可识别的IP地址(如 `93.184.216.34`),使得网络通信成为可能。 在日常运维和网络故障排查中,`dig`(Domain Information Groper)是一个强大的DNS查询工具,能够提供详细的域名解析信息。本文将通过一个实际的 `dig` 查询案例,深入解析DNS查询的各个部分,帮助读者理解DNS的工作原理,并掌握如何使

私聊前往站内信:https://i.youkuaiyun.com/#/msg/chat/weixin_44976692 1941

“/usr/lib/wsl/wsl-setup“ failed, exiting

WSL2安装Ubuntu时出现"wsl-setup failed"错误的解决方法 摘要:当Windows用户名包含中文字符时,安装WSL2+Ubuntu会出现"wsl-setup failed"错误。本文提供两种解决方案:1)修改中文用户名(风险较大);2)通过命令手动配置。推荐第二种方法:先使用"wsl -l -v"查看Ubuntu名称,再通过"wsl -d Ubuntu20.04 -e /bin/bash"命令启动WSL2系

猿小白的博客 994

使用dig查询dns解析

原文地址:使用dig查询dns解析 作者:chenwenming 一般来说linux下查询域名解析有两种选择,nslookup或者dig,而在使用上我觉得dig更加方便顺手。 如果是在debian下的话,只要装上dnsutils这个包就可以使用dig命令了。 最基本的使用方式就是 dig www.oolec.com 即查询域名的A记录,查询的dns服务器将采用系统配置的服...

weixin_33979203的博客 848

假人有限元模型

假人模型,车辆碰撞假人有限元模型,适合做乘员安全的研究者利用

精雕软件(JDpaint) 5.5 绿色版

精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版

深入解析 dig 命令:DNS 查询与故障排除利器

在互联网和局域网中,DNS(域名系统)起着至关重要的作用。网络管理员在解决域名解析和DNS故障时,常常需要借助强大的工具来定位问题。dig(Domain Information Groper)作为一款功能强大的DNS查询工具,凭借清晰详细的查询结果和灵活的参数配置,成为Linux系统(如RedHat、RHEL、Ubuntu、CentOS、Fedora等)上不可或缺的调试利器。本文将详细介绍dig命令的基本语法、常用参数、实例解析以及一些使用技巧,帮助您快速上手并深入理解该工具。

XMYX-0 1471

win10 跳过U8环境检测的IE WebControls.rar

win10 安装u8的时候 提示IE WebControls 不通过,这个工具可以欺骗u8的检查。 跳过U8环境检测的IE WebControls。提示导入失败后,重新检测通过。

linux查看dns及ttl时间,使用dig查询dns解析

一般来说linux下查询域名解析有两种选择,nslookup或者dig,而在使用上我觉得dig更加方便顺手。如果是在debian下的话,只要装上dnsutils这个包就可以使用dig命令了。最基本的使用方式就是dig即查询域名的A记录,查询的dns服务器将采用系统配置的服务器,即/etc/resovle.conf 中的。如果要查询其他类型的记录,比如MX,CNAME,NS,PTR等,只需将类型加在...

weixin_39612733的博客 3204

温度PID控制PLC程序

温度PID稳定控制程序,适用于欧姆龙PLC,对其他PLC也具有很大参考价值

查询 DNS 解析**的工具,nslookup , dig,Resolve-DnsName等

两个都是的工具,用来查,排查域名/网络解析问题。

sun007700的专栏 297

DNS正、反解析查询指令host、dig、nslookup

一、host指令格式:host [-a] FQDN [server] host -l domain [server]选项:-a :代表列出该主机所有的相关信息,包括 IP、TTL 与除错讯息等等-l :若后面接的那个 domain 设定允许 allow-transfer 时,则列出该domain所管理的所有主机名对应数据!server:这个参数可有可无,当想要利用非 /etc/...

weixin_34294649的博客 575

[Linux] host dig nslookup查询域名的DNS解析

root@VM-38-204-ubuntu:~# host baidu.com baidu.com has address 220.181.57.216 baidu.com has address 123.125.114.144 baidu.com mail is handled by 15 mx.n.shifen.com. baidu.com mail is handled ...

weixin_34261739的博客 138

java查询域名ns,使用dig/nslookup命令查看dns解析的方法步骤

dig - DNS lookup utility当域名出现访问故障时,可以通过检查域名解析来判断是否是由错误的解析导致的问题。1.域名解析无结果(不存在或被HOLD(未实名认证等))2.域名解析到错误的IP(被阻断,被劫持响应错误结果,需要对解析流程做判断)3.对应CNAME记录的值无法解析4.部分解析异常(配置多个域名服务器时,多个服务器解析结果不一致,需要确认是否在DNS服务器上配置添加的解析...

weixin_35851654的博客 909

Linux dig命令超全详解|DNS域名解析查询、故障排查实战教程

dig命令是用于DNS查询的实用工具,比nslookup更详细灵活。基本语法为dig [@server] [name] [type],支持指定DNS服务器、查询类型(如A/MX/NS记录)和输出格式。常用选项包括+short(简洁输出)、+trace(跟踪解析路径)和-x(反向查询IP)。示例用法涵盖基础查询、批量操作和权威服务器查询。注意输出中的TTL值,并留意防火墙或网络限制可能影响查询。该工具是网络管理员进行DNS调试的重要选择。

qq_36742166的博客 203
elseME
博客等级 码龄10年 0粉丝 0原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值