Re: Intranet Name Resolution
From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 11/30/04
- Next message: Kevin D. Goodknecht Sr. [MVP]: "Re: DNS & Exchange 2003 config"
- Previous message: Lanwench [MVP - Exchange]: "Re: DNS & Exchange 2003 config"
- In reply to: Ricardo: "Re: Intranet Name Resolution"
- Next in thread: Kevin D. Goodknecht Sr. [MVP]: "Re: Intranet Name Resolution"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 17:55:44 -0700
Hi Ricardo,
I understand you have changed from having a subdomain
named intranet to having an A record by that name in your
company.com zone.
Good.
Now you have an internal machine that is able to ping the
name intranet.company.com and get that correct IP for the
internal web, but it goes straight to the external website
when the name is entered in IE (that is what you now see,
right?)
I can only understand this in some form of IE caching, but
even that does not add up.
This is what you say is your current state, right?
Is this so on only the one machine?
-- Roger Abell Microsoft MVP (Windows Security) MCSE (W2k3,W2k,Nt4) MCDBA "Ricardo" <Ricardo@discussions.microsoft.com> wrote in message news:DF1983F9-C426-4993-AB22-559C8DCA5683@microsoft.com... > In fact I have to create a HOST record for "intranet" on DNS inside the > COMPANY.COM domain, in order to reach my IIS server. > it's correct because when I ping intranet.company.com, it returns my the IP > of my IIS server. But when I type this on my IE, it still displays my my > internet site. > > PS.: The internet site is not running on this IIS server, it's running on a > Linux Apache web server, and there's a BIND DNS Server that is solving > internet names (the internal Windows DNS is fowarding to BIND). > May this be afecting my name resolution ??? > Any other help, please, > > "Steve Duff [MVP]" wrote: > > > This is not really a DNS issue. DNS in essence, just > > points a name to IP addresses. That's it. It doesn't > > know anything at all about web servers or browsers > > or what they are doing with that tidbit of information. > > > > So, you will have to put intranet.company.com on a different > > IP address and then 'bind' your sites in IIS to those specific > > addresses independently. That way IIS "knows" which site > > is being asked for. > > > > Or you can use "host header discrimination" in your IIS > > sites' properties to direct traffic depending on what the browser > > is actually sending to your web server. The IIS help explains > > how to configure this and it is relatively simple to do. > > > > Steve Duff, MCSE, MVP > > Ergodic Systems, Inc. > > > > "Ricardo" <Ricardo@discussions.microsoft.com> wrote in message news:CA6F2751-95B5-4CFF-89C9-F37EC5150B2F@microsoft.com... > > >I have a internet site called by www.company.com > > > Now I`ve created a intranet site, and I want it to be called by typying > > > "intranet.company.com" or "www.company.com/intranet", but I can't setup this. > > > In my DNS I've created a domais called INTRANET inside the COMPANY.COM > > > domain, but it's not working, because when a type intranet.company.com, it > > > shows my the same as I type www.company.com > > > > > > Please I need some help. > > > > > > > > > Thanks, > > > > > >
- Next message: Kevin D. Goodknecht Sr. [MVP]: "Re: DNS & Exchange 2003 config"
- Previous message: Lanwench [MVP - Exchange]: "Re: DNS & Exchange 2003 config"
- In reply to: Ricardo: "Re: Intranet Name Resolution"
- Next in thread: Kevin D. Goodknecht Sr. [MVP]: "Re: Intranet Name Resolution"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|