Questions tagged [dig]

dig is a command-line client to make queries against DNS servers, the Internet name servers.

dig is a command-line client that allows you to make queries against DNS servers, which are servers that provide the Internet name service. While querying DNS servers is part of most Internet based applications (like web browsers, chat clients, email tools and so forth), those queries are done by the clients in the background, and without any user intervention. dig allows you to make such queries explicitly from the command-line. This is usually interesting for people that maintain DNS servers and want to test them, or network administrators that want to inspect name resolution in a particular network.

dig is part of the BIND software package, which runs on POSIX platforms, but ports to the Windows platform exist. An alternative tool is nslookup, but dig is usually preferred for its better configurability and scriptability.

This tag should be added to questions that explicitly refer to the dig tool and its workings. Related tags are dns, nslooup, domain-name and bind.

Further information:

223 questions
1
vote
3 answers

What is the best way to get PRECISE domain name from ip address logged in iptables log

In iptables I am logging certain public IP addresses... say of websites visited from different workstations, depending on destination port number... All this is not really relevant to the question but I am just stating it here so my goals become…
Sunny
  • 381
  • 1
  • 6
  • 16
1
vote
1 answer

Using 'Dig' to zone transfer but gets a 'timed out connection'

i am corrently trying to test a zone transfer via dig (9.8.4) with the following command: dig axfr @ns.server.com domainname.com and i get the following error:(notice its not a declined zone transfer error) <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> axfr…
Sahar
  • 11
  • 3
1
vote
1 answer

Where does dig additional section nameserver information come from?

I have a client whose website has intermittent issues, which I believe are due to DNS lookup. When this happens and they do a ping, the host cannot be resolved. Therefore, I ran: dig @a.gtld-servers.net autoquarterly.com I get: ;; ADDITIONAL…
1
vote
1 answer

TTL and Google DNS

I've found a similar post about this, however my user can't comment. I wonder why doing dig @8.8.8.8 domain.com prints out different "countdowns" when running it several times in few seconds, as if that domain was cached in different places inside…
whitenoisedb
  • 125
  • 1
  • 6
1
vote
0 answers

Dig returns Refused Status on norecurse?

I've looked up two questions here at serverfault, but my question's a little different in specificity - when running the dig command with the +norecurs option (I'm trying to experiment with cache here - by running it once with +norecurs and another…
blazonix
  • 113
  • 1
  • 5
1
vote
2 answers

Why are additional DNS records only returned when the query isn't cached?

I'm trying to track down an issue we're having sending mail to a particular domain. We noticed that we're not getting consistent results from nslookup/dig when querying their MX records, and I'm not sure if we're chasing a non-existent DNS problem…
rtf
  • 884
  • 2
  • 17
  • 31
1
vote
1 answer

Check all domains served by a DNS server

Is there any way to query a dns server to find out all the domains it is the authoritative server? [all domains it has configured?] (I can use dig or any other tool)
AlfaTeK
  • 275
  • 3
  • 12
1
vote
1 answer

PowerDNS does not resolve TXT records

My PowerDNS DNS server 3.3 does not resolve TXT records. Database looks like this: PowerDNS database When I try to dig my server for TXT entry they are not being shown: [root@nowosci powerdns]# dig @ns1.nowosci.org private._domainkey.nowosci.org…
Spacedust
  • 568
  • 5
  • 13
  • 28
1
vote
1 answer

Dkim DNS Setup: dig +trace finds the key, dig notrace doesn't

i'm setting up DKIM for my domain to sign outgoing mails. I've got some issues on DNS configuration, because DNS configuration is mixed between external DNS (hosting) and a cloud server, which sends the emails. Cloud server IP: 85.95.211.100…
apelliciari
  • 179
  • 1
  • 11
1
vote
1 answer

Dig Connection Error on SRV Records

Using Bind9 running on localhost. I have two records in my DNS zone file: _kerberos._udp.GROUP-42.SNOOPY.ISP IN SRV 0 0 88 kirby.group-42.snoopy.isp. kirby.group-42.snoopy.isp. IN A 10.44.42.129 I can run dig…
Takkun
  • 113
  • 3
1
vote
1 answer

Bind DNS configuration, dig command don't resolve name

I am using Fedora 17 with bind 9. I tried to manually configure a DNS for a network, editing /etc/named.conf: options { listen-on port 53 { localhost; }; listen-on-v6 port 53 { ::1; }; directory "/var/named"; dump-file …
Ramy Al Zuhouri
  • 261
  • 1
  • 4
  • 14
1
vote
1 answer

"dig ... any" shows A record but "dig ... a" does not

When using "dig host.name.here.com A" I get SERVFAIL and no answer. But when I do a "dig host.name.here.com ANY" I get NOERROR and it returns an A record. Any idea as to what may be wrong with the domain in question? Below is a sanitized example.…
sij99
  • 11
  • 1
  • 2
1
vote
2 answers

Why don't DNS root servers answer?

If I try to query a root server with dig, I never receive an answer. For example the output for dig @b.root-servers.net www.ubuntu.com is ; <<>> DiG 9.8.1-P1 <<>> @b.root-servers.net www.ubuntu.com ; (1 server found) ;; global options: +cmd ;;…
JustTrying
  • 239
  • 2
  • 5
  • 11
1
vote
2 answers

CentOS 5.8 dig is not resolving ip-address

I'm running centos 5.8 on a local machine at home. Today I was trying to analyze the DNS-Lookup via dig. $ dig +trace -t A www.heise.de. This is giving me something like this as a response de. 172800 IN NS f.nic.de. de. 172800 …
travisbotello
  • 23
  • 1
  • 7
1
vote
0 answers

DNS lookup failure while configuration is okay

I have configured my DNS using OpenPanel and it didn't report any errors. It just adds a DNS config file which is included /etc/bind/named.conf. When I do named-checkconf /etc/bind/named.conf which finishes without reporting any errors, by the…
Milad Naseri
  • 195
  • 4