[as112-ops] [gii-ops] Re: [Ext] Request to add service.arpa to AS112
Florian Obser
fobser at ripe.net
Sat Aug 31 07:23:25 UTC 2024
Hi there,
I ran a RIPE Atlas measurement using *all* probes (10225 answered):
https://atlas.ripe.net/measurements/78275087/overview
Downloading results (on the results tab) and running this script:
----------8<----------8<----------8<----------
import json
import base64
import dns.message
with open("./Downloads/RIPE-Atlas-measurement-78275087.json") as f:
for l in f:
result = json.loads(l)
if 'result' in result:
answer = result['result']['abuf'] + "=="
content = base64.b64decode(answer)
msg = dns.message.from_wire(content)
if msg.rcode() != 0:
for opt in msg.options:
if opt.otype == dns.edns.NSID:
nsid = opt.to_wire().decode('utf-8')
print("{}
{}".format(dns.rcode.to_text(msg.rcode()),nsid))
----------8<----------8<----------8<----------
yields:
$ python3 ./atlas_nsid.py | sort | uniq
NXDOMAIN
NXDOMAIN CleanBrowsing v1.6a - dns-edge-australia-sydney2
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-amsterdam5
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-frankfurt4
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-frankfurt5
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-london7
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-paris3
NXDOMAIN CleanBrowsing v1.6a - dns-edge-europe-stockholm-v
NXDOMAIN CleanBrowsing v1.6a - dns-edge-usa-east-chicago2
NXDOMAIN CleanBrowsing v1.6a - dns-edge-usa-east-newyork6
NXDOMAIN CleanBrowsing v1.6a - dns-edge-usa-west-seattle-v
NXDOMAIN DNS
NXDOMAIN chndnsrrpc04
NXDOMAIN dnssyd06.island.aussiebb.io
NXDOMAIN gpdns-bom
NXDOMAIN gpdns-gru
NXDOMAIN gpdns-lhr
NXDOMAIN gpdns-lpp
NXDOMAIN gpdns-muc
NXDOMAIN gpdns-sfo
NXDOMAIN gpdns-sof
NXDOMAIN res714.fra.rrdns.pch.net
NXDOMAIN res720.lhr.rrdns.pch.net
NXDOMAIN res760.sea.rrdns.pch.net
NXDOMAIN thwdnsrec02
REFUSED
REFUSED AS112.AS59715.NET
REFUSED DNS
REFUSED app17.ams2.hosts.meta.redstone.afilias-nst.info-1615580861
REFUSED app30.ams2.hosts.meta.redstone.afilias-nst.info-1615580861
REFUSED app4.ams2.hosts.meta.redstone.afilias-nst.info-1615580861
REFUSED as112-acc
REFUSED as112-ams
REFUSED as112-bom
REFUSED as112-chi
REFUSED as112-den
REFUSED as112-dfw
REFUSED as112-dxb
REFUSED as112-fmt1.he.net
REFUSED as112-fra
REFUSED as112-gru
REFUSED as112-hkg
REFUSED as112-iad
REFUSED as112-lax
REFUSED as112-lga
REFUSED as112-lhr
REFUSED as112-maa
REFUSED as112-man
REFUSED as112-mia
REFUSED as112-nbo
REFUSED as112-nyc6.he.net
REFUSED as112-phx
REFUSED as112-rdu
REFUSED as112-scl
REFUSED as112-sea
REFUSED as112-sin
REFUSED as112-sjc
REFUSED as112-syd
REFUSED as112-tor
REFUSED as112-waw
REFUSED as112-yul
REFUSED as112.bahnhof.net
REFUSED as112.baikal-ix.ru
REFUSED as112.datahata.by
REFUSED as112.fcix.net
REFUSED as112.paulbunyan.net
REFUSED as112.pkl.inx.net.za
REFUSED as112.romandix.ch
REFUSED as112.services.167l.mbix.ca
REFUSED as112.umh.inx.net.za
REFUSED as112.zrh.ch.massars.net
REFUSED blackhole.dns.br
REFUSED blackhole.luco.restena.lu
REFUSED chzrh01.paphosting.net
REFUSED dns4
REFUSED e1-as112-bog.edgeuno.net
REFUSED e1-as112-eze2.edgeuno.net
REFUSED e1-as112-gdl1.edgeuno.net
REFUSED e1-as112-gru1.edgeuno.net
REFUSED e1-as112-ist1.edgeuno.net
REFUSED e1-as112-mex1.edgeuno.net
REFUSED e1-as112-mia1.edgeuno.net
REFUSED e1-as112-qro1.edgeuno.net
REFUSED e1-as112-scl1.edgeuno.net
REFUSED hostname.as112.net - Gondor node
REFUSED nomen
REFUSED nomi68.percipientnetworks.com
REFUSED ns.example.net
REFUSED poppy.home.waf.hk
REFUSED res210.pdx.rrdns.pch.net
SERVFAIL
SERVFAIL 115m25
SERVFAIL 151m48
SERVFAIL 169m21
SERVFAIL 341m55
SERVFAIL 363m174
SERVFAIL 368m33
SERVFAIL 397m198
SERVFAIL 398m315
SERVFAIL 46m50
SERVFAIL 471m326
SERVFAIL 481m4
SERVFAIL 492m122
SERVFAIL 532m157
SERVFAIL 533m181
SERVFAIL 543m14
SERVFAIL 573m3
SERVFAIL 612m2
SERVFAIL 646m55
SERVFAIL 64m136
SERVFAIL 65m132
SERVFAIL 684m71
SERVFAIL 735m153
SERVFAIL 75m119
SERVFAIL 768m42
SERVFAIL 78m118
SERVFAIL 793m76
SERVFAIL 84m58
SERVFAIL 906m26
SERVFAIL 94m43
SERVFAIL r13.atl1
SERVFAIL r2001.yyz
SERVFAIL r2008.yyz
SERVFAIL r3.ams
SERVFAIL r3005.cdg1
SERVFAIL r3007.lax
Note that there are many more nodes that do not answer NOERROR and do
not provide an NSID.
Cheers,
Florian
On Thu, 29 Aug 2024 at 19:04, Kim Davies <kim.davies at iana.org> wrote:
>
> Dear all,
>
> As a follow-up to this request, an unscientific polling from a variety
> of test nodes (NLNOG RING) suggests that around 27% of sites are seeing
> service.arpa properly configured. As a point of comparison, 77% are
> seeing home.arpa properly configured.
>
> I'd encourage AS112 operators who have not yet configured service.arpa
> to do so. We intended to introduce the delegation into the .arpa zone
> next week.
>
> We are exploring the viability of using DNAME records, however our
> preliminary exploration suggests it will require some significant work
> on how the zone is administered and published. We'll continue this
> work with a view to ultimately provisioning these kinds of services
> as described in RFC 7535, but for now we will rely on conventional
> delegation for the service.arpa domain.
>
> kim
>
> Quoting To as112-ops at lists.dns-oarc.net on Monday April 29, 2024:
> > Dear AS112 operators:
> >
> > IANA is being being asked to implement the IANA considerations of a
> > new RFC-to-be, draft-ietf-dnssd-srp-25, which requires delegation of
> > "service.arpa" to black hole servers as follows:
> >
> > In order to be fully functional, the owner of the 'arpa.' zone must
> > add a delegation of 'service.arpa.' in the '.arpa.' zone [RFC3172].
> > This delegation is to be set up as was done for 'home.arpa', as a
> > result of the specification in Section 7 of [RFC8375]. This is
> > currently the responsibility of the IAB [IAB-ARPA]
> >
> > Therefore, just as with home.arpa we are requesting AS112 operators to
> > configure their AS112 nodes as soon as practical to answer queries for
> > this new zone on blackhole-[12].iana.org, so that we may delegate it in
> > the .arpa zone with those two NS records. The zone should be configured
> > with the "db.dd-empty" zone content described in RFC 7534.
> >
> > I suspect one of the questions will be whether we can use DNAME as
> > described in RFC 7535. While we have made some progress in separating
> > root server infrastructure from .ARPA infrastructure (see RFC 9120),
> > that work has not concluded and today they are still served through
> > common infrastructure.
> >
> > Our intention is to add the delegation to the .ARPA zone around mid-May,
> > to provide AS112 operators time to make this configuration update.
> >
> > Thank you in advance, and if you have any questions please let me know,
> > or respond back to this group.
> >
> > Kindest regards,
> >
> > Kim Davies
> > Internet Assigned Numbers Authority
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
> as112.net administrative requests
> ops at as112.net
--
Being fully aware that we have no control over how the Universe works
or what the future holds.
More information about the as112-ops
mailing list