IETF Logo Mail Archive

Re: Valid charecter set in DNS

Kenneth Porter <shiva@well.com> Thu, 18 April 2002 20:32 UTC

Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21970 for <dnsop-archive@lists.ietf.org>; Thu, 18 Apr 2002 16:32:04 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3/8.12.3) with ESMTP id g3IKB0TB001572 for <dnsop-outgoing@nic.cafax.se>; Thu, 18 Apr 2002 22:11:01 +0200 (MEST)
Received: by nic.cafax.se (8.12.3/8.12.3/Submit) id g3IKB0gW001571 for dnsop-outgoing; Thu, 18 Apr 2002 22:11:00 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from smtp.well.com (smtp.well.com [206.14.209.7]) by nic.cafax.se (8.12.3/8.12.3) with ESMTP id g3IKAvTB001566 for <dnsop@cafax.se>; Thu, 18 Apr 2002 22:10:58 +0200 (MEST)
Received: from uugw.kensingtonlabs.com (uugw.kensingtonlabs.com [65.200.126.98]) by smtp.well.com (8.8.5/8.8.4) with ESMTP id NAA13258; Thu, 18 Apr 2002 13:00:49 -0700 (PDT)
Subject: Re: Valid charecter set in DNS
From: Kenneth Porter <shiva@well.com>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Danny Mayer <mayer@gis.net>, dhiraj Dhiraj <gdhiraj@novell.com>, dnsop@cafax.se, namedroppers@ops.ietf.org
In-Reply-To: <2263.1019109914@brandenburg.cs.mu.OZ.AU>
References: <4.3.1.2.20020417203447.03914a00@pop.gis.net> <2263.1019109914@brandenburg.cs.mu.OZ.AU>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3.99
Date: Thu, 18 Apr 2002 12:59:24 -0700
Message-Id: <1019160050.24326.28.camel@obi-wan.kenlabs.com>
Mime-Version: 1.0
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed, 2002-04-17 at 23:05, Robert Elz wrote:
>     Date:        Wed, 17 Apr 2002 20:38:17 -0500
>     From:        Danny Mayer <mayer@gis.net>
>     Message-ID:  <4.3.1.2.20020417203447.03914a00@pop.gis.net>
> 
>   | It's not part of any RFC for SRV Records.
> 
> Have you ever looked at RFC2782 ?

Don't feel bad, I got burned by this a few months back. The newer RFC
wasn't in the BIND distribution at the time. It specifies the prefixing
of underscores on service and protocol names to avoid collision with
other names in the DNS namespace.

http://www.ietf.org/rfc/rfc2782.txt

v2.23.0 | Report a Bug | By Email