Drewbert
11th June 2012, 11:41 PM
I think it's important that parking companies are ready to go for when Verisign's .com translits go live in the root:
The parking companies could build an automated process (giving Russian as an example here).
10 Go through entire domain portfolio one name at a time...
20 Is it a .com?
30 no? goto 10
40 Does it have cyrillic characters?
50 no? goto 10
60 Create an extra entry in the portfolio (in a subfolder called ".ком") with .ком as the TLD instead of .com and assign the same settings as the .com entry had.
70 goto 10
Have I missed anything?
I certainly want duplicated entires for all my .ком domains in my Parking Co accounts BEFORE .ком goes live in the root because if they're not ready in advance, I'll be losing traffic and revenue, and it's much more efficient for them to automate the process at their end rather than force us to do it manually or upload thousands of new entries and try to duplicate the settings on them all!
The parking companies could build an automated process (giving Russian as an example here).
10 Go through entire domain portfolio one name at a time...
20 Is it a .com?
30 no? goto 10
40 Does it have cyrillic characters?
50 no? goto 10
60 Create an extra entry in the portfolio (in a subfolder called ".ком") with .ком as the TLD instead of .com and assign the same settings as the .com entry had.
70 goto 10
Have I missed anything?
I certainly want duplicated entires for all my .ком domains in my Parking Co accounts BEFORE .ком goes live in the root because if they're not ready in advance, I'll be losing traffic and revenue, and it's much more efficient for them to automate the process at their end rather than force us to do it manually or upload thousands of new entries and try to duplicate the settings on them all!