Once again, many thanks to all participants of the discussion! It's nice to
know that I'm not alone with my problems.
I think the topic can be considered closed.
сб, 2 апр. 2022 г. в 21:38, Anand Buddhdev :
> On 02/04/2022 19:47, Dzmitry Shykuts wrote:
>
> Hi Dzmitry,
>
> > I have some questions
On 02/04/2022 19:47, Dzmitry Shykuts wrote:
Hi Dzmitry,
I have some questions about this situation.
What causes this "address fetching loop"?
Maybe it's a bug/future in the BIND software?
Misconfigured .BY zone and its servers?
Problem with root servers or TLD?
Why does my server have this pro
Am 02.04.22 um 20:30 schrieb Dzmitry Shykuts:
I have read every post and am very grateful to everyone who took part in
the discussion.
It's good when the server is configured correctly, but here you have to
use crutches for the whole .BY zone. This has never happened in my 20
years of expe
I have read every post and am very grateful to everyone who took part in
the discussion.
It's good when the server is configured correctly, but here you have to use
crutches for the whole .BY zone. This has never happened in my 20 years of
experience.
сб, 2 апр. 2022 г. в 21:06, Ondřej Surý :
>
Read the thread, this has been already answered on the list.
Ondřej
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 2. 4. 2022, at 19:48, Dzmitry Shykuts wrote:
>
>
> I have
Am 02.04.22 um 19:47 schrieb Dzmitry Shykuts:
I have some questions about this situation.
What causes this "address fetching loop"?
Maybe it's a bug/future in the BIND software?
Misconfigured .BY zone and its servers?
Problem with root servers or TLD?
Why does my server have this problem, but
I have some questions about this situation.
What causes this "address fetching loop"?
Maybe it's a bug/future in the BIND software?
Misconfigured .BY zone and its servers?
Problem with root servers or TLD?
Why does my server have this problem, but other servers don't?
пт, 1 апр. 2022 г. в 23:41,
Add a static-stub zone for .by which has the addresses of the nameservers for
.by configured. This will break the stupid address fetching loop.
The real fix is for .by to use nameservers that are directly in .by or ones
thot don’t require a loop to get there addresses.
--
Mark Andrews
> On 2
Can anyone suggest something? Can someone tell me which server timeout? I
would be very happy for any help!
вт, 29 мар. 2022 г. в 17:02, Dzmitry Shykuts :
> Hello! Can anybody help me with periodic and critical for me SERVFAIL?
> Cannot determine the source of the problem.
>
> I have Debian 11.3
"servfail-ttl 0" doesn't help.
вт, 29 мар. 2022 г. в 18:16, Ondřej Surý :
> The .by domain is kind of bonkers…
>
> Step 1: get nameservers for 103.by:
>
> $ dig +noall +authority IN NS 103.by. @a.root-servers.net
> by. 172800 IN NS dns1.tld.becloudby.com.
> by.
On 29/03/2022 17:16, Ondřej Surý wrote:
The .by domain is kind of bonkers…
[snip]
Sascha Pollok also ran into this issue with .BY. He asked me about it,
and I found their setup to be very weird. TTL misalignment leads to
sporadic SERVFAILs. Sascha posted about it to the dns-operations list:
The .by domain is kind of bonkers…
Step 1: get nameservers for 103.by:
$ dig +noall +authority IN NS 103.by. @a.root-servers.net
by. 172800 IN NS dns1.tld.becloudby.com.
by. 172800 IN NS dns2.tld.becloudby.com.
by.
12 matches
Mail list logo
