re: sub.sub.domain DNS question
Wednesday, May 7, 2008 at 12:43 am
Windows Server 2003 Annoyances Discussion Forum
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.
>
>
>
|
