|
|
Ok, here's our situation.
We run 2 DNS servers on our Win2003 AD network. We were hosting our website
internally, and recently moved our site to someone else. I work for the a
state agency, so our DNS is forwarded onto the main state DNS servers, and
each of my 2 DNS servers have 4 IP for forwarding DNS requests.
We had several cname records, www being one of them, that pointed to the
webserver. I removed the cname record for www yesterday (12/1). The
minimum TTL is set to 1 hour, and scavange is 1 day.
Since deleting that cname record, if I try to ping/tracert www.site.com, I
get: "could not find host www.site.com. Please check the name and try
again".
It seems to be just a internal problem, as I can get to the new location
just from using an external PC.
Any ideas???
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:7473F167-4E18-4114-A262-79244F0B2F46[ at ]microsoft.com...
[Quoted Text] > We run 2 DNS servers on our Win2003 AD network. We were hosting our
> website internally, and recently moved our site to someone else. I work
> for the a state agency, so our DNS is forwarded onto the main state DNS
> servers, and each of my 2 DNS servers have 4 IP for forwarding DNS
> requests.
>
> We had several cname records, www being one of them, that pointed to the
> webserver. I removed the cname record for www yesterday (12/1). The
> minimum TTL is set to 1 hour, and scavange is 1 day.
>
> Since deleting that cname record, if I try to ping/tracert www.site.com, I
> get: "could not find host www.site.com. Please check the name and try
> again".
Assuming your AD Domain Name and the Public Domain Name are spelled the same
(sounds like they probably are),.....You have to replace CNAME with an A
Record that uses the new IP# of the Site. You DNS is *not* going to bounce
to a Forwarder when it already possesses a Zone of the same name within its
own Database.
So you DNS has to maintain *all* records for any Public Sites that use the
Domain that is spelled the same as your AD Domain Name. However the ISP or
whoever is hosting the Public DNS Records still has to keep thier own
records maintainsed as well.
Remember:
Your users will use your own AD/DNS to resolve this,...the Public will not.
The Public will use the ISP (or DNS Hoster) to resolve this,...your users
will not.
--
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.
-----------------------------------------------------
|
|
Well, I had this thought before you wrote it, but its good to hear it again.
I did something similar
Added a cname for www that points to the FQDN of the DNS server that has the
entry for www
and a A record for just the http://site.com entry that points to the IP of
the DNS server....
Seems to work fine....
Thanks!!
"Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message
news:OVrAZvJVJHA.3912[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > "Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
> news:7473F167-4E18-4114-A262-79244F0B2F46[ at ]microsoft.com...
>
>> We run 2 DNS servers on our Win2003 AD network. We were hosting our
>> website internally, and recently moved our site to someone else. I work
>> for the a state agency, so our DNS is forwarded onto the main state DNS
>> servers, and each of my 2 DNS servers have 4 IP for forwarding DNS
>> requests.
>>
>> We had several cname records, www being one of them, that pointed to the
>> webserver. I removed the cname record for www yesterday (12/1). The
>> minimum TTL is set to 1 hour, and scavange is 1 day.
>>
>> Since deleting that cname record, if I try to ping/tracert www.site.com,
>> I get: "could not find host www.site.com. Please check the name and try
>> again".
>
> Assuming your AD Domain Name and the Public Domain Name are spelled the
> same (sounds like they probably are),.....You have to replace CNAME with
> an A Record that uses the new IP# of the Site. You DNS is *not* going to
> bounce to a Forwarder when it already possesses a Zone of the same name
> within its own Database.
>
> So you DNS has to maintain *all* records for any Public Sites that use the
> Domain that is spelled the same as your AD Domain Name. However the ISP
> or whoever is hosting the Public DNS Records still has to keep thier own
> records maintainsed as well.
>
> Remember:
>
> Your users will use your own AD/DNS to resolve this,...the Public will
> not.
>
> The Public will use the ISP (or DNS Hoster) to resolve this,...your users
> will not.
>
> --
> 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.
> -----------------------------------------------------
>
>
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:AC43B2F1-B808-46F2-B942-EBF56A30B124[ at ]microsoft.com...
[Quoted Text] > Well, I had this thought before you wrote it, but its good to hear it > again. I did something similar > > Added a cname for www that points to the FQDN of the DNS server that has > the entry for www > and a A record for just the http://site.com entry that points to the IP of > the DNS server.... > > Seems to work fine....
No I wouldn't do that at all.
I would not even suspected that it would have worked in the first place.
Besides that there is no point in jumping to that machine, then to that
machine, then to that machine, then to that machine. Just create the simple
"A" Record that points directly to where you are supposed to go and be done
with it.
Your AD/DNS is *authoritative* for that Zone with respect to your LAN
machines,...so treat it that way.
--
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.
-----------------------------------------------------
|
|
In news:AC43B2F1-B808-46F2-B942-EBF56A30B124[ at ]microsoft.com,
Steve Grosz <boise_bound[ at ]hotmail.com> requesting assistance, typed the
following:
[Quoted Text] > Well, I had this thought before you wrote it, but its good to hear it > again. I did something similar > > Added a cname for www that points to the FQDN of the DNS server that > has the entry for www > and a A record for just the http://site.com entry that points to the > IP of the DNS server.... > > Seems to work fine.... > > Thanks!!
Steve,
If your internal and external names are the same, you can't mess with the
"site.com" name, or more accurately, the one that shows up as:
(same as parent) A x.x.x.x
This is called the LdapIpAddress. It is used by AD clients to "find" domain
controllers in the domain for such services and functions as the GetGpoList
function, replication, and other functions. If you notice, each DC creates
one for itself. If you manually create an A record for it, you're
introducing issues.
My suggestion, as well as Phillips, is to simply create a www record, and
provide the new external IP of the new web server. CNAMES can also be
problematic, which is one reason many admins prefer to not use them.
Also I noticed you mentioned you are using 4 Forwarders. Usually 2 is
plenty. Besides, it may never get to the 3rd or especially the 4th one
because of the time out of the client side resolver service on the querying
client. It will simply time out after it's own algorithm before the query is
resolved. If you;re having problems with Forwarders, I would suggest to pick
to the two fastest servers in respect to speed of the machine, and speed of
the link they are on for your 2 Forwarders and discard the others.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
Ace,
I did notice there were to A records that pointed to both DNS servers in our
office.
The problem is that the website in question uses just http://site.com, AND
http://www.site.com and http://site.com is used on the outside as well as
inside. For the outside, its being handled by different DNS servers, so I
think we're ok there.
If the 2 A records that point to the DNS/AD servers remain in place, in
addition to a A record that points to the external site, then I lose because
it seems like the web browser then resorts to the server internal to our
office. If I remove the 2 A records that point to the DNS/AD servers and
just leave the A record that points to the external server, it works fine.
Steve
"Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com>
wrote in message news:%23amI92PVJHA.2080[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > In news:AC43B2F1-B808-46F2-B942-EBF56A30B124[ at ]microsoft.com, > Steve Grosz <boise_bound[ at ]hotmail.com> requesting assistance, typed the > following: >> Well, I had this thought before you wrote it, but its good to hear it >> again. I did something similar >> >> Added a cname for www that points to the FQDN of the DNS server that >> has the entry for www >> and a A record for just the http://site.com entry that points to the >> IP of the DNS server.... >> >> Seems to work fine.... >> >> Thanks!! > > Steve, > > If your internal and external names are the same, you can't mess with the > "site.com" name, or more accurately, the one that shows up as: > (same as parent) A x.x.x.x > > This is called the LdapIpAddress. It is used by AD clients to "find" > domain controllers in the domain for such services and functions as the > GetGpoList function, replication, and other functions. If you notice, each > DC creates one for itself. If you manually create an A record for it, > you're introducing issues. > > My suggestion, as well as Phillips, is to simply create a www record, and > provide the new external IP of the new web server. CNAMES can also be > problematic, which is one reason many admins prefer to not use them. > > Also I noticed you mentioned you are using 4 Forwarders. Usually 2 is > plenty. Besides, it may never get to the 3rd or especially the 4th one > because of the time out of the client side resolver service on the > querying client. It will simply time out after it's own algorithm before > the query is resolved. If you;re having problems with Forwarders, I would > suggest to pick to the two fastest servers in respect to speed of the > machine, and speed of the link they are on for your 2 Forwarders and > discard the others. > > > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT > Microsoft Certified Trainer > > For urgent issues, you may want to contact Microsoft PSS directly. > Please check http://support.microsoft.com for regional support phone > numbers.
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:erPcvxVVJHA.2468[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Ace, > > I did notice there were to A records that pointed to both DNS servers in > our > office. > > The problem is that the website in question uses just http://site.com, AND > http://www.site.com and http://site.com is used on the outside as well as > inside. For the outside, its being handled by different DNS servers, so I > think we're ok there.
That is just simply a bad practice and you need to stop doing that. The
Stucture of a Domain Name with respect to a web site "demands" 3 parts to
the name. Each of the three parts has a specific meaning and purpose.
hostname.domainname.top-level-domain
^ ^ ^
www . site . com
What you are doing with http://site.com is having the DNS that does the
resolving make the *assumption* that "www" is the hostname when no host name
is supplied. That may be fine on the Internet DNS because the choices of
"assumed" Hostname are very few. However I do not think this is a very good
thing to do with an internal AD/DNS which contains hundreds or thousands of
Hostnames.
You need to stop using http://site.com
--
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.
-----------------------------------------------------
|
|
Ok, now I'm just confused......
So whoever set up DNS before I got here has two entries that don't make any
sense to me.
2 A records that are going to (same as parent folder) to different IP's,
which are our DNS servers.
I have 1 A record for www that points to a outside IP, but after making that
change, I can't get to that location, instead its hitting our internal IIS
server's ip and bring up the internal web page. Nothing in DNS points www
to a internal IP.
So why is it when I type www.site.com, I go to our internal web server
instead of the external one??????
"Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message
news:uD48YYiVJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > "Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message > news:erPcvxVVJHA.2468[ at ]TK2MSFTNGP02.phx.gbl... >> Ace, >> >> I did notice there were to A records that pointed to both DNS servers in >> our >> office. >> >> The problem is that the website in question uses just http://site.com, >> AND >> http://www.site.com and http://site.com is used on the outside as well as >> inside. For the outside, its being handled by different DNS servers, so >> I >> think we're ok there. > > That is just simply a bad practice and you need to stop doing that. The > Stucture of a Domain Name with respect to a web site "demands" 3 parts to > the name. Each of the three parts has a specific meaning and purpose. > > hostname.domainname.top-level-domain > ^ ^ ^ > www . site . com > > What you are doing with http://site.com is having the DNS that does the > resolving make the *assumption* that "www" is the hostname when no host > name is supplied. That may be fine on the Internet DNS because the > choices of "assumed" Hostname are very few. However I do not think this > is a very good thing to do with an internal AD/DNS which contains hundreds > or thousands of Hostnames. > > You need to stop using http://site.com> > -- > 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. > ----------------------------------------------------- > >
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:DF0DBE35-2AFF-460F-AB88-6FE108E4DCA1[ at ]microsoft.com...
[Quoted Text] > Ok, now I'm just confused......
>
> So whoever set up DNS before I got here has two entries that don't make
> any sense to me.
>
> 2 A records that are going to (same as parent folder) to different IP's,
> which are our DNS servers.
Confusion is start to set in with me too :-) Maybe Ace can clarify.
But I believe these entries are the ones that make the "assumption" when no
host is given in the URL (like http://site.com). It means the "naked"
domain name will resolve to the IP given in that A Record since no Host Name
is declared in the URL.
Yes it is confusing,...that's why I say stop doing http://site.com . Never
leave the host name undeclared.
> I have 1 A record for www that points to a outside IP, but after making
> that change, I can't get to that location, instead its hitting our
> internal IIS server's ip and bring up the internal web page. Nothing in
> DNS points www to a internal IP.
>
> So why is it when I type www.site.com, I go to our internal web server
> instead of the external one??????
Well let's get to the bottom line. You have 2 web servers,..one
internal,...one external,...what FQDN do you *want* them to be designated
with?
--
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.
-----------------------------------------------------
|
|
In news:erPcvxVVJHA.2468[ at ]TK2MSFTNGP02.phx.gbl,
Steve Grosz <boise_bound[ at ]hotmail.com> requesting assistance, typed the
following:
[Quoted Text] > Ace, > > I did notice there were to A records that pointed to both DNS servers > in our office. > > The problem is that the website in question uses just > http://site.com, AND http://www.site.com and http://site.com is used > on the outside as well as inside. For the outside, its being handled > by different DNS servers, so I think we're ok there. > > If the 2 A records that point to the DNS/AD servers remain in place, > in addition to a A record that points to the external site, then I > lose because it seems like the web browser then resorts to the server > internal to our office. If I remove the 2 A records that point to > the DNS/AD servers and just leave the A record that points to the > external server, it works fine. > Steve >
Steve, your CANNOT remove those two blank A records. I am assuming you are
talking about those 'blank' domain records without names but have a name
called "(same as parent)." These records are necessary records for AD. They
are called the "LdapIpAddress" that the netlogon service on EACH domain
controller registers into DNS. THey are used by a multitude of domain
functions such as GPOs, DFS, and more. Those records are part of AD's
functionality. To delete them to satisfy website access will compromise
domain functionality. I do not think you want that to happen. This is one of
the results of choosing the same AD domain name internal as external.
If you can live with having to type in www, please do so, as Phillip also
implied.
But, if you absolutely need to get to the domain without the www in the
name, then follow these instructions:
1. Create a www record under your site.com zone in your DNS server. Give it
the IP address of the new external webserver.
2. On each and every domain controller, make sure IIS is installed with the
default website.
3. In the default website properties, redirect the URL to www.site.com.
There is no real other way around this.
Now that said, if you are having trouble pinging www.site.com to the
external IP addres, I suggest to go into DNS properties on each server, and
clear the cache, then go to your workstation that you are trying to ping it
with and clear the client's local host cache by typing in the following:
ipconfig /flushdns
Then ping it again.
This is of course assuming that the www record was only created once, and
you gave it the correct IP address of the webserver, as well as the
webserver is not blocking or ignoring ping requests (that many websites
hosted at ISPs are now doing).
Ace
|
|
Well, we're going to be turning off the site internally, its being hosted
elsewhere.
So, if I type www.site.com, it should go to the off-site webserver.
Intstead its going to the internal web server.
If I tracert the www.site.com, it goes to the correct location. Just seems
to be a problem in the browser. NSLOOKUP also shows the correct location
for www.site.com and is being determined by our DNS server in the office.
So I'm stumped why is is when I type www.site.com it goes to the internal
webserver....
"Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message
news:OCvoNmnVJHA.1220[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > "Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message > news:DF0DBE35-2AFF-460F-AB88-6FE108E4DCA1[ at ]microsoft.com... >> Ok, now I'm just confused...... >> >> So whoever set up DNS before I got here has two entries that don't make >> any sense to me. >> >> 2 A records that are going to (same as parent folder) to different IP's, >> which are our DNS servers. > > Confusion is start to set in with me too :-) Maybe Ace can clarify. > But I believe these entries are the ones that make the "assumption" when > no host is given in the URL (like http://site.com). It means the "naked" > domain name will resolve to the IP given in that A Record since no Host > Name is declared in the URL. > Yes it is confusing,...that's why I say stop doing http://site.com . > Never leave the host name undeclared. > >> I have 1 A record for www that points to a outside IP, but after making >> that change, I can't get to that location, instead its hitting our >> internal IIS server's ip and bring up the internal web page. Nothing in >> DNS points www to a internal IP. >> >> So why is it when I type www.site.com, I go to our internal web server >> instead of the external one?????? > > Well let's get to the bottom line. You have 2 web servers,..one > internal,...one external,...what FQDN do you *want* them to be designated > with? > > -- > 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. > ----------------------------------------------------- > >
|
|
I have run the ipconfig /flushdns several times, and on my local PC, the IP
for www.site.com is resolving to the correct external IP. But when in the
web browser, its going to the internal webserver instead of the external
one.
"Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com>
wrote in message news:OLfsXLpVJHA.5504[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > In news:erPcvxVVJHA.2468[ at ]TK2MSFTNGP02.phx.gbl, > Steve Grosz <boise_bound[ at ]hotmail.com> requesting assistance, typed the > following: >> Ace, >> >> I did notice there were to A records that pointed to both DNS servers >> in our office. >> >> The problem is that the website in question uses just >> http://site.com, AND http://www.site.com and http://site.com is used >> on the outside as well as inside. For the outside, its being handled >> by different DNS servers, so I think we're ok there. >> >> If the 2 A records that point to the DNS/AD servers remain in place, >> in addition to a A record that points to the external site, then I >> lose because it seems like the web browser then resorts to the server >> internal to our office. If I remove the 2 A records that point to >> the DNS/AD servers and just leave the A record that points to the >> external server, it works fine. >> Steve >> > > Steve, your CANNOT remove those two blank A records. I am assuming you are > talking about those 'blank' domain records without names but have a name > called "(same as parent)." These records are necessary records for AD. > They are called the "LdapIpAddress" that the netlogon service on EACH > domain controller registers into DNS. THey are used by a multitude of > domain functions such as GPOs, DFS, and more. Those records are part of > AD's functionality. To delete them to satisfy website access will > compromise domain functionality. I do not think you want that to happen. > This is one of the results of choosing the same AD domain name internal as > external. > > If you can live with having to type in www, please do so, as Phillip also > implied. > > But, if you absolutely need to get to the domain without the www in the > name, then follow these instructions: > > 1. Create a www record under your site.com zone in your DNS server. Give > it the IP address of the new external webserver. > 2. On each and every domain controller, make sure IIS is installed with > the default website. > 3. In the default website properties, redirect the URL to www.site.com. > > There is no real other way around this. > > Now that said, if you are having trouble pinging www.site.com to the > external IP addres, I suggest to go into DNS properties on each server, > and clear the cache, then go to your workstation that you are trying to > ping it with and clear the client's local host cache by typing in the > following: > ipconfig /flushdns > Then ping it again. > > This is of course assuming that the www record was only created once, and > you gave it the correct IP address of the webserver, as well as the > webserver is not blocking or ignoring ping requests (that many websites > hosted at ISPs are now doing). > > > Ace >
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:9FC0D02A-FF30-42B6-8392-048D0F46CEA0[ at ]microsoft.com...
[Quoted Text] > Well, we're going to be turning off the site internally, its being hosted
> elsewhere.
It can not happen "grandually". It has to be solid,.."boom",..done. So
disable IIS or at least the particular Site on IIS and soon as the new one
is available. You can't go to the wrong one if there is nothing there to go
to.
> So, if I type www.site.com, it should go to the off-site webserver.
> Intstead its going to the internal web server.
>
> If I tracert the www.site.com, it goes to the correct location. Just
> seems to be a problem in the browser. NSLOOKUP also shows the correct
> location for www.site.com and is being determined by our DNS server in the
> office.
>
> So I'm stumped why is is when I type www.site.com it goes to the internal
> webserver....
It will do that if you are running a CERN Compliant Web Proxy and the proxy
is either:
1. Using the wrong DNS itself
2. It can "cache" the site in the Web Cache. Either dumb the Cache and
force it to refresh,...or shut down the proxy for a day of so and don't use
it. When you start it up later on the cache will be so "old" that it will
be forced to refresh it. I had a *lot* of trouble like that with MS ISA
Server and had to disable the Web Proxy Service for about three days and run
off of the other ISA's Services for a while. When I reenabled it later it
was fine. The really annoying thing was the Cacheing had been disabled and
unused from the beginning,...but ISA still caches things in some way even
with it disabled.
3. IE's temporary internet files are a problem too, so dump them,...set
them to the minmum size (because it is impossible to turn it off). Then set
it to "every visit to the page".
--
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.
-----------------------------------------------------
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:E81F7EB4-6F35-4B71-A509-10C81EF9C9C2[ at ]microsoft.com...
[Quoted Text] > ........................... But when in the web browser, its going to
> the internal webserver instead of the external one.
See my last post on that one.
--
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.
-----------------------------------------------------
|
|
Well, with the internal site turned off, the www.site.com is not going to
the new server, even though the ping and tracert are!
We aren't using anything like ISA, so we don't have another system for web
caching.....
Steve
"Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message
news:uivq7CxVJHA.5496[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > "Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
> news:9FC0D02A-FF30-42B6-8392-048D0F46CEA0[ at ]microsoft.com...
>> Well, we're going to be turning off the site internally, its being hosted
>> elsewhere.
>
> It can not happen "grandually". It has to be solid,.."boom",..done. So
> disable IIS or at least the particular Site on IIS and soon as the new one
> is available. You can't go to the wrong one if there is nothing there to
> go to.
>
>> So, if I type www.site.com, it should go to the off-site webserver.
>> Intstead its going to the internal web server.
>>
>> If I tracert the www.site.com, it goes to the correct location. Just
>> seems to be a problem in the browser. NSLOOKUP also shows the correct
>> location for www.site.com and is being determined by our DNS server in
>> the office.
>>
>> So I'm stumped why is is when I type www.site.com it goes to the internal
>> webserver....
>
> It will do that if you are running a CERN Compliant Web Proxy and the
> proxy is either:
> 1. Using the wrong DNS itself
> 2. It can "cache" the site in the Web Cache. Either dumb the Cache and
> force it to refresh,...or shut down the proxy for a day of so and don't
> use it. When you start it up later on the cache will be so "old" that it
> will be forced to refresh it. I had a *lot* of trouble like that with MS
> ISA Server and had to disable the Web Proxy Service for about three days
> and run off of the other ISA's Services for a while. When I reenabled it
> later it was fine. The really annoying thing was the Cacheing had been
> disabled and unused from the beginning,...but ISA still caches things in
> some way even with it disabled.
> 3. IE's temporary internet files are a problem too, so dump them,...set
> them to the minmum size (because it is impossible to turn it off). Then
> set it to "every visit to the page".
>
>
> --
> 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.
> -----------------------------------------------------
>
>
|
|
"Steve Grosz" <boise_bound[ at ]hotmail.com> wrote in message
news:AFEF7287-BC4B-45F9-9271-AFC5BBD23683[ at ]microsoft.com...
[Quoted Text] > Well, with the internal site turned off, the www.site.com is not going to
> the new server, even though the ping and tracert are!
>
> We aren't using anything like ISA, so we don't have another system for web
> caching.....
I have no idea then.
--
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.
-----------------------------------------------------
|
|
I'm sure there are just some details about the situation that if we knew
them the problem might be easily solved. But we are pretty much blindfolded
and can only judge it based on the details you give us.
--
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.
-----------------------------------------------------
|
|
In news:E81F7EB4-6F35-4B71-A509-10C81EF9C9C2[ at ]microsoft.com,
Steve Grosz <boise_bound[ at ]hotmail.com> requesting assistance, typed the
following:
[Quoted Text] > I have run the ipconfig /flushdns several times, and on my local PC,
> the IP for www.site.com is resolving to the correct external IP. But
> when in the web browser, its going to the internal webserver instead
> of the external one.
>
Then you must have skipped steps 2 & 3 in my suggestions.
Ace
|
|
|