Annoyances.org
Home » Windows Server 2003 Discussion Forum » Message 1209846708 » Entire Thread Search | Help | Home
  
sub.sub.domain DNS question
Showing all messages in thread #1209846708
Windows Server 2003 Annoyances Discussion Forum


The following are all of the messages in this thread (3 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
sub.sub.domain DNS question
Saturday, May 3, 2008 at 1:31 pm
Posted by Chris (32 messages posted)

Hi Guys,

This question isnt specific to W2003 but.. Im trying to run an application on a server, 
the application accepts connections on a single IP but uses the hostname to distinguish 
which service to direct to.

The root domain for the services is like this: service.domain.com

But i want to give each person a "sub domain" of that address to access their service. 
Like this..

one.service.domain.com
two.service.domain.com
three.service.domain.com

But, the IP of each "sub sub" domain, returns the IP of domain.com and not service.domain.com.

Instead, all subdomains of service.domain.com should have the same IP as service.domain.com 
and NOT the root IP of domain.com

Hopefully I've explained that OK.
I've googled around but its hard to find a document that means what im looking for.

Thanks in advance

[Reply or follow-up to this message]

re: sub.sub.domain DNS question
Tuesday, May 6, 2008 at 10:02 pm
Posted by appleoddity (1472 messages posted)

What happens is that you have a default (wildcard) entry, and everything in front of service.domain.com falls under that wildcard, which is usually pointed at the root domain (domain.com).. So.. Say, if I do a DNS lookup of abc.domain.com and abc is not in my DNS server records, it will return the wildcard address which is domain.com. If I do a DNS lookup of abc.services.domain.com and abc.services.domain.com does not exist, I will fall under the wildcard entry for domain.com. I think the way to properly handle this, is to create a new zone in your DNS server.. That zone will have a root domain of services.domain.com, then create a wildcard entry for that zone that points to services.domain.com. Then, no matter what you type in front of services.domain.com will point to the proper location. I believe wildcards can be placed in Windows server 2003 DNS just by using the * symbol. So, a *.services.domain.com A record that points to the IP address of services.domain.com should do the trick. Either that, or you just create a new wildcard entry in your root domain (*.domain.com) and make it point to services.domain.com.. However, this would not be considered standard practice as most people want misspelling and such to point to the root domain. So, if I am trying to get to your website and I accidentally type wew.domain.com it will go to domain.com anyways and display the proper webpage. Hope that helps.

[Reply or follow-up to this message]

re: sub.sub.domain DNS question
Wednesday, May 7, 2008 at 12:43 am
Posted by Chris (32 messages posted)

Fantastic, thank you very much for that clear and perfect explanation!

Chris






On Tuesday, May 6, 2008 at 10:02 pm, appleoddity wrote:
>


>What happens is that you have a default (wildcard) entry, and everything in front
>of service.domain.com falls under that wildcard, which is usually pointed at the
>root domain (domain.com)..
>
>So.. Say, if I do a DNS lookup of abc.domain.com and abc is not in my DNS server
>records, it will return the wildcard address which is domain.com. If I do a DNS
>lookup of abc.services.domain.com and abc.services.domain.com does not exist, I will
>fall under the wildcard entry for domain.com.
>
>I think the way to properly handle this, is to create a new zone in your DNS server..
> That zone will have a root domain of services.domain.com, then create a wildcard
>entry for that zone that points to services.domain.com. Then, no matter what you
>type in front of services.domain.com will point to the proper location.
>
>I believe wildcards can be placed in Windows server 2003 DNS just by using the *
>symbol. So, a *.services.domain.com A record that points to the IP address of services.domain.com
>should do the trick.
>
>Either that, or you just create a new wildcard entry in your root domain (*.domain.com)
>and make it point to services.domain.com.. However, this would not be considered
>standard practice as most people want misspelling and such to point to the root domain.
>So, if I am trying to get to your website and I accidentally type wew.domain.com
>it will go to domain.com anyways and display the proper webpage.
>
>Hope that helps.
>
>
>

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows Server 2003 Discussion Forum

All content at Annoyances.org is Copyright © 1995-2008 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.