Archived from groups: microsoft.public.win2000.dns (
More info?)
Yes, this would work for what he's asking. Now, the disclaimer part is just
the same as we have today on the EDNS0 thingy. It is also the same with ehlo
and helo in SMTP. The unicode is RFC-complaint, but not everyone adheres to
RFC.
Now, on to my own disclaimer. I am NOT doing unicode in production. This
should not mean anything to anyone who needs to do it. I'm just saying my
experience with it is limited to PoC in lab and Virtual networks.
--
Sincerely,
Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:eokWUbBVEHA.2544@TK2MSFTNGP10.phx.gbl...
> In news:%23WgHYs%23UEHA.3024@TK2MSFTNGP09.phx.gbl,
> Deji Akomolafe <noemail@akomolafe.com> posted their thoughts, then I
offered
> mine
> > Yes, it does. This is how you get it to work:
> >
http://www.petri.co.il/naming_convention_in_windows_2000_2003_dns.htm
> >
> >
>
> That does have a disclaimer on it about using it outside of a private
> network. Deji, do you think it will work with what the poster has in mind?
>
> --
> Regards,
> Ace
>
> Please direct all replies to the newsgroup so all can benefit.
> This posting is provided "AS-IS" with no warranties and confers no
> rights.
>
> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
> Microsoft Windows MVP - Active Directory
>
> HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
> pig. --
> =================================
>
>