Visit Our UNIX and Linux User Community

Special Forums IP Networking DNS: Dig returns different responses... Post 302885973 by fpmurphy on Wednesday 29th of January 2014 09:29:01 AM
Old 01-29-2014
A recursive query (which by the way is the default setting in dig) has nothing to do with returning subdomains.

If a DNS server does not have the requested information when it receives a recursive query, it queries other DNS servers until it gets the information, or until the query fails.
Test Your Knowledge in Computers #763
Difficulty: Medium
L4 caches are currently very common in computer systems.
True or False?

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ping to machine and count responses

if i wanted to ping all the machines in a given directory (/etc/hosts) and return a total count of responses how would i go about scripting that? complete be gentle if ; then //$1 = /etc/hosts cd "$1" //this puts me into the directory i need...but how do i send ... (2 Replies)
Discussion started by: trostycp
2 Replies

2. Shell Programming and Scripting

How to automate responses

I would have searched for this but I couldn't really think of what to use for the search text... I've got a situation where I need to automate responses to an executable when running it from a script so that it can be made into a job the operators don't have to interact with. When I run it... (2 Replies)
Discussion started by: djp
2 Replies

3. Shell Programming and Scripting

DNS prob - dig process

Dear MoDs, I have several doubts regarding query domain using DIG process.. below is my dig process:- ********************************************* dns-dual# /usr/bin/dig my soa ; <<>> DiG 9.3.0 <<>> my soa ;; global options: ... (1 Reply)
Discussion started by: unknown2205
1 Replies

4. Linux

How do I capture responses from the chat command?

Unfortunately googling the word 'chat' gives you zebedee billion responses that relate to everything and few of them refer to the linux chat command. I've read the man page and found a couple of examples but can't see how to do this. I want to query the modem for it's manufacturer, product id... (8 Replies)
Discussion started by: Bashingaway
8 Replies

5. Shell Programming and Scripting

Using AWK to Calculate Correct Responses

Hello, I am trying to count how many times a subject makes a correct switch or a correct stay response in a simple task. I have data on which condition they were in (here, labeled "IMAGINE" and "RECALL"), as well as whether they made a left or right button response, and whether the outcome was... (5 Replies)
Discussion started by: Jahn
5 Replies

6. What is on Your Mind?

DNS Lookup Tool Using DIG

Hi. Having a bit of quick fun putting some networking tools online. Here is a DNS Lookup tool. It's basically the DIG command line tool wrapped in forum formatting. If you want more features, please post here. I'm doing to make a few more network tools like this and move on to other... (1 Reply)
Discussion started by: Neo
1 Replies

7. IP Networking

Dig only returns MX records in +trace mode

One of our email recipients has 17 mx records, and our emailing program postfix on linux does not retrieve these records. When using dig, the same thing happens. This command returns no mx records >dig mx But when using +trace, the records get returned >dig mx +trace ... (4 Replies)
Discussion started by: Joop Kaashoek
4 Replies

8. UNIX for Beginners Questions & Answers

Simple conditional yields too many responses

In this script: #!/bin/bash # bird read -p "Enter name of a bird " REPLY=$REPLY birdname="duck sparrow hawk" for i in $birdname do if ] then echo "Yes, that is a bird." else echo "That is not a bird." fi done I get... (9 Replies)
Discussion started by: Xubuntu56
9 Replies

9. Windows & DOS: Issues & Discussions

Home Questions Tags Users Unanswered Windows 2016 DNS server returns SERVFAIL for non-existing doma

I have two DNS resolvers in /etc/resolv.conf file. The top one is Windows DNS server, and the bottom one is my wi-fi router. Please see below. nameserver nameserver In Windows DNS server, the sole "Forward Lookup Zone" is When I query for host in the zone... (6 Replies)
Discussion started by: broy32000
6 Replies
DNSPROXY(1)						    BSD General Commands Manual 					       DNSPROXY(1)

dnsproxy -- DNS proxy SYNOPSIS
dnsproxy [-dhV] [-c file] DESCRIPTION
The dnsproxy daemon waits for nameserver queries on a user specified address, dispatches these queries to authoritative and recursive name- servers and forwards the received answers back to the original client. The options are as follows: -c file Read configuration from file. -d Detach from current terminal and run as background process. -h Show usage. -V Show version. If a client from an internal IP address does a recursive lookup the query is forwarded to a recursive DNS server. Authoritative queries and queries coming from clients in foreign networks are forwarded to an authoritative DNS server. CONFIGURATION FILE
At startup dnsproxy reads a configuration file specified via the -c option or at the default location of /etc/dnsproxy.conf. The following keywords are recognized: authoritative IP Address of the authoritative nameserver [required]. recursive IP Address of the recursive nameserver [required]. listen IP Local address (defaults to port number Local port number (defaults to 53). chroot path A path to chroot to before starting to answer queries. user name A user to change to before starting to answer queries. authoritative-timeout seconds Time in seconds when authoritative queries time out (defaults to 10). recursive-timeout seconds Time in seconds when recursive queries time out (defaults to 90). authoritative-port number Port number on authoritative nameserver (defaults to 53). recursive-port number Port number on recursive nameserver (defaults to 53). statistics seconds Period between output of statistics (defaults to 3600). Use 0 to disable output of statistics completely. internal network Declare networks recognized as internal and thus eligible to do recursive queries. One network in CIDR notation per keyword. EXAMPLE authoritative recursive recursive-port 10053 listen port 53 chroot /var/empty user nobody internal internal STATISTICS
Every hour (by default) dnsproxy logs the collected statistics about its usage to standard error (or syslog when running detached). Statis- tics look like ActiveQr AuthorQr RecursQr AllQuery Answered 0 0 0 0 0 TimeoutQ DroppedQ DroppedA LateAnsw HashColl 0 0 0 0 0 and have the following meaning: ActiveQr Number of currently active queries proxied to the servers. AuthorQr Accumulated number of authoritative queries. RecursQr Accumulated number of recursive queries. AllQuery Accumulated number of all queries ever received. Answered Accumulated number of answered queries. TimeoutQ Accumulated number of queries that did not receive an answer in time. DroppedQ Accumulated number of dropped queries (e.g. transmission errors). DroppedA Accumulated number of dropped answers. LateAnsw Accumulated number of answers received after the timeout period. HashColl Accumulated number of hash collisions in the query list. SEE ALSO
named(1) VERSION
This manual page describes dnsproxy version 1.16. AUTHORS
Armin Wolfermann <> The dnsproxy homepage is at LOCAL
November 29, 2003 LOCAL

Featured Tech Videos

All times are GMT -4. The time now is 10:14 AM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy