Internationalized domain name system with iterative conversion

• US 20040044791A1
• Filed: 11/22/2002
• Published: 03/04/2004
• Est. Priority Date: 05/22/2001
• Status: Abandoned Application

• Current Assignee: Daniel G. Pouzzner
• Original Assignee: Daniel G. Pouzzner
• Inventors: Pouzzner, Daniel G.
• Application Number:
  US10/296,105
• Publication Number:
  US 20040044791A1
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 40/12 Use of codes for handling textual entities
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Abstract

A system, method, and logic for managing data, including a database for implementing a key value operation, such as DNS resource record lookup, with a key having a predetermined encoding, such as Unicode. Also provided is an iterative converter, for iteratively converting the key from each of multiple encodings to the predetermined encoding before performing the key value operation with each converted key. The system may further include a validator for verifying that a syntax of each converted key is valid and a normalizer for normalizing each converted key.

Claims

1. A system for managing data, comprising:

a database for implementing a key value operation with a key having a predetermined encoding; and

means for iteratively converting the key from each of a plurality of encodings to the predetermined encoding before performing the key value operation with each converted key.

2. The system recited in claim 1, wherein the key value operation is selected from the group consisting of a key value insertion operation and a key value retrieval operation.

3. The system recited in claim 2, wherein the key value operation accommodates at least one wildcard.

4. The system recited in claim 1, further comprising means for verifying that a syntax of the converted key is valid.

5. The system recited in claim 1, further comprising means for normalizing the converted key.

6. The system recited in claim 1, wherein the encodings are character encodings.

7. The system recited in claim 6, wherein the character encodings are associated with the same language.

8. The system recited in claim 6, wherein the predetermined character encoding is Unicode.

9. The system recited in claim 6, further comprising means for providing image data corresponding to a result of the key value operations.

10. The system recited in claim 1, wherein the database includes name data.

11. The system recited in claim 1, wherein the database includes location data.

12. The system recited in claim 10, wherein the database includes location data.

13. The system recited in claim 10, wherein the name data includes domain name data.

14. The system recited in claim 11, wherein the location data includes IP address data.

15. The system recited in claim 12, wherein the name data includes domain name data and the address data includes IP address data.

27. The method recited in claim 10, wherein the database includes location data.

30. The method recited in claim 27, wherein the name data includes domain name data and the address data includes IP address data.

16. A method for managing data, comprising the steps of:

implementing a key value operation in a database with a key having a predetermined encoding; and

iteratively converting the key from each of a plurality of encodings to the predetermined encoding before performing the key value operation with each converted key.

17. The method recited in claim 16, wherein the key value operation is selected from the group consisting of a key value insertion operation and a key value retrieval operation.

18. The method recited in claim 17, wherein the key value operation accommodates at least one wildcard.

19. The method recited in claim 16, further comprising the step of verifying that a syntax of the converted key is valid.

20. The method recited in claim 16, further comprising the step of normalizing the converted key.

21. The method recited in claim 16, wherein the encodings are character encodings.

22. The method recited in claim 21, wherein the character encodings are associated with the same language.

23. The method recited in claim 21, wherein the predetermined character encoding is Unicode.

24. The method recited in claim 21, further comprising the step of providing image data corresponding to a result of the key value operations.

25. The method recited in claim 16, wherein the database includes name data.

26. The method recited in claim 16, wherein the database includes location data.

28. The method recited in claim 25, wherein the name data includes domain name data.

29. The method recited in claim 26, wherein the location data includes IP address data.

31. A computer readable medium for managing data, comprising:

logic for implementing a key value operation in a database with a key having. a predetermined encoding; and

logic for iteratively converting the key from each of a plurality of encodings to the predetermined encoding before performing the key value operation with each converted key.

32. The logic recited in claim 31, wherein the key value operation is selected from the group consisting of a key value insertion operation and a key value retrieval operation.

33. The logic recited in claim 32, wherein the key value operation accommodates at least one wildcard.

34. The logic recited in claim 31, further comprising logic for verifying that a syntax of the converted key is valid.

35. The system recited in claim 31, further comprising logic for normalizing the converted key.

36. The logic recited in claim 31, wherein the encodings are character encodings.

37. The logic recited in claim 36, wherein the character encodings are associated with the same language.

38. The logic recited in claim 36, wherein the predetermined character encoding is Unicode.

39. The logic recited in claim 36, further comprising logic for providing image data corresponding to a result of the key value operations.

40. The logic recited in claim 31, wherein the database includes name data.

41. The logic recited in claim 31, wherein the database includes location data.

42. The logic recited in claim 40, wherein the database includes location data.

43. The logic recited in claim 42, wherein the name data includes domain name data.

44. The logic recited in claim 42, wherein the location data includes IP address data.

45. The logic recited in claim 42, wherein the name data includes domain name data and the addresses data includes IP address data.

46. A system for managing data, comprising:

a database for implementing a key value operation with a key having a predetermined encoding; and

an iterative converter for converting the key from one of a plurality of encodings to the predetermined encoding before performing the key value operation with each converted key.

47. The system recited in claim 46, wherein the key value operation is selected from the group consisting of a key value insertion operation and a key value retrieval operation.

48. The system recited in claim 47, wherein the key value operation accommodates at least one wildcard.

49. The system recited in claim 46, further comprising a key validator for verifying that a syntax of the converted key is valid.

50. The system recited in claim 46, further comprising a key normalizer for normalizing the converted key.

51. The system recited in claim 46, wherein the encodings are character encodings.

52. The system recited in claim 51, wherein the character encodings are associated with the same language.

53. The system recited in claim 51, wherein the predetermined character encoding is Unicode.

54. The system recited in claim 46, further comprising an image generator for providing image data corresponding to a result of the key value operation.

55. The system recited in claim 46, wherein the database includes name data.

56. The system recited in claim 46, wherein the database includes location data.

57. The system recited in claim 55, wherein the database includes location data.

58. The system recited in claim 55, wherein the name data includes domain name data.

59. The system recited in claim 56, wherein the location data includes IP address data.

60. The system recited in claim 57, wherein the name data includes domain name data and the address data includes IP address data.

61. A data server, comprising:

means for receiving a request including an encoded portion;

means for iteratively converting the encoded portion of the request from each of a plurality of encodings to a predetermined encoding; and

means for responding to the request based upon at least one of the converted portions having the predetermined encoding.

62. The server recited in claim 61, further comprising means for verifying a syntax of each of the converted portions.

63. The server recited in claim 61, further comprising means for normalizing each of the converted portions.

64. The server recited in claim 61, wherein the encodings are character encodings.

65. The server recited in claim 64, wherein the character encodings are associated with the same language.

66. The server recited in claim 64, wherein the predetermined character encoding is Unicode.

67. The server recited in claim 61, wherein the response includes image data.

68. The server recited in claim 61, wherein the server is a daemon.

69. The server recited in claim 68, wherein the daemon is subsumed in a NAMED portion of the Berkeley Internet Name Domain software.

70. The server recited in claim 61, wherein the server is selected from the group consisting of a file server, a Network File System server, a Network Information Service server, a Domain Name System server, a WHOIS server, a File Transfer Protocol server, a Hyper Text Transfer Protocol server, a Simple Mail Transfer Protocol server, and a Lightweight Directory Access Protocol server.

192. The server recited in claim 61, wherein the response includes multiple conversions of the encoded portion.

71. A method of implementing a data service, comprising the steps of:

receiving a request including an encoded portion;

iteratively converting the encoded portion of the request from each of a plurality of encodings to a predetermined encoding; and

responding to the request based upon at least one of the converted portions having the predetermined encoding.

72. The method recited in claim 71, further comprising the step of verifying a syntax of each of the converted portions.

73. The method recited in claim 71, further comprising the step of normalizing each of the converted portions.

74. The method recited in claim 71, wherein the encodings are character encodings.

75. The method recited in claim 74, wherein the character encodings are associated with the same language.

