little problem with url

[missy]

Hi everyones now i have a little problem with the url issue. i have set my domaine back to the x10 account as name.exofire.net when i go to visite www.name.exofire.net exemple doesnt work. i remove the www. and my website appeart another little issue? thanks in advence :happysad:

 

[Brandon]

http://nexteam.exofire.net/ works fine for me?

 

[GFXDude2010]

You're adding the www infront of a sub-domain url? Don't. They're not made for that. You've just gotta' type in the url you're supposed to. Not www. Like Brandon showed, http://nexteam.exofire.net/ is your sites URL. No www.

Hope this helps!

 

[missy]

Oh i see so when i go to my account of x10 i have to set the www. before nexteam? is right?
Edit:

http://nexteam.exofire.net/ works fine for me?

yes that one work but i guess i have to set www. in the account before nexteam my bad maybe..
Edit:
i tryed to put www.nexteam in the text area but doesnt work :/

 

[GFXDude2010]

No... lol there is no www for that website. WWW refers to World Wide Web. Your website is hosted via a Sub-Domain, which sets your website's "name" in place of the www, and uses your host's name after your site's name, then .com, .net, etc.

So, if you register your website as a Sub-Domain (something.x10hosting.com) it WILL NOT have www.

BUT, if you're going to purchase an actual domain, and use x10 as your webhost, your website WILL have WWW infront of the domain that you purchase. Example: www.something.com "Something" would be the name of your website, www is telling the browser that it's worldly viewable, and .com is telling your browser that it's a "Commercial" website.

Got it now? Lol


EDIT: Did you purchase that domain? nexteam.com? You must do this via another website, because x10 doesn't offer domain registeration. Might I recommend signing up for a free account HERE and then purchasing a domain for $6/year?

 

[Fedlerner]

That's not correct. You should be able to acccess your subdomain with the "www." or with out it.
Both work fine for me:
http://www.nexteam.exofire.net/
http://nexteam.exofire.net/

Try: Clear your cache and temp files, flush your DNS, and refresh your page.

 

[GFXDude2010]

=O I stand corrected...

 

[missy]

That's not correct. You should be able to acccess your subdomain with the "www." or with out it.
Both work fine for me:
http://www.nexteam.exofire.net/
http://nexteam.exofire.net/

Try: Clear your cache and temp files, flush your DNS, and refresh your page.

let me try thanks for you'Re help too :happysad:
Edit:
still cannot see by www.nexteam.exofire.net but i can see with http://nexteam.exofire.net its wierd. i have clear all of temps and cache files. cookies too and tryed with 2 browsers. ie6 and maxthon and my 2nd computer does have this same problem

 

[Corey]

You might just have to wait for DNS to resolve for it. (24-72 hours)

 

[missy]

okay i will wait for thanks corey

 

[GFXDude2010]

Did you flush your DNS though?

Go to: Start>Run>(type in): cmd > and in the cmd type: ipconfig /flushdns

That'll flush your DNS. Then as Corey stated, wait for it to completely delete and reslove.

 

[missy]

the page cannot be display on my 2 computer same as with www. without. but i can go on the ftp . :/

and i have try to flush dns and tryed without router

 

[Corey]

It works for me at home and at work. What country are you in?

 

[missy]

canada, but if i change my domain name i can see back this one :/
maybe this domain block me??

( btw i can acess to the ftp but with the ip giving me by cpanel when i was able to see my website )

 

[Johnny]

=O I stand corrected...

yeah i was thinking the same thing, my www works

maybe he just deleted it from his account, either way, its fixed now

 

[missy]

but for me now isint working at all and i keep doesnt understand the problem ...

 

[Corey]

What domain are you trying to access?

 

[missy]

www.nexteam.exofire.net
http://nexteam.exofire.net
the page cannot be display

but i can see the ftp :S

 

[missy]

Corey can i pm u please? its urgently. thanks

 

[Corey]

Sure.

I believe this was caused by a bug in the cPanel update we did two nights ago. This bug was fixed last night.