You wrote: "From the end-user's perspective, whether you typed in susancrawford.test or [non-ascii script susancrawford].[IDN equivalent of .test], you'd go to the same place." I think that's not quite right. Let me give it a try. The alias is only at the TLD level, not the second-level. For an existing registrant, DNAME gives you new resolutions but only in mix matched pairs of .net and .IDN! and .IDN2, etc. In other words, you have scrawford.net. If Verisign does an IDN DNAME for .NET of the form ".IDN", then "scrawford" will point to the same place in both .NET and in .IDN. Now, "[non-ascii script susancrawford]".IDN would be a new registration. That registration would also resolve in .NET. But just because you have "scrawford.NET" does not mean that DNAME also would give you [non-ascii script susancrawford].[IDN equivalent of .test]. Does that make sense? It may make more sense if I draw a picture. -- Bret