From owner-freebsd-questions@FreeBSD.ORG Wed Feb 9 09:04:03 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 271BB106566B for ; Wed, 9 Feb 2011 09:04:03 +0000 (UTC) (envelope-from bsemene@cyanide-studio.com) Received: from mail.cyanide-studio.com (mail.cyanide-studio.com [62.73.7.64]) by mx1.freebsd.org (Postfix) with ESMTP id B6B198FC16 for ; Wed, 9 Feb 2011 09:04:02 +0000 (UTC) Received: from localhost (unknown [10.1.8.14]) by mail.cyanide-studio.com (Postfix) with ESMTP id 0B4F717BF447 for ; Wed, 9 Feb 2011 09:47:39 +0100 (CET) Received: from mail.cyanide-studio.com ([10.1.8.3]) by localhost (mailguard.cyanide-studio.com [10.1.8.14]) (amavisd-maia, port 10024) with ESMTP id 63173-09 for ; Wed, 9 Feb 2011 09:47:38 +0100 (CET) Received: from [10.1.8.96] (unknown [10.1.8.96]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bsemene@cyanide-studio.com) by mail.cyanide-studio.com (Postfix) with ESMTP id D782E17BF442 for ; Wed, 9 Feb 2011 09:47:38 +0100 (CET) Message-ID: <4D5254AB.5030408@cyanide-studio.com> Date: Wed, 09 Feb 2011 09:47:39 +0100 From: Bastien Semene User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Partial DNS tree X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2011 09:04:03 -0000 Hi everyone, This is not the preferred mailing list to ask this question, but I think people here can easily answer. I've seen in the past that DNS servers can resolve some FQDNs while forwarding (or caching) other resolutions of the same DN. But I can't remember the word qualifying this technology, and had hard time finding this on google. Can someone please point me to the correct direction ? The goal of this is to have some FQDN (i.e. : svn.domain.com) resolved on a local network, and others (i.e. www.domain.com) resolved on the Internet. I think this is the best solution for a subsidiary to have local resources while also can hit remote resources. And it should be easy to maintain. Thank you ! -- Bastien Semene Administrateur Réseau& Système Cyanide Studio - FRANCE