Re: unable to view parts of outside site
- From: "Anthony [MVP]" <anthony@xxxxxxxxxxxx>
- Date: Thu, 28 Aug 2008 20:12:54 +0100
Hi MC.
You have split DNS. This means that xxx.company.com goes to one place with the internal DNS and a different place with the external DNS. This is fine, and you just need to maintain records like www. or mail. manually.
The question is why does your website code call pages that are not resolved externally. It should be referring to pages relative either to the site root or to the document. If it references a page or image with an explicit URL (e.g http://) then a) there should be a reason for that, and b) the URL must also have a split DNS. Hence I asked what exact path was not resolving correctly.
It sounds to me as though the code worked OK somewhere and has then been transported to an external site where it does not work, so you need to edit the code,
Anthony,
http://www.airdesk.co.uk
"mc123" <mc123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F13B3BED-52A3-4E81-BDE4-46743C77EFB8@xxxxxxxxxxxxxxxx
Anthony: it does appear to me that changes needs to be made at the site, or I.
suppose that I would need to change my internal domain? Is this is with a
2003 doamin?
Phillip: I do have an A record, but this does not help with content that is
mapped to "company.com", there is no A record for this, or am I missing
something?
Thanks.
"Phillip Windell" wrote:
"mc123" <mc123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FCDC12F6-A6EC-44F4-9079-91BBDBF34D7C@xxxxxxxxxxxxxxxx
> Hi,
>
> The issue is that our external website for the company uses our domain > as
> the path to a lot of content and pictures.
> Because our internal domain is the same as external, for example inside > is
> company.com and outside is also company.com. With the main site;
> www.company.com, its not a problem I just setup an A record, but when > the
> outside site maps a lot of the picture and content directly to
> company.com,
> any system inside our network will not find that content, because it > will
> always go to our inside network, like the domain controllers.
Split-DNS.
It is a simple solution. You have to add the manual "A" Records in your
AD/DNS so that the links resolve to the correct IP#. In your case it will
be the inside IP#s and it will work fine for your users.
However your ISP (or whoever is the Authoritative DNS for you Public domain)
will have to do the same thing except that they have to use the Public IP#
that is correct for the Public to use,...hence the name Split-DNS.
More things:
"outside site maps a lot of the picture and content directly to company.com"
That is incorrect. "company.com" is *nothing*,..it is imcomplete,...their
must be "???.company.com"
The locations of these Links within the Site must be reachable from the
Internet. If they are not, then you cannot link to them. That is a bad
site design and it will not work.
Web Servers do not "route" anything. They send Client-Side code to a user's
Web Browser.
The Web Browser renders the code and does what it is told.
If the code comes from http://www.company.com and has a link in the code to
an image at http://privateserver.company.com/images/someimage.jpg then that
is exactly what the user's browser will request and "privateserver" had
better be reachable from the internet from the user browser,...the web
server "www" that sent the original code to the browser is irrelevant.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
- References:
- unable to view parts of outside site
- From: mc123
- Re: unable to view parts of outside site
- From: Phillip Windell
- Re: unable to view parts of outside site
- From: mc123
- unable to view parts of outside site
- Prev by Date: Re: unable to view parts of outside site
- Next by Date: Notebook Internet Connectivity (Domain, DNS)
- Previous by thread: Re: unable to view parts of outside site
- Next by thread: DNS Forward Lookup Zone has 2 PCs with the same IP address
- Index(es):
Relevant Pages
|