76. The method recited in claim 74, wherein the predetermined character encoding is Unicode.

77. The method recited in claim 74, wherein the response includes image data.

78. The method recited in claim 71, wherein the service is a daemon.

79. The method recited in claim 78, wherein the daemon is subsumed in a NAMED portion of the Berkeley Internet Name Domain softaware.

80. The method recited in claim 71, wherein the data service follows a protocol selected from the group consisting of a Network File System protocol, a Network Information Service protocol, a Domain Name System protocol, WHOIS protocol, File Transfer Protocol, Hyper Text Transfer Protocol, a Simple Mail Transfer Protocol, and a Lightweight Directory Access Protocol.

193. The method of implementing a data service recited in claim 71, wherein the response includes multiple conversions of the encoded portion.

81. A computer readable medium for implementing data service, comprising:

logic for receiving a request including an encoded portion;

logic for iteratively converting the encoded portion of the request from each of a plurality of encodings to a predetermined encoding; and

logic for responding to the request based upon at least one of the converted portions having the predetermined encoding.

82. The server recited in claim 81, further comprising logic for verifying a syntax of each of the converted portions.

83. The server recited in claim 81, further comprising logic for normalizing each of the converted portions.

84. The server recited in claim 81, wherein the encodings are character encodings.

85. The server recited in claim 84, wherein the character encodings are associated with the same language.

86. The server recited in claim 84, wherein the predetermined character encoding is Unicode.

87. The server recited in claim 84, wherein the response includes image data.

88. The server recited in claim 81, wherein the server is a daemon.

89. The server recited in claim 88, wherein the daemon is subsumed in a NAMED portion of the Berkeley Internet Name Domain software.

90. The server recited in claim 81, wherein the server is selected from the group consisting of a file server, a Network File System server, a Network Information Service server, a Domain Name System server, a WHOIS server, a File Transfer Protocol server, a Hyper Test Transfer Protocol server, a Simple Mail Transfer Protocol server, and a Lightweight Directory Access Protocol server.

194. The computer readable medium recited in claim 81, wherein the response includes multiple conversions of the encoded portion.

91. A system for implementing the DNS protocol, comprising:

a name server for receiving a query including an encoded domain name expression;

means for iteratively converting the encoded domain name expression from each of a plurality of character encodings to a predetermined character encoding; and

means for providing a response to the query based upon at least one of the converted domain name expressions having the predetermined character encoding.

92. The system recited in claim 91, wherein the response includes data representing a second domain name expression.

93. The system recited in claim 92, wherein the second domain name expression is a fully-qualified domain name expression.

94. The system recited in claim 92, wherein the data includes image data.

95. The system recited in claim 91, wherein the response includes an HTTP response.

96. The system recited in claim 91, wherein the HTTP response includes a redirection status code.

97. The system recited in claim 91, further comprising means for providing the query to the name server.

98. The system recited in claim 97, wherein the providing means includes a second name server having a wildcard resource record for directing the query to the first name server.

99. The system recited in claim 91, further comprising means for verifying a syntax of each converted domain name expression.

100. The system recited in claim 91 wherein the each of the plurality of character encodings are associated with the same language.

101. A system for implementing the Domain Name System (DNS) protocol in distributed name space, comprising a name server for mapping a queried domain name expression encoded with an initially-undetermined character map to a resource record.

102. The system recited in claim 101 wherein said initially-undetermined character map includes characters which are not DNS-legal.

103. The system recited in claim 101 wherein said initially-undetermined character map includes non-ASCII characters.

104. The system recited in claim 101 including modified code operating in conjunction with the Berkeley Internet Name Domain (“

BIND”

) implementation of the DNS protocol.

105. The system recited in claim 101 further comprising a Referral Domain Name Service for determining whether the queried domain name expression contains a 7-bit DNS-legal character string, 8-bit DNS-legal character string, or another type of character string.

106. The system recited in claim 101 wherein the Referral Domain Name Service also determines whether said queried domain name expression contains a special character string.

