up vote 0 down vote favorite
share [g+] share [fb]

I have one website (example.com) on our main server (server A). However, we have some files that we want to host on another serve (server B), but accessible via download.example.com.

I thought I had it setup correctly, but I appear to be missing something. I added an A Record to example.com's DNS Zone (download.example.com. pointing to server B's IP), but it doesn't seem to be working. I am getting server A's 404 page.

In server B, I created a domain with a website (download.example.com), so that should work, right?

Any advice would be appreciated.

Thanks!

link|improve this question
feedback

2 Answers

up vote 0 down vote accepted

Okay, I figured it out. I hadn't set server B up properly to accept the subdomain.

Thanks for the help!

-Jack

link|improve this answer
feedback
up vote 0 down vote

woops, reread your OP...

have you tried accessing the download.example.com server directly? i.e., 

http://download.example.com/somefilethatreallyexists

If that works, then it sounds like the request is still being passed to server A. You need to trace the request to establish whether or not it's being handed off to the right server.

link|improve this answer
can you expand upon that? – meder Dec 10 '09 at 2:53
@greeblesnort: Not 100% sure what you mean. server b is up. I have a temp alias that my host gives me that is working just as it should. I hope I'm understanding your question... Thanks! – jchapa Dec 10 '09 at 2:57
Okay, I just did a trace of the web request. Really weird. It's ending up at server B! The A record is pointing to server B. However the NS records are pointing to server A. Note that these are the DNS server records for the root (example.com). Do I need to create a new DNS Server record for the subdomain? Thanks! – jchapa Dec 10 '09 at 3:08
feedback

Your Answer

 
or
required, but never shown