I have a win2003 server which is handeling DNS for my internal users.
One of my users has an external website (not on same domain as the internal
domain), but when he does a NSLOOKUP, the internal dns server returns
old/wrong ip number.
If he uses an external DNS to resolve his IP adress, it's correct.
How do i tell my internal DNS to "update" it's cache or aging it's contens.
TIA
Ole
--
--
Brian Desmond
Windows Server MVP
desm...@payton.cps.k12.il.us
"goofy" <ole.m...@noosspam.omc.dk> wrote in message
news:%23kWC5GI%23DH...@TK2MSFTNGP09.phx.gbl...
Is there any way that i can do this on a regular basis (using AT or
something like taht), or do i have to do it by hand ??
/Ole
"Brian Desmond [MVP]" <desm...@payton.cps.k12.il.us> skrev i en meddelelse
news:uDafEfO%23DHA...@TK2MSFTNGP10.phx.gbl...
You can use dnscmd.exe to do this.
The format would be
dnscmd <server name> /clearcache
You could use the task scheduler to automate this.
Having said this, in most cases, it's probably not such a great idea as
caching does reduce external bandwidth usage. Personally, I find the
need to mess around with cache pretty near zero, unless I'm
reconfiguring a network.
--
Thomas Lee
(t...@psp.co.uk)
--
--
Brian Desmond
Windows Server MVP
desm...@payton.cps.k12.il.us
"Thomas Lee" <t...@psp.co.uk> wrote in message
news:gGXV0a55...@mail.psp.co.uk...
True - but I've seen some pretty badly setup serves, with TTLs that are,
shall we say,...
Thomas
--
Thomas Lee
(t...@psp.co.uk)
TL> True - but I've seen some pretty badly setup serves, with
TL> TTLs that are, shall we say,...
If you were about to say "excessively long", then you've forgotten that
Microsoft's DNS server places an upper bound on TTLs (for cached resource
record sets) of one day.
So if Goofy is seeing this resource record set not expiring after more than a
day, then it is not caching that is his problem. (In such a case, my first
educated guess would be that he's done the common thing and set up "split
horizon" DNS service without knowing it.)