Hello ALL,
Every few days I have to change the ip add for one of the static DNS record.
I was hoping to find a way to flush the local workstation DNS cache that way
workstation would lookup this new record instead of using its DNSCACHE to
resolve this add.

Thanks in advance for reading & replying to this post!!!

Pete wrote:
> Hello ALL,
> Every few days I have to change the ip add for one of the static DNS
> record. I was hoping to find a way to flush the local workstation DNS
> cache that way workstation would lookup this new record instead of
> using its DNSCACHE to resolve this add.
>
> Thanks in advance for reading & replying to this post!!!

You can set the TTL on the record to 0 and the record won't get cached..

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:%23PReY31MHHA.2236@TK2MSFTNGP02.phx.gbl...
> Pete wrote:
> > Hello ALL,
> > Every few days I have to change the ip add for one of the static DNS
> > record. I was hoping to find a way to flush the local workstation DNS
> > cache that way workstation would lookup this new record instead of
> > using its DNSCACHE to resolve this add.
> >
> > Thanks in advance for reading & replying to this post!!!
>
> You can set the TTL on the record to 0 and the record won't get cached..

Kevin's correct but why does this static record need to keep
changing?

Kevin & Herb,
Thanks for your reply, its a proxy server that went down few times in past
& had to change the ip add so it would point to different ip add.

Thanks,
pete

"Herb Martin" wrote:

>
> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
> news:%23PReY31MHHA.2236@TK2MSFTNGP02.phx.gbl...
> > Pete wrote:
> > > Hello ALL,
> > > Every few days I have to change the ip add for one of the static DNS
> > > record. I was hoping to find a way to flush the local workstation DNS
> > > cache that way workstation would lookup this new record instead of
> > > using its DNSCACHE to resolve this add.
> > >
> > > Thanks in advance for reading & replying to this post!!!
> >
> > You can set the TTL on the record to 0 and the record won't get cached..
>
> Kevin's correct but why does this static record need to keep
> changing?
>
>
>
>

"Pete" <Pete@discussions.microsoft.com> wrote in message
news:4BF033A9-B1BA-4667-9F24-65949D11C833@microsoft.com...
> Kevin & Herb,
> Thanks for your reply, its a proxy server that went down few times in
past
> & had to change the ip add so it would point to different ip add.

Ok, but that doesn't explain why a manual address keeps
needing CHANGING????

Herb,
Sorry for the delay in replying back to your question, was trying to take
care of few loose ends.

Both sites are connected to each other through T3 & both sites have
separate t1 going out to internet. Both sites have different proxy.

site1 proxy1 ip add=192.168.1.120 goes out to internet through t1
site2 proxy2 ip add=192.168.1.121 goes out to internet through
different t1.

In past either proxy or T1 went down at site1, users still need to use
internet. So I modified the dns entry for proxy1 to ip add=192.168.1.121.
Thats why I wanted to know if their was a way to clear users local dns cache
immediately?


Thank YOu,,,,

"Pete" <Pete@discussions.microsoft.com> wrote in message
news:B8BB9E38-8510-4A4D-AF34-E2DBB697E929@microsoft.com...
> Herb,
> Sorry for the delay in replying back to your question, was trying to take
> care of few loose ends.
>
> Both sites are connected to each other through T3 & both sites have
> separate t1 going out to internet. Both sites have different proxy.
>
> site1 proxy1 ip add=192.168.1.120 goes out to internet through t1
> site2 proxy2 ip add=192.168.1.121 goes out to internet through
> different t1.
>
> In past either proxy or T1 went down at site1, users still need to use
> internet. So I modified the dns entry for proxy1 to ip add=192.168.1.121.
> Thats why I wanted to know if their was a way to clear users local dns
cache
> immediately?

Why not just add the missing IP address (for down server) to
the running (proxy) server -- and remove it when the other
server is ready to come back online?

Clients will just keep using the name and same address but won't
know the proxy machine is different.

Also, consider fault tolerant proxy servers (ISA can do this quite
nicely, even sharing cache through CARP) if this happens on a
regular basis.