107. The system recited in claim 101, further comprising a Referral Domain Name Service for determining whether the queried domain name expression contains an 8-bit DNS-legal character strings and for referring said 8-bit DNS-legal expression to a Unicode Validation and Canonicalization Engine for determining whether the referred 8-bit DNS-legal expression has been encoded with a universal character map.

108. The system recited in claim 107, wherein, prior to mapping, said Unicode Validation and Canonicalization Engine also validates, downcases, and decomposes said 8-bit DNS-legal expression which has been determined to be encoded with the Unicode universal character map.

109. The system recited in claim 101, further comprising a Legacy Unicodification Trial Engine for converting said queried domain name expression to a universal character map from another character map prior to attempting a look-up of the converted expression.

110. The system recited in claim 109, wherein, after an unsuccessful mapping attempt, the Legacy Unicodification Trial Engine converts the queried domain name expression to a universal character map from another different character map prior to attempting another look-up of the converted expression.

111. The system recited in claim 105, further comprising a Legacy Unicodification Trial Engine for converting said queried domain name expression containing said other type of string to a universal character map prior to attempting a look-up of the converted expression.

112. The system recited in claim 109, wherein, after an unsuccessful look-up, the Legacy Unicodification Trial Engine converts the queried domain name expression to Unicode from another different character map prior to attempting another look-up of the converted expression.

113. A virtual internationalized domain name system, comprising a URI forwarding agent for attempting a mapping of a queried domain name expression that is encoded with an initially-undetermined character map to a corresponding DNS-legal domain name expression.

114. The virtual internationalized domain name system recited in claim 113 wherein said queried domain name expression includes at least one DNS-illegal character.

115. The virtual internationalized domain name system recited in claim 113 wherein said initially-undetermined character map is a non-ASCII character map.

116. The virtual internationalized domain name system recited in claim 115 wherein said initially-undetermined character map includes a binary code unit that is longer than seven bits.

117. The virtual internationalized domain name system recited in claim 116 wherein said queried domain name expression includes at least one DNS-illegal character.

118. The virtual internationalized domain name system recited in claim 113 further comprising a name server with a wildcard resource record for referring the queried domain name expression to the URI forwarding agent.

119. The virtual internationalized domain name system as recited in claim 113 wherein said URI forwarding agent includes a first module for verifying that the queried domain expression is encoded with a Unicode/UTF-8 character map and canonicalizing the verified expression prior to said attempted mapping.

120. The virtual internationalized domain system as recited in claim 119 wherein said canonicalizing uses Normalization Form KD.

121. The virtual internationalized domain name system as recited in claim 113 wherein said URL forwarding agent includes a module for converting the queried domain name expression to a preferred character map prior to said attempted mapping.

122. The virtual internationalized domain name system as recited in claim 121 wherein said preferred character map is a universal character map.

123. The virtual internationalized domain name system as recited in claim 122 wherein the universal character map is Unicode with transformation format UTF-8.

124. The virtual internationalized domain name system as recited in claim 119 wherein said URL forwarding agent includes a second module for converting the queried domain name expression to a preferred character map prior to a second attempted mapping.

125. The virtual internationalized domain name system as recited in claim 124 wherein the preferred character map is Unicode with transformation format UTF-8.

126. The virtual internationalized domain name system as recited in claim 125 wherein the first module also verifies and canonicalizes the encoding of the converted expression prior said second attempted mapping.

127. The virtual internationalized domain name system recited in claim 126 further comprising a name server with a wildcard resource record for referring the queried domain name expression to the URI forwarding agent.

128. The virtual internationalized domain name system as recited in claim 127 wherein, when said second attempted mapping is unsuccessful, the URI forwarding agent maps the queried domain name expression to a predetermined domain name expression.

129. A method of implementing a virtual internationalized domain name system comprising the steps of:

receiving a query with a domain name expression that is encoded with an initially-undetermined character map; and

attempting a mapping of the queried domain name expression to a DNS-legal domain name expression.

