no ADDITIONAL SECTION in answer

[Ulrich David]

Le 9 oct. 08 à 17:51, James a écrit :
> I noticed that too but I had different versions so I figured it just  
> changed.
>
> This is from man dig:
> "       +[no]additional
>           Display [do not display] the additional section of a  
> reply. The
>           default is to display it."
>
> Did you use the same dig client with the different servers?

Hi,

Yes, I use same dig client (2 tests with dig 9.4.2-P2 and 2 with 9.3.5- 
P1)
The client version doesn't change the result.

>
> Do you see the additional section if you explicitly ask for it on  
> the dig
> command?

If I ask it explicitly I don't see it too...From rtanner at linfield.edu  Thu Oct  9 21:25:38 2008
Received: with ECARTIS (v1.0.0; list bind-users); Thu, 09 Oct 2008 21:25:38 +0000 (UTC)
Return-Path: <rtanner at linfield.edu>
X-Original-To: bind-users at webster.isc.org
Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mx.isc.org", Issuer "ISC CA" (verified OK))
	by webster.isc.org (Postfix) with ESMTPS id 64B8A10E449
	for <bind-users at webster.isc.org>; Thu,  9 Oct 2008 21:25:38 +0000 (UTC)
	(envelope-from rtanner at linfield.edu)
Received: from neskowin.linfield.edu (neskowin.linfield.edu [192.147.171.21])
	by mx.isc.org (Postfix) with SMTP id 72F2811408C
	for <bind-users at isc.org>; Thu,  9 Oct 2008 21:21:55 +0000 (UTC)
	(envelope-from rtanner at linfield.edu)
Received: from neskowin.linfield.edu (localhost.localdomain [127.0.0.1])
	by linfield.edu (Postfix) with SMTP id 0EDB15818A
	for <bind-users at isc.org>; Thu,  9 Oct 2008 14:21:55 -0700 (PDT)
Received: from aragorn.linfield.edu (aragorn.linfield.edu [10.219.255.241])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by neskowin.linfield.edu (Postfix) with ESMTP id D9C22580F7
	for <bind-users at isc.org>; Thu,  9 Oct 2008 14:21:54 -0700 (PDT)
Message-ID: <48EE75F2.2040202 at linfield.edu>
Date: Thu, 09 Oct 2008 14:21:54 -0700
From: Rob Tanner <rtanner at linfield.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.17) Gecko/20080914 Lightning/0.8 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: bind-users at isc.org
Subject: RESOLVED: Re: Need help setting up forwarding
References: <48EE4EEC.2070006 at linfield.edu>
In-Reply-To: <48EE4EEC.2070006 at linfield.edu>
Content-type: text/plain
X-Spam-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE
	autolearn=ham version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mx.isc.org
Content-Transfer-Encoding: 8bit
Sender: bind-users-bounce at isc.org
Errors-to: bind-users-bounce at isc.org
Precedence: bulk
List-unsubscribe: <mailto:bind-users-request at isc.org?Subject=unsubscribe>
List-Id: <bind-users.isc.org>
X-List-ID: <bind-users.isc.org>

Found  better solution to the problem.
On 10/9/08 11:35 AM, Rob Tanner wrote:
> Hi,
> I have a web server behind a firewall and in it's own address space that 
> eventually will become a DMZ.  The addresses on the public side of the 
> firewall are not the same as on the private side, and the firewall takes 
> care of the translations.  Here's the problem.  Because we run a proxy 
> service for the library on that server, sometimes the server has to look 
> up it's own address and send a get request to itself.  But what it gets 
> when it looks itself up is its public, in front of the firewall 
> address.  And because it's behind the firewall, it can't reach that address.
>
> Normally, /etc/hosts would be the perfect solution except that the proxy 
> service requires wild card lookups (i.e., *.ezproxy.linfield.edu) and 
> /etc/hosts does not recognize wild cards.  The option I can think of is 
> running a local DNS with forwarding enabled.  There are only 4 IP 
> addresses that the local server will be authoritative for (one 
> in-addr.arpa segment), but it needs to think that it's authoritative for 
> the entire linfield.edu domain but forward any address it can't resolve 
> in that domain (i.e., any hostname that not one of the 4) to one of our 
> regular servers.  And that's what I can't figure out how to do. 
>
> Can this even be done?
>
> Thanks,
>
> Rob Tanner
> UNIX Services Manager
> Linfield College, Oregon
>
>
>
>
>