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
5
votes
3 answers

Simple dig output?

In a script I want to be able to write an IP address to somewhere easily, so I thought using dig (or a similar command) with back-ticks. However the simplest output I've been able to come up to wrt dig parameters is > dig -t A +noall +answer…
knocte
  • 347
  • 1
  • 6
  • 18
4
votes
1 answer

dig output missing answer section

I recently got a new domain (lets call it testdomain.extample) from Route53 on Amazon. I further have a classic load balancer from AWS that I want requests to be forwarded to when somebody visits www.testdomain.example. Under hosted zones on Route53…
user2399453
  • 149
  • 1
  • 1
  • 3
4
votes
1 answer

BIND/DNS - dig +trace = Bad Referral and Bad Horizontal Referral

I have an interesting problem. I started noticing that when I do a dig +trace against one of the domains we are authoritative for, we get errors from our nameservers for "Bad Referral" and you can see where it forwarded the request back up the…
user53029
  • 629
  • 3
  • 14
  • 36
4
votes
2 answers

linux: shorter 'host' command output

I'm using dns to manage my virtual hosts. In order to do so I query my nameserver with the host command for certain values I need. For example: > host -t txt mycl1.vz mycl1.vz.myserver.de descriptive text "1026" but I only need 1026 as answer…
Scheintod
  • 391
  • 1
  • 5
  • 17
4
votes
2 answers

resolv.conf options not being honored

Was hoping to implement the "options rotate" directive within resolv.conf to have DNS lookups rotate through the nameservers listed in that file. As I understand it that is the point of this directive. It does not work on any system that I have…
CarpeNoctem
  • 2,437
  • 4
  • 23
  • 32
4
votes
2 answers

dig: "Transfer failed."

INPUT: dig +multiline google.com axfr OUTPUT: ; <<>> DiG 9.7.3-RedHat-9.7.3-1.fc14 <<>> +multiline google.com axfr ;; global options: +cmd ; Transfer failed. What am I missing? Regarding: DNS Lookup to Bind config file
LanceBaynes
  • 3,087
  • 9
  • 29
  • 31
4
votes
3 answers

Forcing the dig tool to return us answers from the root servers

When doing a dig over some site (i.e. www.nasa.gov) from different online dig tool sites(in this case, http://networking.ringofsaturn.com/Tools/dig.php and http://www.kloth.net/services/dig.php), I've noticed their answers are different. I guess…
4
votes
5 answers

Discover server responsible for serving a PTR for a specific IP?

Just as the title reads: How do I discover what nameserver is the authoritative nameserver for PTR records for a specific IP?
CarpeNoctem
  • 2,437
  • 4
  • 23
  • 32
4
votes
1 answer

What would be causing a "recursion requested but not available" error using dbndns?

The tinydns and dnscache services are running and I have 127.0.0.1 in my resolv.conf: root@ubuntu:~# cat /etc/resolv.conf nameserver 127.0.0.1 domain localdomain search localdomain root@ubuntu:~# sv status /etc/service/* run:…
joe
  • 51
  • 1
  • 1
  • 4
3
votes
2 answers

Authoritative DNS will not respond to pings or digs on domain

I am making an Authoritative DNS for a new site. The site responds nicely to all pings and most digs on its IP address, however rejects anything to its domain name. I would presume this is due to a DNS forwarding problem, but I can't make heads or…
storm
  • 89
  • 2
  • 3
  • 12
3
votes
2 answers

get NS record for domain using dig

I'm currently trying to write a script that validates, whether a given record attached to a name is available via all nameservers that are responsible for that name. E.g. I would like to check whether there is an A record for foo.example.com…
umläute
  • 499
  • 1
  • 7
  • 26
3
votes
2 answers

Domain Name Forwarding not working with github pages

I had my blog on github pages with a custom domain name blog.tamizhvendan.in and today I've moved it to a new domain name www.p3programmer.com by updating the CNAME record with www.p3programmer.com. The new domain name is working fine. As it is a…
3
votes
1 answer

Cannot find solution to "One or more of your nameservers did not return any of your NS records." on intoDNS site

I have set up DNS on my Linux Centos server and when I test on this site I get the following errors: WARNING: One or more of your nameservers did not return any of your NS records. ERROR: One or more of your nameservers did not respond: The ones…
setenson mile
  • 33
  • 1
  • 4
3
votes
1 answer

Why does TTL sometimes re-increment between DNS queries?

I dig xkcd.com, and I get something like this back: ; <<>> DiG 9.9.5-3ubuntu0.1-Ubuntu <<>> xkcd.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52538 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY:…
dayuloli
  • 1,253
  • 2
  • 11
  • 19
3
votes
1 answer

dig succeeds, nslookup fails (with dnsmasq as the server)

I installed dnsmasq on a machine of mine (It's a Kubuntu 12.04 LTS), backed only by /etc/hosts (no connection to the Internet until later). Now, if I dig mymachine, I get 192.168.0.1, but if I try to nslookup mymachine, I get: >> connection timed…
einpoklum
  • 1,652
  • 3
  • 21
  • 31
1 2
3
14 15