130. The method of implementing a virtual internationalized domain name system recited in claim 129 wherein said queried domain name expression includes at least one DNS-illegal character.

131. The method of implementing. a virtual internationalized domain name system recited in claim 129 wherein said initially-undetermined character map is a non-ASCII character map.

132. The method of implementing a virtual internationalized domain name system recited in claim 129 wherein said initially-undetermined character map includes a binary code unit that is longer than seven bits.

133. The virtual internationalized domain name system recited in claim 132 wherein said queried domain name expression includes at least one DNS-illegal character.

134. The method of implementing a virtual internationalized domain name system as recited in claim 129 wherein during said receiving step, the queried domain name expression is received from a name server in response to finding a wildcard resource record in a zone file of the name server.

135. The method of implementing a virtual internationalized domain name system as recited in claim 129 further comprising the step of verifying whether the queried domain expression is encoded with a Unicode/UTF-8 character map and canonicalizing the verified expression prior to said attempted mapping.

136. The method of implementing a virtual internationalized domain name system as recited in claim 129 further comprising the step of converting the queried domain name expression to a universal character map before said attempted mapping step.

137. The method of implementing a virtual internationalized domain name system as recited in claim 136 wherein said universal character map is Unicode/UTF-8.

138. The method of implementing a virtual internationalized domain name system as recited in claim 137 further comprising the step of verifying whether the converted domain name expression is encoded with a Unicode/UTF-8 character map and canonicalizing the verified expression prior to said attempted mapping.

139. The method of implementing a virtual internationalized domain name system as recited in claim 135 further comprising the step of, after an unsuccessful verification, converting the queried domain name expression to a universal character map before said attempted a second mapping of the queried domain name expression to a DNS-legal domain name expression.

140. The method of implementing a virtual internationalized domain name system as recited in claim 139 wherein said universal character map is Unicode/UTF-8 and said canonicalization uses Normalization Form KD.

141. The method of implementing a virtual internationalized domain name system as recited in claim 140 further comprising the step of verifying whether the converted domain name expression is encoded with a Unicode/UTF-8 character map and canonicalizing the verified expression prior to said second attempted mapping of the converted domain name expression.

142. The method of implementing a virtual internationalized domain name system as recited in claim 141 wherein during said receiving step, the queried domain name expression is received from a name server in response to finding a wildcard resource record in a zone file of the name server.

143. The method of implementing a virtual internationalized domain name system as recited in claim 142 further comprising the step of, when all attempted mappings are unsuccessful, mapping the queried domain name expression to a predetermined domain name expression.

144. A virtual internationalized domain name system, comprising a name server with a wildcard resource record for referring a queried domain name expression that is encoded with an initially-undetermined character map expression to a URI forwarding agent.

145. The virtual internationalized domain name system recited in claim 144 wherein said queried domain name expression includes at least one DNS-illegal character.

146. The virtual internationalized domain name system recited in claim 144 wherein said initially-undetermined character map is a non-ASCII character map.

147. The virtual internationalized domain name system recited in claim 146 wherein said initially-undetermined character map includes a binary code unit that is longer than seven bits.

148. The virtual internationalized domain name system recited in claim 147 wherein said queried domain name expression includes at least one DNS-illegal character.

149. A method of implementing a virtual internationalized domain name system, comprising the steps of:

receiving a query with a domain name expression that is encoded with an initially-undetermined character map; and

referring the query to a URI forwarding agent for mapping the queried domain name expression to another domain name expression.

150. The method of implementing a internationalized domain name system recited in claim 149 wherein said queried domain name expression includes at least one DNS-illegal character.

151. The method of implementing a virtual internationalized domain name system recited in claim 149 wherein said initially-undetermined character map is a non-ASCII character map.

152. The method of implementing a virtual internationalized domain name system recited in claim 151 wherein said initially-undetermined character map includes a binary code unit that is longer than seven bits.

153. The method of implementing a virtual internationalized domain name system recited in claim 152 wherein said queried domain name expression includes at least one DNS-illegal character.

