Hi Artem and welcome to our,

Yes this is possible by adding a domain hostnames to the node in your case add http://sincity.mysite.com/ or http://www.sincity.mysite.com/ and perhaps you want to have both so you can make a 301 redirect depening on which url google has indexed most from your site, non www or www.

You can check this make a site search in google like, in the google search field write: site:mysite.com, check how many pages that are indexed, then do the same for www.mysite.com.

Click on the three dots, and click the option do something else, then choose culture and hostnames. Add the http://sincity.mysite.com to the node.

Hope this helps, and make sense, if you further questions do this don't hesitate to ask again

/Dennis

Hi Artem and welcome to our :)

If I understand your question correctly then you should be able to go to the node where and right click and then setup a hostname pointing to your desired url. You will of course also need to set it up as a binding on the IIS site.

Does this make any sense? And if so...does it work?

/Jan

Hello,

The posts above are already providing good information, but there is one downside. Once your node has it's down domain it's not accessible anyone through a higher node.

So

- Website
-- Page1
--- Page2

By default the url would be website.com/page1/page2/ but if you add a domain to page2 that will be accessible through page2.com, but it won't be accessible anymore by website.com/page1/page2/. I wrote some more info about that here: http://24days.in/umbraco/2014/urlprovider-and-contentfinder/. Read the "The possibilities" part.

Jeroen

Thanks for your answers! Yes, i've found this 'culture and hostnames', added a domain 'http://sincity.mysite.com/' there, and the node became 'invisible' on 'http://mysite.com/sincity/' -> that all is 'Ok'.

But unfortunately, 'http://sincity.mysite.com/' is not availiable too(

As were mentioned above, the cause may be in IIS / hosting settings... So now I need to find anybody who had the same task at the same hosting company - I use Arvixe.com ('personal class asp pro').

So... If I got the answer - I will definitely describe it. And of course you are welcome to help me :)

Well...)

At Arvixe hosting side I had to create new website pointer 'sincity' under my site 'mysite.com' - that gave me 'sincity.mysite.com' pointer. Then I removed my rewirite rules (see below) from web.config and my page became availiable through the web. It worked in Chrome and IE10, but not in FF(

Although the thread question is resolved, now I'm configuring my permanent redirects (I'm not so good neither in regex nor in redirects)... As usual, I will publish my solution.

My old rewrite rules:

<rewrite>
<rules>
    <clear />
    <rule name="Redirect to non-www" stopProcessing="true">
        <match url="(.*)" negate="false"></match>
        <conditions>
            <add input="{HTTP_HOST}" pattern="^mysite\.com$" negate="true"></add>
        </conditions>
        <action type="Redirect" url="http://mysite.com/{R:1}" redirectType="Permanent"></action>
    </rule>
</rules>

And if anybody has better solution for 301 redirect from www to non-www - You are welcome!))

You could try the SEO Checker package. It's not free, but it can help with a lot of SEO stuff including a redirect from www to non-www.

Jeroen

is working on a reply...