NameSilo

Problems Registering Emoji on Godaddy Iā¤ļø.ws

Located in Domain Registrar Reviews started by Basicgravity, May 7, 2018.

Replies:
7
Views:
378

  1. Basicgravity

    Basicgravity Established Member

    Posts:
    135
    Likes Received:
    44
    In February, we registered šŸ•šŸ„§.WS via Godaddy's Iā¤ļø.ws emoji registration platform. Though the domain is in our account, the website doesn't resolve or forward properly. After sending numerous requests to GD tech staff to fix, they have only stated that they have sent my request for further review. They have ignored my most recent request for follow up. This is never a good sign.

    As the original request was early March, there might be some glitches that Godaddy has not resolved in their emoji registration platform.
    That said, šŸ„§.WS seems to have no problem resolving to a sales platform site.

    Has anyone else had problems with emoji domains?
     
    The views expressed on this page by users and staff are their own, not those of NamePros.
  2. šŸ•šŸ„§.ws resolves to http://xn--vi8he1h.ws/ - and returns HTTP Error 400. The request hostname is invalid. This could be because to the above url is not correctly binded to the webserver. Fixing the problem will all depend on your setup.

    Are you using Godaddy's web hosting, another hosting service, or a dedicated server?
     
  3. Basicgravity

    Basicgravity Established Member

    Posts:
    135
    Likes Received:
    44
    Thank you. Well, we registered on Godaddy and forward to a landing site. The landing site holds the domains that are not in use for other reasons and, has no problem. I just checked our GD account. There is no forwarding problems. I also checked other šŸ„§ combinations. šŸ’šŸ„§.ws is used but does not resolve. šŸ„§.ws goes to a Godaddy sales site and seems to have no problem.

    None of our other forwards - including emojis - have issues. This is especially troublesome as we want to use this for a client's shop.


     
  4. Basicgravity

    Basicgravity Established Member

    Posts:
    135
    Likes Received:
    44
  5. Is this a custom landing page you have on a hosting account or dedicated server? If so it looks like you are missing a binding for http://xn--vi8he1h.ws/ . Maybe a typo on that end?

    I would have to dig into where the 400 is coming from. GD or your server before I could say it is definitely godaddy's issue.

    If It is godaddy's issue - normally deleting the forwarding, and then putting it back would solve.

    Another way to resolve is to delete the forwarding and create an A record to the IP if it is static.
     
  6. Actually for šŸ’© and giggles:

    Leave your forwarding as is, and set your nameservers to
    NS47.DOMAINCONTROL.COM
    NS48.DOMAINCONTROL.COM

    They return a different IP which is the one that is working on your other sites. Worth a try.

    Please note it will take a while for DNS records to propagate.
     
  7. Basicgravity

    Basicgravity Established Member

    Posts:
    135
    Likes Received:
    44
    Haha

    I will try your easy solution first. If is doesn't work, I will fiddle with the nameservers. The landing page is static; nothing fancy.Then I will post again with the result.

    Thank you for your suggestions...


     

Want to reply or ask your own question?

It only takes a minute to sign up ā€“ and it's free!

Share This Page

Lysted
  1. NamePros uses cookies and similar technologies. By using this site, you are agreeing to our privacy policy, terms, and use of cookies.
    Dismiss Notice
Loading...