154. The method of implementing a virtual internationalized domain name system recited in claim 153 wherein said other domain name expression is DNS-legal.

155. A URI forwarding agent arranged to map a queried domain name expression that is encoded with an initially-undetermined character map to a corresponding DNS-legal domain name expression.

156. The URI forwarding agent recited in claim 155 wherein said queried domain name expression includes at least one DNS-illegal character.

157. The URI forwarding agent recited in claim 155 wherein said initially-undetermined character map is a non-ASCII character map.

158. The URI forwarding agent recited in claim 157 wherein said initially-undetermined character map includes a binary code unit that is longer than seven bits.

159. The URI forwarding agent recited in claim 158 wherein said queried domain name expression includes at least one DNS-illegal character.

160. The URI forwarding agent recited in claim 155, further comprising a first module for verifying that the queried domain expression is encoded with a Unicode/UTF-8 character map and for canonicalizing the verified expression prior to a first attempt at said mapping.

161. The URI forwarding agent recited in claim 155 further comprising a module for converting the queried domain name expression to a preferred character map prior to said. mapping.

162. The URI forwarding agent recited in claim 161 wherein said preferred character map is a universal character map.

163. The URI forwarding agent recited in claim 162 wherein the universal character map is Unicode.

164. The URI forwarding agent recited in claim 163 wherein the universal character map is Unicode/UTF-8.

165. The URI forwarding agent recited in claim 160 wherein said URL forwarding agent includes a second module for converting the queried domain name expression to a preferred character map prior to a second attempt at said mapping.

166. The URI forwarding agent recited in claim 165 wherein the preferred character map is Unicode/UTF-8.

167. The URI forwarding agent recited in claim 166 wherein the first module also verifies and canonicalizes the encoding of the converted expression using Normalization Form KD prior said second attempted mapping.

168. The URI forwarding agent recited in claim 167 wherein, when said second attempted mapping is unsuccessful, the URI forwarding agent maps the queried domain name expression to a predetermined domain name expression.

169. A system for accommodating multiple character encodings in a keyed database retrieval and insertion operation without having prior knowledge of the particular character encoding that is used for each key, the system comprising:

a database for implementing a key value retrieval using a universal character encoding;

a key validator for determining whether the key follows an acceptable pattern for the universal character encoding;

an encoding converter for transforming the key to the universal character encoding from a different character encoding when the key does not follow an acceptable pattern in the universal character encoding; and

an iterator for controlling the database, key validator, and encoding converter to perform in an iterative fashion using a plurality of said different character encodings.

170. The system recited in claims 169, further comprising a transformed key validator for determining whether the transformed key follows an acceptable pattern for the universal character encoding.

171. The system recited in claim 169 wherein said key validator also normalizes the key.

172. The system recited in claim 171, wherein said normalization includes downcasing and decomposition.

173. The system recited in claim 172, wherein said universal character code is Unicode and said normalization is Normalization Form KC.

174. The system recited in claim 172, wherein said universal character code is Unicode and said normalization is Normalization Form KD.

175. The system recited in claim 169 wherein said database includes DNS resource records.

176. The system recited in claim 171 wherein said database includes DNS resource records.

177. The system recited in claim 174 wherein said database includes DNS resource records.

178. The system recited in claim 175 subsumed into one of the group consisting of a DNS service, a virtual hosting web service, a WHOIS service, a conversion service, a registration service, and a URL forwarding agent.

179. A system for implementing the Domain Name System (DNS) protocol in distributed name space, comprising a name server for mapping a queried domain name expression encoded with an initially-undetermined character map to a resource record.

180. The system recited in claim 179 wherein said initially-undetermined character map includes characters which are not DNS-legal.

181. The system recited in claim 179 wherein said initially-undetermined character map includes non-ASCII characters.

182. The system recited in claim 179 including modified code operating in conjunction with the Berkeley Internet Name Domain (“

BIND”

) implementation of the DNS protocol.

