Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Jan 2001 22:43:48 -0800
From:      "Crist J. Clark" <cjclark@reflexnet.net>
To:        Steve Price <sprice@hiwaay.net>
Cc:        questions@FreeBSD.ORG
Subject:   Re: dig(1) Q
Message-ID:  <20010114224348.A97980@rfx-64-6-211-149.users.reflexco>
In-Reply-To: <20010115002522.J65118@bonsai.knology.net>; from sprice@hiwaay.net on Mon, Jan 15, 2001 at 12:25:22AM -0600
References:  <20010114234830.I65118@bonsai.knology.net> <20010114220528.X97980@rfx-64-6-211-149.users.reflexco> <20010115002522.J65118@bonsai.knology.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 15, 2001 at 12:25:22AM -0600, Steve Price wrote:
> On Sun, Jan 14, 2001 at 10:05:28PM -0800, Crist J. Clark wrote:
> # On Sun, Jan 14, 2001 at 11:48:30PM -0600, Steve Price wrote:
> # > I'm utterly confused at the output I've been getting from dig(1).
> # > Can anyone out there explain why the first time I run dig I get
> # > one answer and yet seconds later I get another?
> # 
> # Ask the servers you are querying. dig(1) is just telling you whatever
> # they send back.
> 
> I have and they both (the primary and secondary DNS servers for this
> domain) give me the first answer which is the correct one.  I have
> accounts on all of the boxes in question and when I dig(1) this domain
> on those boxes I get the answer I expect no matter how many times I try
> it.
> 
> # What I believe we have here is the differences between what you see
> # when you are getting a reply from the remote server and when you are
> # getting from the cached reply from the local server. Note,
> # 
> # > steve@bonsai(~)$ dig dogbark.com
> [snip]
> # > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
> #                ^^
> # This is an authoritarive response.
> 
> Yes and this is the one I'd expect to get every time.
> 
> # > steve@bonsai(~)$ dig dogbark.com
> [snip]
> # > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
> # 
> # This is not. It is cached.
> 
> Why wouldn't my local DNS server cache the correct result instead of
> a clearly bogus one after having received the correct one?

Clearly bogus? The only difference between the two is,

> # > ;; ADDITIONAL SECTION:
> # > bichon.dogbark.com.     10M IN A        207.234.88.178
> # > bichon.dogbark.com.     10M IN A        216.183.105.106
> # > spitz.dogbark.com.      10M IN A        207.234.88.179

Versus,

> # > ;; ADDITIONAL SECTION:
> # > bichon.dogbark.com.     1d14h50m59s IN A  207.234.88.178
> # > spitz.dogbark.com.      1d4h7m48s IN A  207.234.88.179

In the first one, we are getting two addresses for
bitchon.dogpark.com. In the second one, we only are given one of the
results for bitchon.dogpark.com. I guess it just returns the first
result it finds. I guess. But I don't know if that is "clearly bogus."
-- 
Crist J. Clark                           cjclark@alum.mit.edu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010114224348.A97980>