[dns-operations] [Ext] Re: ENT NXDOMAIN problem at .BS nameserver ns36.cdns.net

[Edward Lewis]

I think there is still something broken.

Using edu.bs, which seems to be working, the name ub.edu.bs can be resolved.  If one queries for the SOA at edu.bs, the negative answer is the right answer – showing the SOA record owned by bs.

Asking for the SOA for com.bs., the responses I see, from all three servers for bs., have an authority section pointing towards the NS set for com.bs.  This makes little sense as, if there is no soa record for com.bs, It can’t have an ns set.

It’s hard to tell remotely, but, you probably want to set up com.bs just like edu.bs.  But that’s not very reliable advice, based on not knowing the full intentions nor the contents of the zone file.

From: dns-operations <dns-operations-bounces at dns-oarc.net> on behalf of BS Domain Administrator <bsadmin at ub.edu.bs>
Date: Tuesday, September 27, 2022 at 2:32 PM
To: "dns-operations at dns-oarc.net" <dns-operations at dns-oarc.net>
Subject: [Ext] Re: [dns-operations] ENT NXDOMAIN problem at .BS nameserver ns36.cdns.net

Thank you for your email.
Please test again and let us know if the problem still occurs.

Best regards,

BSNIC
Office of Information Technology
University of The Bahamas
University Drive
PO Box N4912
Nassau, NP
The Bahamas
www.register.bs
________________________________
From: Viktor Dukhovni <ietf-dane at dukhovni.org>
Sent: Tuesday, September 20, 2022 8:33 PM
To: dns-operations at dns-oarc.net <dns-operations at dns-oarc.net>
Cc: BS Domain Technical Contact <bstech at ub.edu.bs>; BS Domain Administrator <bsadmin at ub.edu.bs>
Subject: ENT NXDOMAIN problem at .BS nameserver ns36.cdns.net

The .COM.BS is an empty non-terminal with various child domains
registered beneath.  The "ns36.cdns.net" nameserver for .BS responds
with NXDOMAIN to "com.bs" qname-minimised queries.

This in turn can and does sometimes lead to NXDOMAIN inference for the
child domains.

This nameserver needs to be withdrawn and fixed before it is returned to
service.

    2001:678:4::24    ns36.cdns.net
    194.0.1.36        ns36.cdns.net

Example responses:

@194.0.1.36

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3297
    ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;com.bs.                        IN SOA

    ;; AUTHORITY SECTION:
    bs.                     SOA     dns.nic.bs. bsadmin.cob.edu.bs. 2022092000 3600 900 1814400 9000

@2001:678:4::24

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39616
    ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;com.bs.                        IN SOA

    ;; AUTHORITY SECTION:
    bs.                     SOA     dns.nic.bs. bsadmin.cob.edu.bs. 2022092000 3600 900 1814400 9000

--
    Viktor.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20220927/bb47e3f8/attachment.html>