RequestSSL Ticket on Hold | Miraheze | Page 1

exotic trail Apr 14, 2024, 3:56 PM

#

My RequestSSL ticket, #38, is still on hold. I confirm the authoritative server is configured properly. Please check, thanks!

exotic trail Apr 16, 2024, 5:34 AM

#

No. DNS is still not configured properly at Miraheze's side

true yacht Apr 16, 2024, 9:39 AM

#

@devout crypt

exotic trail Apr 20, 2024, 11:09 AM

#

Hey, any updates for now?

wicked junco Apr 20, 2024, 11:10 PM

#

@devout crypt @viscid crest

true yacht Apr 21, 2024, 6:17 AM

#

That's not true. No one has looked at this in days.

#

Yes they do

#

If you're not going to say anything of use, please desist.

exotic trail Apr 21, 2024, 8:13 AM

#

Thanks for the update.

exotic trail Apr 28, 2024, 6:12 AM

#

As per section 4.1.1 of the RFC a Refused response indicates that the server refused to perform such operation, querying A on the domain is not possible to complete.

I have a standard procedure on requesting services, and I take quality control in a serious manner. I don't know why you reached to the conclusion that my DNS provider didn't inform you of the configuration change, but the configuration is valid from the time the request was made.
"NS" DNS records for wkmr.liao.media, [DNS server 198.41.0.4]:

Additional records:

v2n1.nic.media. 172800 IN A 161.232.11.3
v2n1.nic.media. 172800 IN AAAA 2a01:8840:f5:0:0:0:0:3
v0n1.nic.media. 172800 IN A 65.22.21.3
v0n1.nic.media. 172800 IN AAAA 2a01:8840:17:0:0:0:0:3
v0n3.nic.media. 172800 IN A 161.232.10.3
v0n3.nic.media. 172800 IN AAAA 2a01:8840:f4:0:0:0:0:3
v2n0.nic.media. 172800 IN A 65.22.23.3
v2n0.nic.media. 172800 IN AAAA 2a01:8840:19:0:0:0:0:3
v0n0.nic.media. 172800 IN A 65.22.20.3
v0n0.nic.media. 172800 IN AAAA 2a01:8840:16:0:0:0:0:3
v0n2.nic.media. 172800 IN A 65.22.22.3
v0n2.nic.media. 172800 IN AAAA 2a01:8840:18:0:0:0:0:3
"NS" DNS records for wkmr.liao.media, [DNS server 161.232.11.3]:
liao.media nameserver = ns1-32.azure-dns.com
liao.media nameserver = ns2-32.azure-dns.net
liao.media nameserver = ns3-32.azure-dns.org
liao.media nameserver = ns4-32.azure-dns.info
"NS" DNS records for wkmr.liao.media, [DNS server ns1-32.azure-dns.com]:
wkmr.liao.media nameserver = ns1.miraheze.org
wkmr.liao.media nameserver = ns2.miraheze.org

#

@MacFan4000
Hello,

Thanks for the reply.

The most recent comment regarding the DNS configuration was made by Agent saying querying A failed. I've updated him accordingly.

According to RFC 1035, per section 3.3.11, NS records lead to A records being responded by the zone it is referenced, when using as a referral to a foreign DNS server. Furthermore, section 2.1 indicates that, "From the resolver's point of view, the database that makes up the domainspace is distributed among various name servers. Different parts of thedomain space are stored in different name servers, although a particular
data item will be stored redundantly in two or more name servers," which means, under this case, that all DNS servers as referenced by NS records which are involved in querying the domain wkmr.liao.media must be responded with either announcing the query result, or with announcing no results. Unfortunately, as previously stated, querying A for wkmr.liao.media on ns1.miraheze.org returned returned a Server refused error, as indicated in the SSLRequest form.

📎 message.txt 📎 message.txt

#RequestSSL Ticket on Hold