> I was curious about the additional section count dig is
> reporting. I had to do a packet capture to prove it to myself,
> but there is an additional records section returned in the
> answer from 183.47.126.169. It is the edns OPT pseudosection
> which is also shown in my dig output:
You
Hi Håvard,
I was curious about the additional section count dig is reporting. I
had to do a packet capture to prove it to myself, but there is an
additional records section returned in the answer from 183.47.126.169.
It is the edns OPT pseudosection which is also shown in my dig output:
% dig
> You are wrong if you think the SOA record is only informal.
> It's not, see https://www.rfc-editor.org/rfc/rfc2308 for more
> details.
Exactly. The SOA record included in the "Authority section" of an
NXDOMAIN ("name does not exist") or NODATA ("answer count" = 0,
i.e. indicating "name exists,
You are wrong if you think the SOA record is only informal. It’s not, see
https://www.rfc-editor.org/rfc/rfc2308 for more details.
Then
> In a similar way, bind should not object to the SOA mail contect being valid,
> as a surprising number of zones actually fail to handle mail to that address
On 2023-07-07 12:17, Emmanuel Fusté wrote:
Le 07/07/2023 à 11:57, Jakob Bohm via bind-users a écrit :
On 2023-06-02 05:02, Jesus Cea wrote:
On 2/6/23 4:25, Mark Andrews wrote:
Yep, some people just don’t take care with delegations. Complain
to Huawei.
Complain to the other companies you
Le 07/07/2023 à 11:57, Jakob Bohm via bind-users a écrit :
On 2023-06-02 05:02, Jesus Cea wrote:
On 2/6/23 4:25, Mark Andrews wrote:
Yep, some people just don’t take care with delegations. Complain to
Huawei.
Complain to the other companies you list in your followup email.
All it takes to
On 2023-06-02 05:02, Jesus Cea wrote:
On 2/6/23 4:25, Mark Andrews wrote:
Yep, some people just don’t take care with delegations. Complain to
Huawei.
Complain to the other companies you list in your followup email.
All it takes to fix this is to change the name of the zone on the
child
On 6/7/23 12:17 AM, Jesus Cea wrote:
The list is quite long, in a few minutes I have a 859 unique requests
with the same configuration error. Interestingly, quite a few from
"ntp.org". For example:
resolver: notice: DNS format error from 102.130.49.148#53 resolving
On 2/6/23 4:25, Mark Andrews wrote:
Yep, some people just don’t take care with delegations. Complain to Huawei.
Complain to the other companies you list in your followup email.
Huawei is already notified, days ago. No reply and no changes so far.
The list is quite long, in a few minutes I
> On 02/06/2023 13:59, Jesus Cea wrote:
>> On 2/6/23 10:38, Cathy Almond wrote:
>>> Has this just started - as in, it worked before ... when?
>>
>> No idea. We have been biten by this because a new client. The issue
>> could be for ages, no idea.> That may be so. For the client, they're
>>
On 02/06/2023 13:59, Jesus Cea wrote:
> On 2/6/23 10:38, Cathy Almond wrote:
>> Has this just started - as in, it worked before ... when?
>
> No idea. We have been biten by this because a new client. The issue
> could be for ages, no idea.> That may be so. For the client, they're
getting a
On 2/6/23 7:59, Nick Tait via bind-users wrote:
On 2/06/23 15:02, Jesus Cea wrote:
What I get from your reply is that BIND is not expected to do anything
about this. It is a bit disappointed but I agree that BIND is doing
the right thing. Too bad big players don't care. But I need to "solve"
On 2/6/23 10:38, Cathy Almond wrote:
Has this just started - as in, it worked before ... when?
No idea. We have been biten by this because a new client. The issue
could be for ages, no idea.
It sounds like 'they changed something', possibly by accident (maybe
adding more servers or
On 01/06/2023 15:58, Jesus Cea wrote:
I am getting errors "Name huawei.com (SOA) not subdomain of zone
cloud.huawei.com". The problem raises when requesting on
oauth-login.cloud.huawei.com . The problem was described in the mailing
list:
On 2/06/23 15:02, Jesus Cea wrote:
What I get from your reply is that BIND is not expected to do anything
about this. It is a bit disappointed but I agree that BIND is doing
the right thing. Too bad big players don't care. But I need to "solve"
this, so dropping BIND (nooo!) or patching
On 2/6/23 4:25, Mark Andrews wrote:
Yep, some people just don’t take care with delegations. Complain to Huawei.
Complain to the other companies you list in your followup email.
All it takes to fix this is to change the name of the zone on the child servers
(ns3.dnsv5.com,
Yep, some people just don’t take care with delegations. Complain to Huawei.
Complain to the other companies you list in your followup email.
All it takes to fix this is to change the name of the zone on the child servers
(ns3.dnsv5.com, gns1.huaweicloud-dns.org and ns4.dnsv5.com) from
On 1/6/23 17:00, Ondřej Surý wrote:
From top of my head - try disabling QNAME minimization.
I don't see the relevance but I tried "qname-minimization off" in my
configuration. No changes, I still see the SERVFAIL.
I insist this is not a bug in BIND. The original domain is
misconfigured.
On 1/6/23 17:00, Ondřej Surý wrote:
From top of my head - try disabling QNAME minimization.
I don't see the relevance but I tried "qname-minimization off" in my
configuration. No changes, I still see the SERVFAIL.
I insist this is not a bug in BIND. The original domain is
misconfigured.
From top of my head - try disabling QNAME minimization.
Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 1. 6. 2023, at 16:58, Jesus Cea wrote:
>
> I am
I am getting errors "Name huawei.com (SOA) not subdomain of zone
cloud.huawei.com". The problem raises when requesting on
oauth-login.cloud.huawei.com . The problem was described in the mailing
list:
https://lists.isc.org/pipermail/bind-users/2021-January/104064.html
BIND is replying
21 matches
Mail list logo
