W
W C Hull
I need some info regarding Stub zones and how to control the time to live on
records cached entries in Windows 2003 DNS.
Here's my issue....We have 2 rather large zones in one of our domain
environments. Currently, there are secondary zone copies of these zones on
our two main DNS servers that are in a different domain environment. We
were thinking about removing the secondary zones and replacing them with
stub zones thinking that this would be more efficient to have DNS queries
get routed by the stub zones directly the primaries.
When we setup some test stub zones on our two DNS servers the first query
worked just great but after we changed the IP addresses of some of the
records are DNS queries kept showing the old address instead of the new.
What we discovered a bit later was that the DNS server was creating a cache
of the queried entries for that stub zone and that the cached entries were
of the old IP. It was my impression that a query for a stub zone record
would be sent to the primary zone and that the cache would not be checked
but it appears that I was wrong.
So...My problem is that we get requests all the time to change IP addresses
on devices and today, thru scripting, we update the primary zone and force a
secondary zone transfer to occur immediately so the secondary zones get
updated. With a stub zone there is nothing to update so I either need a
means of setting any record queried from that stub zone to have a VERY short
life when it gets placed into cache or I need some means of removing a
single record from Microsoft DNS's cache without having to flush the entire
cache. Can someone point me in the right direction in regard to this
problem?
Thanks,
records cached entries in Windows 2003 DNS.
Here's my issue....We have 2 rather large zones in one of our domain
environments. Currently, there are secondary zone copies of these zones on
our two main DNS servers that are in a different domain environment. We
were thinking about removing the secondary zones and replacing them with
stub zones thinking that this would be more efficient to have DNS queries
get routed by the stub zones directly the primaries.
When we setup some test stub zones on our two DNS servers the first query
worked just great but after we changed the IP addresses of some of the
records are DNS queries kept showing the old address instead of the new.
What we discovered a bit later was that the DNS server was creating a cache
of the queried entries for that stub zone and that the cached entries were
of the old IP. It was my impression that a query for a stub zone record
would be sent to the primary zone and that the cache would not be checked
but it appears that I was wrong.
So...My problem is that we get requests all the time to change IP addresses
on devices and today, thru scripting, we update the primary zone and force a
secondary zone transfer to occur immediately so the secondary zones get
updated. With a stub zone there is nothing to update so I either need a
means of setting any record queried from that stub zone to have a VERY short
life when it gets placed into cache or I need some means of removing a
single record from Microsoft DNS's cache without having to flush the entire
cache. Can someone point me in the right direction in regard to this
problem?
Thanks,