flagshipcredit
asked on
A Record to Dedicated Hosted Server - IIS
I'm having an issue where the Subdomain address isn't going to the server. We recently bought a dedicated server through GoDaddy with IIS to run a few simple ASP Scripts.
We have our Domain name through NetworkSolutions, I set an A Record (abc.domain.com) to the Dedicated Server IP. (Did this early yesterday)
I when into IIS and created a new site (abc), assigned the cert and ip to that site. I can access the site through https://IPADDRESS/abc with no problems, but I can't access the site through https://abc.domain.com
It is probably a simple setting I missing, but I just can't seem to find it, IIS isn't my strong area but I've created internal sites before but nothing outside the network.
Thanks,
- Fred
We have our Domain name through NetworkSolutions, I set an A Record (abc.domain.com) to the Dedicated Server IP. (Did this early yesterday)
I when into IIS and created a new site (abc), assigned the cert and ip to that site. I can access the site through https://IPADDRESS/abc with no problems, but I can't access the site through https://abc.domain.com
It is probably a simple setting I missing, but I just can't seem to find it, IIS isn't my strong area but I've created internal sites before but nothing outside the network.
Thanks,
- Fred
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do domain.com and abc.domain.com point to same IP address? They have to.
ASKER
We may be misunderstanding each other because we have subdomains pointing to outside servers that work without having the main domain on those servers. I will try to explain step by step on how it is setup.
Network Solutions Configuration:
- Main Domain Registar
- Main Domain Hoster
- DNS A Record created 'abc.domain.com' Pointing to IP Address of GoDaddy's Dedicated Server
GoDaddy Server Configuration
- Windows 2008 R2 Box
- IIS7 Installed
- SSL Cert installed for abc.domain.com
- Added Site, type: HTTPS Port:443 Assigned to abc.domain.com Cert
~ I've tried naming the site 'abc' and naming it 'abc.domain.com' to see if that would work but nothing.
I can access the site via https://IPAddress just not through the sub yet.
I'm almost leaning towards that the DNS hasn't propagated yet however I've never had it take over 4 hours before, I figured 24 hours it should be working by now.
Network Solutions Configuration:
- Main Domain Registar
- Main Domain Hoster
- DNS A Record created 'abc.domain.com' Pointing to IP Address of GoDaddy's Dedicated Server
GoDaddy Server Configuration
- Windows 2008 R2 Box
- IIS7 Installed
- SSL Cert installed for abc.domain.com
- Added Site, type: HTTPS Port:443 Assigned to abc.domain.com Cert
~ I've tried naming the site 'abc' and naming it 'abc.domain.com' to see if that would work but nothing.
I can access the site via https://IPAddress just not through the sub yet.
I'm almost leaning towards that the DNS hasn't propagated yet however I've never had it take over 4 hours before, I figured 24 hours it should be working by now.
Can you give the domain to check?
Check here if anything is amiss.
http://www.intodns.com
And here for propogation
https://www.whatsmydns.net/
http://www.intodns.com
And here for propogation
https://www.whatsmydns.net/
Procedure :
Login to your Network Registrar and in Advanced DNS Settings for domain.com , put the A @ record abc.subdomain.com to Godaddy Dedicated IP Address .
And @ Godaddy Dedicated server >in IIS there is a single site configured..or any other sites are there..? Please check the site bindings settings > host headers are correct. And that dedicated IP address showing in IIS Manager..?
And firstly check the site on localhost with 80 & 443
check with ping abc.subdomain.com
And instead of https , check with http://abc.subdomain.com
Regards,
Vijay Kadadi
Login to your Network Registrar and in Advanced DNS Settings for domain.com , put the A @ record abc.subdomain.com to Godaddy Dedicated IP Address .
And @ Godaddy Dedicated server >in IIS there is a single site configured..or any other sites are there..? Please check the site bindings settings > host headers are correct. And that dedicated IP address showing in IIS Manager..?
And firstly check the site on localhost with 80 & 443
check with ping abc.subdomain.com
And instead of https , check with http://abc.subdomain.com
Regards,
Vijay Kadadi
ASKER
It was the propagation, it took almost the full 48 hours to do so. Guess there is a first time for everything.
ASKER
Yea I've never really had a DNS take that look, normally between an hour to 5 hours is has taken for me in the passed.
When going to https://abc.domain.com it just states the page can not be found/displayed
yea it exists on the Dedicated Server with the defauly IIS index page