IDN Forums - Internationalized Domain Names  
Home | Advertise on idnforums | Premium Membership

Go Back   IDN Forums - Internationalized Domain Names > IDN Discussions > General Discussion

General Discussion Feel free to talk about anything and everything in this board.

LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 17th August 2010, 11:44 AM
555 555 is offline
ком.ком コム.コム
Join Date: Jan 2006
Posts: 4,141
iTrader: (33)
Rep Power: 1702
555 has disabled reputation
Problem Statement: DNS Resolution of Aliased Names

It was recognized as part of the original specification of the DNS
that a host can have many names; in fact this expectation predates
the DNS, referring to the earlier specification of host names. In
the simplest case for "aliases", Internet users need these multiple
names to be resolved to the same IP address by a DNS server. The
CNAME record [RFC1034], where "CNAME" is an abbreviation for
"Canonical Name", is a way to designate aliases of the "real" or
canonical name of a host. In some cases, CNAME can be used to
produce the necessary association a bundle of variant domain names.
But the CNAME only maps itself, not its descendants; in fact it is
defined to not have descendants, as it is the only name at a node in
the DNS tree and can't exist at the same name as delegation. In the
case of IDN variants, however, it is often desirable that the name
map both itself and its descendants.


The advantage of BNAME is that it would enable a class of "aliasing"
behavior that some operators find desirable, particularly in
preference to some of the provisioning overhead they describe having
to deploy to support potentially large numbers of "bundles" of
variants at multiple levels of the DNS tree. The disadvantage is
that it may not provide the behavior people really want while
requiring the time and resources to code and deploy any new DNS

Alternatively, a proposal has been made that would leave CNAME as
already specified, but eliminating the constraint that a CNAME must
be alone at a node in the DNS tree. This would avoid any coding and
deployment overhead associated with new RRtypes, while obtaining the
desired behavior. Concerns expressed about it, however, include the
possible (but not yet specified) effort required for backwards
compatibility to avoid harm to implementations that expect, and use,
the old behavior.

Last edited by 555; 17th August 2010 at 11:50 AM..
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

All times are GMT. The time now is 02:28 PM.

Site Sponsors
Your ad here
buy t-shirt
מחיר הזהב

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright 2005

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54