Tag Info

New answers tagged

2

Without the CNAME, you would need an A record for the www-subdomain instead, otherwise DNS resolution for www.example.com won't work and the request won't reach your server. You will also need the ServerAlias, because even when using CNAME, the host header in the HTTP request won't change, so it will still be www.example.com and you need to tell ...


0

It don't works with CNAME records. A CNAME only tells it to use the same DNS records as the target, it does not tell your HTTP server (Apache) that when it sees the CNAME domain that it should treat it the same as the CNAME target. There's several options but essentially you need to specify that xyz.com is an alias of abc.projects.domain.com somehow. ...


0

We figured it out. We had to add the alias name to the server's hosts file.


4

This is almost certainly caused by something in your application, or web server configuration that is dependent on the hostname. You should talk to the system administrator and/or developer in charge of those things. Things to look for: Absolute links that could be causing XSS errors when accessed through an alternate domain name Use of any of the ...


0

Ideally run your new HelpDesk application in its own web site, independent of the existing default site. Then just use the host header binding to match your cname. If you have to run it under the existing site, you have to trick a bit. You can not point a cname or any DNS entry directly to a subdirectory of a website. Create a second site with the host ...


5

DNS has nothing to do with this. You need to edit the IIS site in question to accept requests for that host header. Using IIS Manager, open up the Sites node and choose the site you want the host header to work on. In the Actions pane, click Bindings. Then choose the binding you want to add a host header to and click Add. Type in a host header, for example ...


2

CNAME *, www -> ultimately resolving to "foo.com/clientmaintenance.html" No, that's not how DNS works. DNS CNAME (and ultimately A/AAAA) records resolve names to IP addresses, and that's where DNS stops. What you're proposing requires HTTP, which is a completely different protocol and application. That said, you could create a simple vhost that ...


0

I just wanted to point out that you need to add all of the CNAME redirects chained to your Azure redirection, that are being used by your users. Example: Domain A redirects to B which redirects to C which redirects to Azue. A -> B -> C -> Azure Adding only domain B to Manage Custom Domains will cause 404 while redirecting from A and C. You need to add all ...



Top 50 recent answers are included