Can I host a xxx.us domain at FutureQuest?

[Tom E.]

I'd like to transfer a client's ".us" domain to FQ (registered with NetSol) and I was wondering if there was any reason I couldn't.

[Bob]

Hello Tom,

If it is an aaa.us to a www.us or yyy.us to zzz.us domain there shouldn't be any problem... BUT a xxx.us now that may not meet the TOS requirements ;)
http://www.FutureQuest.net/Services/TOS/

Seriously FutureQuest hosts many .us domains. The bottom line is if you can point the name servers for a domain to the FutureQuest name servers than we can host it :)

-Bob

[Snarpy]

BUT a xxx.us now that may not meet the TOS requirements=)

Snarpy

[Tom E.]

If it is an aaa.us to a www.us or yyy.us to zzz.us domain there shouldn't be any problem...

But what about the ranges xaa-xxy and xxz-xzz.us?

Thanks for the quick (and funny) reply. It was about as sharp as a page of Oscar Wilde witticisms, rolled to a point, dipped in lemon juice and poked in your eye. (Blackadder, I think)

I think I'll be right at home here....

[Deb]

Wow..so new yet you already realize Bob is like having unsweetened lemonade concentrate in the eye..... I'm impressed.

Additionally, one of the rules of a .US TLD is that "The listed name servers must be located within the United States;"

:QTUSA: FutureQuest's Name Servers are in fact in the U S of A so we're good to go in that area too ;)

Deb
- Not that QT doesn't carry many other flags as well :P

[kitchin]

I just found out that .com names that start with "xn--" are part of a renaming scheme for non-English letters, such as accented letters. It's causing a big security headache (http://forums.mozillazine.org/viewtopic.php?t=215226) for Mozilla. IE has ignored it.. it doesn't implement this new standard yet.

It comes down to this:
www.xn--amazn-mye.com
really means
www.amazon.com
but the a's are in the Cyrillic alphabet or something, They look like a's, but they aren't, so it's a phish!

It's a hard problem to fix without disabling the feature. And then Mozilla found a bug with the disabling switch... and the registrars deserve much of the blame, seems. They aren't supposed to register deceptive names.

[Randall]

It's a hard problem to fix without disabling the feature. And then Mozilla found a bug with the disabling switch... I'm not sure what they mean when they say the switch "doesn't work."

This page has two links, one to theshmoogroup.com, and another to an IDN domain that looks just like it:

http://www.shmoo.com/idn/

Now go to about:config and set network.enableIDN to "false." With IDN turned off, it still looks like theshmoogroup.com -- but when I click on it, Moz tells me that the domain couldn't be found, same as with IE.

And unlike the compreg.dat workaround mentioned in that Mozillazine post, it shouldn't be affected when you install new themes or extensions.

In other browser news, Microsoft has decided to update IE after all (http://news.com.com/Reversal+Next+IE+update+divorced+from+Windows/2100-1032_3-5577263.html).

Randall

[kitchin]

Randall, I haven't tried it, but they say when you restart the browser, it goes back to the default setting. ?) ?)

You should see all the discussion about making up eleborate tables of letters that look alike, or what language groups might be mixed in a single domain name (4 Japanese varieties are OK together, etc.). Or using a better font. Finally they seem to have zeroed in on the registries. As opposed to "registrars", there is just one "registry" for each .suffix. Certain suffixes, notably .com, are notorious for not policing themselves. The standards say confusing names are not allowed. So the fix is to display the xn-- version of the name if it comes from a bad suffix, like .com, but allow the pretty version for a well-managed suffix, like .jp. Whewww... amazing how the specs can be trickier than the code!

Also, Versign is pushing a plugin for IE that implements the xn-- decoding (sell more domains!). But it's closed source, so there's an open source alternative plugin.

[Randall]

Randall, I haven't tried it, but they say when you restart the browser, it goes back to the default setting. Hmm, I see what you mean. It's still set to false, but it's stopped working. That sucks.

Randall:ytguido:

[kitchin]

Hecka of a smiley!

[Randall]

Hecka of a smiley! Yes, the FQ smiley elves have been busy.

:ytpopcrn:

Randall

[TVB]

:ytpopcrn: :ytpopcrn: :ytpopcrn: :ytpopcrn: :ytpopcrn:

Hey Dank,

How's the reseller thing...

doh...

Betsy http://www.bodieslikeours.org/forums/images/smilies/brick.gif

[Randall]

Now, why do you suppose that smiley made me think of you? :wink:

Randall