DNS adressing problem

Company I work for is going through name change. As such, some of their web-based applications need new addresses added, so sites are accessible via its previous and new URL.
Here is an example:
Our customers can currently access our web-ordering portal via URL orders.xxxx.com.au (xxxx being the old company name). New URL that would toint to the same site would be orders.yyyy.com.au (yyyy being the new company name).
I have created new forward lookup zone yyy.com.au and added New Host orders.yyyy.com.au with an IP addresses pointing to the servers which host our ordering web portal. I have also added a new addess to correct subnet in Reverse Lookup Zone. Literarly, I have copied the same settings as for orders.xxxx.com.au address.

The trouble is that our servers (there are two load-balancing servers) also host our external website www.xxxx.com.au, so when we enter orders.yyyy.com.au, we are redirected to our company's webpage, www.xxxx.com.au. It is the same for our other web-based apps, such as catalogue.yyyy.com.au - they all redirect to our company's homepage.

As I am not much of a Server Guy, I hope someone will collect easy points as solution is, I am sure, starting me in the eye.

Who is Participating?
netmunkyConnect With a Mentor Commented:
in IIS manager (assuming IIS), go to the properties of the website, click Advanced next to the IP Address, you should see host headers for "orders.xxx.com.au" (or whatever relative website you are looking at). add another host header for "orders.yyy.com.au" (or whatever relative).

apache would be done using the <VirtualHost> directive in httpd.conf. copy the <VirtualHost ...>...</VirtualHost> that applies to the old site, duplicate it for the new site with appropriate information.
ChatableConnect With a Mentor Commented:
Your problem is definitely NOT at the DNS server but at the web server.
My guess is that your webserver is configured to use named-based virtual hosts (meaning that it serves different websites on different DNS addresses) with a default site that redirects to your company's homepage.
You should check the virtual hosts section on your webserver's configuration and add the new DNS name to be recognized as the orders website.
If you are unable to figure out how to do this, please reply and tell me which server are we talking about (apache/IIS/etc).
Leon FesterConnect With a Mentor IT Project Change ManagerCommented:
You should be able to resolve the above issue by adding host headers for the site names. Your site probably already has host headers for orders.xxx.com.au, but not for orders.yyy.com.au.

Your main site does not have host headers enabled and is thus displaying your main page to any request that is sent to that IP. Host headers are especially important when using the same IP for different DNS names/web sites.
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

OmaBatlakAuthor Commented:

How easy was that!!

Once I new header and associated it with server IP address and a TCP port 80, it worked like a charm.

Thanks guys!

OmaBatlakAuthor Commented:

new addresses (eq. orders.yyyy.com.au) can only be seen from within our network. They cannot be accessed from outside. Any hints?
Leon FesterIT Project Change ManagerCommented:
You'll need to register the new A records with your upstream provider or ISP. Your local DNS is only availble on your local Network. Then again, you may need to see how forwarding to your webserver is handled by your firewall. It may require an additional entry for the new site names.
the most common scenario is company-x has company-x.com DNS hosted at outside hosting server (it - network solutions, enom, everydns, etc), but then they also host the domain internally for their own use, rather than query the outside server directly. this is often done to make things nice and speedy internally, or if you have domains you want available internally that should not be resolved externally.

go to http://www.dnsstuff.com/ and look up the NS records for your domain. if it is not your local server, you will need to contact your DNS host and have the orders/etc records added.

of course, depending on your SOA record, it may just be a matter of propogation. if you are using microsoft dns server, the serial is automatically incremented with every change, but if you are using bind, make sure you increment the serial in the SOA properly, and wait for the TTL/expire before thinking that it is not working (may take up to 24 hours)
All Courses

From novice to tech pro — start learning today.