Forum Moderators: open

Message Too Old, No Replies

Adding a sub domain

         

andrewsmd

9:14 pm on Feb 23, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I am trying to add a sub domain in iis and dns and am having some issues. Right now in dns I have this
(A) 1.1.1.1
www (A) 1.1.1.1
temp (A) 1.1.2.2

Basically I want domain.com and www.domain.com to go to a different IP but temp.domain.com to come to my server. I have the website set up in IIS as domain.com I can't even ping temp.domain.com. If you go to the who.is the temp.domain.com does not show up. However, I can see it in my dns as an A record. What am I missing? Thanks,

LifeinAsia

10:19 pm on Feb 23, 2010 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Obvious questions, but do you have:
1) IP 1.1.2.2 configured on your server/network card?
2) have temp.domain.com setup in IIS (or whatever web server you're using) and pointing to IP 1.1.2.2?

andrewsmd

10:57 pm on Feb 23, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The IP is correct. I don't have temp.domain.com set up in IIS but I shouldn't need it because I have the host header temp.domain.com set up under the dns records for domain.com. Just to calrify, 1.1.1.1 is someone else's server, and 1.1.2.2 is our local server. So basically if someone is going to domain.com, they should be redirected to the external server, and if someone goes to temp.domain.com they should be sent to 1.1.2.2 which is our server. I don't think this is an IIS issue because I can't even see temp.domain.com on who.is and I can't ping it. I could be wrong though. Any thoughts?

LifeinAsia

11:06 pm on Feb 23, 2010 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



DNS and IIS are 2 separate issues. DNS will direct requests to temp.domain.com to IP 1.1.2.2. But you still need IIS setup so it know what to do with requests coming into it for temp.domain.com. It may be less of an issue with domain.com being on a different server, but it may be part of the problem.

WHOIS doesn't resolve subdomains, just domains. Try nslookup for temp.domain.com- does it resolve to 1.1.2.2?

What happens if you try to ping 1.1.2.2 and temp.domain.com?

Also, how long ago did you setup the DNS entry? It can take several hours for changes to propagate out.

andrewsmd

2:53 am on Feb 24, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



So I just wasn't patient enough. I had thought that since the name server switch had been picked up, that it also would have picked up the temp.domain.com but it didn't. I checked it later this evening and it is working. FYI, I didn't need the site temp.domain.com in IIS as long as domain.com has the A record temp.domain.com