Hello,
From my personnal experience I would add
* Check if you have monitoring in place, you might want to monitor all types of
queries and error messages.
* Since you have external and internal DNS then there might be firewalls
between them, check if the flows are opened and prepare a test plan
On 23/02/17 20:21, Mitchell Kuch wrote:
In practice, we have encountered caching resolvers that provide
non-decrementing TTL values to downstream resolvers and clients. Even
That is a depressingly common residential ISP trick :o(
___
Please visit htt
In message <1ca812f4-7ea0-4498-b838-bbfaf551b...@iastate.edu>, "Eldridge, Rod A
[ITNET]" writes:
>
> Iowa State University is replacing 7 ISC NAMED/BIND servers and 4 ISC DHCP
> servers with Infoblox servers on March 14th. We want to keep the domain
> names of our external servers the same (with
On Thu, Feb 23, 2017 at 2:52 PM, Eldridge, Rod A [ITNET]
wrote:
>
> Iowa State University is replacing 7 ISC NAMED/BIND servers and 4 ISC DHCP
> servers with Infoblox servers on March 14th. We want to keep the domain names
> of our external servers the same (with one exception), but we will be
On Thu, Feb 23, 2017 at 3:03 PM, Reindl Harald wrote:
>
>
> Am 23.02.2017 um 20:52 schrieb Eldridge, Rod A [ITNET]:
>>
>>
>> Iowa State University is replacing 7 ISC NAMED/BIND servers and 4 ISC DHCP
>> servers with Infoblox servers on March 14th. We want to keep the domain
>> names of our externa
Hello, Rod -
It is important to consider the TTL on the glue records at Educause/Verisign.
The EDU. root sets TTLs for each NS/A/ record for two days.
I recommend operating authoritative DNS servers at the old IP addresses for
four days after the EDU. and IASTATE.EDU. zone updates.
In pra
Am 23.02.2017 um 20:52 schrieb Eldridge, Rod A [ITNET]:
Iowa State University is replacing 7 ISC NAMED/BIND servers and 4 ISC DHCP
servers with Infoblox servers on March 14th. We want to keep the domain names
of our external servers the same (with one exception), but we will be changing
all
7 matches
Mail list logo