enable utf8

  • Thread starter Thread starter Guest
  • Start date Start date
Hi,

Thanks for the posting. Windows Server 2000 and 2003 DNS supports almost
any UTF-8 character in a name; however, do not use extended ASCII or UTF-8
characters unless all of the DNS servers in your environment support them.

I did some research and found the following details. Please have a look on
this and confirm whether it meets your requirement or not.

How to Enable
=============
NameCheckFlag
Type: DWORD (Boolean)
Default value: NoKey (Do not write unnecessary NS records)
Function: Specifies the character standard is applied to DNS names.

You can use the NameCheckFlag registry entry to specify the character
standard that is applied to DNS names. The standard determines the
characters that are permitted and the characters that are prohibited in DNS
names . Valid NameCheckFlag entries Value Meaning
0 Permit ANSI characters that comply with the RFCs.
1 Permit ANSI characters that do not comply with the RFCs.
2 Permit multibyte UTF8 characters.
3 Permit all characters.
Change method To change the value of the NameCheckFlag entry, use the DNS
console. Right-click a DNS server, click Properties, click the Advanced
tab, and then click the encoding format you want to use in the Name
checking box. You can also use Dnscmd.exe. Changes are effective
immediately so that you do not have to restart the DNS server. Start method
DNS reads its registry entries only when it starts. You can change entries
while the DNS server is running by using the DNS console or Dnscmd.exe. If
you change entries by editing the registry, the changes are not effective
until you restart the DNS server.

Note Windows 2000 does not add the NameCheckFlag entry to the registry. You
can add it by editing the registry or by using a program that edits the
registry.
NoRecursion
Type: DWORD (Boolean)
Default value: 0
Function: Write NS records to the authority section on a successful
response.

You can use the NoRecursion registry entry to specify if the DNS server
performs recursive resolution to comply with the RecursionDesired bit in
the DNS name query packet header. Recursion occurs only when the value of
the NoRecursion entry is 0 and the RecursionDesired bit is set. Valid
NoRecursion entries Value Meaning
0 Permit ANSI characters that comply with the RFCs.
1 Permit ANSI characters that do not comply with the RFCs.
2 Permit multibyte UTF8 characters.
3 Permit all characters.
You might want to change the value of the NoRecursion entry if clients are
limited to the names on a server, such as in an intranet, or if the server
cannot resolve external names. Change method To change the value of the
NoRecursion entry, use the DNS console. Right-click the server name, click
Properties, and then click the Advanced tab. This entry corresponds to the
Disable Recursion option. You can also use Dnscmd.exe. Changes are
effective immediately so that you do not have to restart the DNS server.

Note Do not change the value of the NoRecursion entry by editing the
registry. Start method DNS reads its registry entries only when it starts.
You can change entries while the DNS server is running by using the DNS
console or Dnscmd.exe. If you change entries by editing the registry, the
changes are not effective until you restart the DNS server.

For more information have a look at
http://support.microsoft.com/?kbid=813964

Thanks,
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top