Matus UHLAR - fantomas wrote:
If you use cisco routers, ask network admins to disable any DNS "fixup"
functionality, because that usually causes problems.
On 14.02.20 12:47, Tony Finch wrote:
In my experience all Cisco PIX/ASA fuxup options are horribly broken and
should be turned off.
I
On 11/02/2020 15:28, Warren Kumari wrote:
> On Tue, Feb 11, 2020 at 3:12 AM Stephane Bortzmeyer wrote:
>>
>> On Mon, Feb 10, 2020 at 02:32:55PM -0500,
>> Warren Kumari wrote
>> a message of 70 lines which said:
>>
>>> Also, can you try:
>>> dig +tcp . axfr @192.0.32.132
>>> dig +tcp . axfr
On 14.02.20 09:32, von Dein, Thomas wrote:
As reported we were unable to transfer the root zone for 1 week, then the
expire time was over and we had an outage.
unfortunately this happens when you decide to mirror root zone and it fails.
you should use more primary servers when possible and
Matus UHLAR - fantomas wrote:
>
> unfortunately this happens when you decide to mirror root zone and it fails.
>
> you should use more primary servers when possible and change root zone
> type from secondary to hint if it fails.
In this particular case, adding more primaries would not have
I've got one follow-up question:
As reported we were unable to transfer the root zone for 1 week, then the
expire time was over and we had an outage. Now we've seen in the logs many many
log entries as the following on slave nameservers during that week when our
local copy were still valid but
5 matches
Mail list logo
