From owner-freebsd-current@FreeBSD.ORG Mon Dec 15 03:06:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8274E106564A for ; Mon, 15 Dec 2008 03:06:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 0F1438FC18 for ; Mon, 15 Dec 2008 03:06:00 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 31609 invoked by uid 399); 15 Dec 2008 03:06:00 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 15 Dec 2008 03:06:00 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4945C999.7020307@FreeBSD.org> Date: Sun, 14 Dec 2008 19:06:01 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Larry Rosenman References: <004901c95a1c$5c6b2680$15417380$@org> <493ECA0D.7090901@andric.com> <4945BF21.7080406@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Dimitry Andric , freebsd-current@freebsd.org, Eygene Ryabinkin Subject: Re: Why does host and dig show a ; as \;? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 03:06:01 -0000 Larry Rosenman wrote: > On Sun, 14 Dec 2008, Doug Barton wrote: > >> >> I've never come across this, but if I had to guess I'd say that it does >> so for maximum compatibility with a wide variety of DNS software. >> Remember the robustness principle, "liberal in what you accept, >> conservative in what you send." > > I'm just surprised it prints it that way, but the actual DNS responses > do *NOT* contain the escaping. > > It was a surprise, at least to me, while trying to verify the RR's. > > Turns out the real problem was unrelated, but this still surprised me. After 14 years I'm still surprised by the DNS on a somewhat regular basis. :) Doug -- This .signature sanitized for your protection