Tork4840
asked on
How do you get a www web site to come up with out the www
My company has the web site www.loansupplies.com . Ive been asked to make it come up if typed as loansupplies.com with out the www . Its registered as loansupplies.com and just has an alias www.loansupplies.com. Im guessing it has somehting to due with my DNS. I changed the header order to reflect loansupplies.com first. Being ran on windows machines with windows software DNS and IIS behind a ISA server if it matters. Im pretty green with these kind of issues.
Thanks
Phillip
Thanks
Phillip
Did you change the address on the ISA server to reflect loansupplies.com?
ASKER
They are the same IP address. No names were used with the IAS configuration.
When I go to that site, I get re-directed elsewhere.
I am assuming
a. this is a fake address
b. this request is done?
Either way, a correct address would be nice to troubleshoot this issue.
--Kelly
I am assuming
a. this is a fake address
b. this request is done?
Either way, a correct address would be nice to troubleshoot this issue.
--Kelly
ASKER
The web guy that did our sites for some reason did them that way. they are a part of www.technologyprinting.com All default.asp has in it is
<html>
<body>
<%
Response.redirect "http://www.technologyprinting.com/industryproducts_list.asp?bear=41"
%>
</body>
</html>
Im not positive that this is an issue external of our network. I have no way to test here.
<html>
<body>
<%
Response.redirect "http://www.technologyprinting.com/industryproducts_list.asp?bear=41"
%>
</body>
</html>
Im not positive that this is an issue external of our network. I have no way to test here.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I added a alias with a blank name pointing the web server in DNS is that what fixed it?
This is a question for your hosting provider's tech support. They should be doing it for you and if not they can set it up to work or tell you how...
ASKER
We host our own websites.
Issue is resolved must have been the record i added
Issue is resolved must have been the record i added
This is strictly DNS. If there is no A record for loansupplies.com, it will not get translated to TCP/IP address. Once the A record is added, it can take a while to be fully implemented. Most DNS servers cache this information and only check it occasionally for changes. While changes can sometimes occur immediately at the host site, it can take a couple of days for the entire web to recognize the additional url definition.
Upon checking your DNS route, your host started resolving at loansupplies.com the date it was pointed, so this had to hav been a cache issue on your end.
--Kelly
--Kelly
ASKER
Dose the internal DNS not have anything to do with it? This has been on issue supposedly way before i got here back in last sept.
Does your internal DNS have an explicit collection of records for your domain or does it get it's DNS information from an external source? If it has an explicit collection (you've entered DNS records manually) then they would override the external DNS collection for any computers that use that DNS. Any computers pointed to an external DNS would get their information from the host which already included loansupplies.com.
ASKER
There are entries for all of our web sites including this one on our private DNS server. Should it not?
I assume that you have pointed the computers on your intranet to your private DNS server. If your private DNS server has access to the public or host DNS server, it can download and cache the public information. If you have manually entered information for your web sites into your private DNS server, these entries will override those on the host DNS server for those intranet computers. If your private DNS server does NOT have access to the host DNS server, then you should match the entires on the public one exactly in order to avoid this type of behavior UNLESS the computers on the intranet need to access the web-site differently.
For instance, the public DNS server may be pointed to your firewall which is forwarding everything to your web server. You would not need to point your intranet visitors to the firewall, you would point them directly at the web server. In this case you should manually enter the same records with different IP addresses. If you left one out such as loansupplies.com, the public visitors would be able to access the site via loansupplies.com but the intranet visitors would not.
For instance, the public DNS server may be pointed to your firewall which is forwarding everything to your web server. You would not need to point your intranet visitors to the firewall, you would point them directly at the web server. In this case you should manually enter the same records with different IP addresses. If you left one out such as loansupplies.com, the public visitors would be able to access the site via loansupplies.com but the intranet visitors would not.
Try to use this as common practice..... always have the blank record to point to your WWW CName.