Using dnscmd to Add and Delete records

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi Al

It's probably because the requests is cached locally. After the deletion,
try an

ipconfig /flushdns

The test.

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: markreno@online.microsoft.com

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

"Al" <alr@ihostuhost.net> wrote in message
news tqpCcZDFHA.3688@TK2MSFTNGP14.phx.gbl...
>I am using dnscmd to add and delete A records to our domain the commands
> both complete successfully, but after a /RecordDelete when you ping the
> just
> removed host you still resolve the ip address which was just deleted.
> However when you check from the console the record is indeed deleted.
> /ZoneWriteback, /ZoneRefresh or /ZoneReload seem to have no effect.
>
> Is there a setting I am missing on the Server?
>
>

Archived from groups: microsoft.public.win2000.dns (More info?)

If Mark is correct (sounds possible to me) AND
you are performing the test ON the DNS server you
might as well just turn off and disable the DNS Client
service.

There is little point is caching something twice ON
THE SAME (server) machine.

If however you are testing from another machine where
the DNS server is not running, the DNS Client will
likely benefit you and you will want to use the:

ipconfig /flushDNS

Another possibility, is that your client settings are pointing
to another DNS server (instead or also).

--
Herb Martin


"Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message
news:umm8IjZDFHA.392@TK2MSFTNGP14.phx.gbl...
> Hi Al
>
> It's probably because the requests is cached locally. After the deletion,
> try an
>
> ipconfig /flushdns
>
> The test.
>
> HTH
> --
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: markreno@online.microsoft.com
>
> Please note you'll need to strip ".online" from my email address to email
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Al" <alr@ihostuhost.net> wrote in message
> news tqpCcZDFHA.3688@TK2MSFTNGP14.phx.gbl...
> >I am using dnscmd to add and delete A records to our domain the commands
> > both complete successfully, but after a /RecordDelete when you ping the
> > just
> > removed host you still resolve the ip address which was just deleted.
> > However when you check from the console the record is indeed deleted.
> > /ZoneWriteback, /ZoneRefresh or /ZoneReload seem to have no effect.
> >
> > Is there a setting I am missing on the Server?
> >
> >
>
>

Archived from groups: microsoft.public.win2000.dns (More info?)

Thanks for your suggestion Mark, however that does not solve the problem. I
think the data is cached somewhere, becuase with a /ZoneWriteback you can
actually see that the record is deleted from the DNS file. Still the remote
machines keep resolving the name to the deleted ip address

What I am trying to accomplish is to be able to connect to our customers
remotely, but since their ip addresses change all the time we have written a
script which checks their ip address and if it is different we want it to be
written to our DNS server, so that we can always access their machines. I
think the "dnscmd" tool should be the best tool for this, but would a WMI
scipt be any different?


"Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message
news:umm8IjZDFHA.392@TK2MSFTNGP14.phx.gbl...
> Hi Al
>
> It's probably because the requests is cached locally. After the deletion,
> try an
>
> ipconfig /flushdns
>
> The test.
>
> HTH
> --
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: markreno@online.microsoft.com
>
> Please note you'll need to strip ".online" from my email address to email
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Al" <alr@ihostuhost.net> wrote in message
> news tqpCcZDFHA.3688@TK2MSFTNGP14.phx.gbl...
> >I am using dnscmd to add and delete A records to our domain the commands
> > both complete successfully, but after a /RecordDelete when you ping the
> > just
> > removed host you still resolve the ip address which was just deleted.
> > However when you check from the console the record is indeed deleted.
> > /ZoneWriteback, /ZoneRefresh or /ZoneReload seem to have no effect.
> >
> > Is there a setting I am missing on the Server?
> >
> >
>
>

Archived from groups: microsoft.public.win2000.dns (More info?)

I had forgotten to change the TTL from the default one hour. All good Now.


"Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message
news:umm8IjZDFHA.392@TK2MSFTNGP14.phx.gbl...
> Hi Al
>
> It's probably because the requests is cached locally. After the deletion,
> try an
>
> ipconfig /flushdns
>
> The test.
>
> HTH
> --
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: markreno@online.microsoft.com
>
> Please note you'll need to strip ".online" from my email address to email
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Al" <alr@ihostuhost.net> wrote in message
> news tqpCcZDFHA.3688@TK2MSFTNGP14.phx.gbl...
> >I am using dnscmd to add and delete A records to our domain the commands
> > both complete successfully, but after a /RecordDelete when you ping the
> > just
> > removed host you still resolve the ip address which was just deleted.
> > However when you check from the console the record is indeed deleted.
> > /ZoneWriteback, /ZoneRefresh or /ZoneReload seem to have no effect.
> >
> > Is there a setting I am missing on the Server?
> >
> >
>
>