183. The system recited in claim 179 further comprising a Referral Domain Name Service for determining whether the queried domain name expression contains a 7-bit DNS-legal character string, 8-bit DNS-legal character string, or another type of character string.

184. The system recited in claim 179 wherein the Referral Domain Name Service also determines whether said queried domain name expression contains a special character string.

185. The system recited in claim 179, further comprising a Referral Domain Name Service for determining whether the queried domain name expression contains an 8-bit DNS-legal character strings and for referring said 8 bit DNS-legal expression to a Unicode Validation and Canonicalization Engine for determining whether the referred 8-bit DNS-legal expression has been encoded with a universal character map.

186. The system recited in claim 185, wherein, prior to mapping, said Unicode Validation and Canonicalization Engine also validates, downcases, and decomposes said 8-bit DNS-legal expression which has been determined to be encoded with the Unicode universal character map.

187. The system recited in claim 179, further comprising a Legacy Unicodification Trial Engine for converting said queried domain name expression to a universal character map from another character map prior to attempting a look-up of the converted expression.

188. The system recited in claim 187, wherein, after an unsuccessful mapping attempt, the Legacy Unicodification Trial Engine converts the queried domain name expression to a universal character map from another different character map prior to attempting another look-up of the converted expression.

189. The system recited in claim 183, further comprising a Legacy Unicodification Trial Engine for converting said queried domain name expression containing said other type of string to a universal character map prior to attempting a look-up of the converted expression.

190. The system recited in claim 187, wherein, after an unsuccessful look-up, the Legacy Unicodification Trial Engine converts the queried domain name expression to Unicode from another different character map prior to attempting another look-up of the converted expression.

191. A Network Information Center, comprising:

a registration web server;

a relational database management system; and

a system for implementing the Domain Name System (DNS) protocol in distributed name space with a name server for mapping resource records to queried domain name expressions that are encoded with any initially-undetermined character map.

195. A conversion server, comprising:

means for receiving a string of characters from a client;

means for converting the string of characters from each of a plurality of encodings to a predetermined encoding; and

means for providing each of the converted strings to the client.

196. The conversion server recited in claim 195, wherein the encodings are character encodings.

197. The conversion server recited in claim 196, wherein the string of characters is a domain name expression in an initially-undetermined character encoding.

198. The conversion server recited in claim 197, wherein the predetermined character encoding is Unicode.

199. A method of implementing a conversion service, comprising the steps of:

receiving a string of characters from a client;

converting the string of characters from each of a plurality of encodings to a predetermined encoding; and

providing each of the converted strings to the client.

200. The method recited in claim 199, wherein the encodings are character encodings.

201. The method recited in claim 200, wherein the string of characters is a domain name expression in an initially-undetermined character encoding.

202. The method recited in claim 201, wherein the predetermined character encoding is Unicode.

203. A computer readable medium for implementing a conversion service, comprising:

logic for receiving a string of characters from a client;

logic for converting the string of characters from each of a plurality of encodings to a predetermined encoding; and

logic for providing each of the converted strings to the client.

204. The computer readable medium recited in claim 203, wherein the encodings are character encodings.

205. The computer readable medium recited in claim 204, wherein the string of characters is a domain name expression in an initially-undetermined character encoding.

206. The computer readable medium recited in claim 205, wherein the predetermined character encoding is Unicode.

207. A conversion server, comprising:

an input device for receiving a string of characters;

a converter for converting the string of characters from each of a plurality of encodings to a predetermined encoding; and

an output device for providing each of the converted strings to a client.

208. The conversion server recited in claim 207, wherein the encodings are character encodings.

209. The conversion server recited in claim 208, wherein the string of characters is a domain name expression in an initially-undetermined character encoding.

210. The conversion server recited in claim 209, wherein the predetermined character encoding is Unicode.

211. The conversion server recited in claim 210, further comprising a validator for verifying that a syntax of each converted domain name is valid.

212. The conversion server recited in claim 210, further comprising a normalizer for normalizing each converted domain name.

213. The conversion server recited in claim 210, wherein the plurality of encodings is identified in the request.