Problem with Regional SRV Records

As I have seen in other titles, sometimes there are regional problems. Please help with this. @TKlein @chris_m1

Unfortunately, my 2 SRV records are not responding. My _minecraft.tcp records are not responding in minecraft. These are my previously working records.

It’s not the first time I’m recording an SRV. It was working in this domain before. I make an SRV record on the same IP in the domains I manage in other DNS and it works. Could I be having a problem specific to this domain?

Domain: aesirmc.com
Subdomain: oyna.aesirmc.com and play.aesirmc.com

They both seem to been gone from the forums for at least 2-3 months, so I’m being curious, what exactly makes you ping these two people?

Maybe, but you would need to share a lot more specific/detailed information, for anyone to be able to attempt to dig further in to it with you:

  1. What domain?

  2. What exact record(s), do you believe there is a problem with?
    And how does your Cloudflare Dashboard look, in regards to these specific record(s)?

  3. What regional areas are you believing that you see issues in?

  4. What makes you believe that there are any problems at all?
    How exactly did you test it, or otherwise end up on that conclusion?

Domain: aesirmc.com
Subdomain: oyna.aesirmc.com and play.aesirmc.com

I saw another topic having the same problem. There, these two friends wrote that there was a regional problem and they were making arrangements. Sorry, I can’t reply under that topic.
It was working only yesterday, I’m pretty sure I didn’t make any changes, maybe I didn’t even log into cloudflare.

I am posting the A record and SRV Records as screenshots.

What is the problem you are experiencing? What error are you seeing?

These SRV records don’t really make much sense to me, as they are both pointing to the same ip.

@ahmetcann1515 -

Digging deeper, would that topic you refer to by any chance be this specific one?

Can you confirm the following pointers?

  1. It does NOT work when you are using the naked domain (e.g. aesirmc.com).

  2. It works perfectly fine, when you are using the sub-domains (e.g. oyna.aesirmc.com and play.aesirmc.com).

Was that a full screenshot including all your records at the time of the screenshot, or just a partial screenshot of the record(s) that you believe is important?

One of the reasons I’m asking is, there must be an A/AAAA record on the naked domain (aesirmc.com), however, your screenshot does not actually show it.

As such, it could be hard to figure out if something would actually be creating a conflict.

As @Laudian says here, since both the oyna.aesirmc.com and play.aesirmc.com actually point towards the exact same IP address, keeping both SRV records alive would serve no purpose at all.

I would personally remove one of them.

The missing A/AAAA record from your screenshot, could possibly be that you have added an A/AAAA record on aesirmc.com since it was working, and that was the one that took the result out over the edge.

That said:

$ dig +norec +nsid TXT _minecraft._tcp.aesirmc.com @arely.ns.cloudflare.com

; <<>> DiG 9.16.37-Debian <<>> +norec +nsid TXT _minecraft._tcp.aesirmc.com @arely.ns.cloudflare.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 805
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; NSID: 33 37 33 6d 38 30 ("373m80")
;; QUESTION SECTION:
;_minecraft._tcp.aesirmc.com.   IN      TXT

;; AUTHORITY SECTION:
aesirmc.com.            1800    IN      SOA     arely.ns.cloudflare.com. dns.cloudflare.com. 2311142258 10000 2400 604800 1800

;; Query time: 44 msec
;; SERVER: 2606:4700:50::a29f:26a4#53(2606:4700:50::a29f:26a4)
;; WHEN: Mon Jun 05 10:42:24 CEST 2023
;; MSG SIZE  rcvd: 126
$ dig +norec +nsid TXT _tcp.aesirmc.com @arely.ns.cloudflare.com

; <<>> DiG 9.16.37-Debian <<>> +norec +nsid TXT _tcp.aesirmc.com @arely.ns.cloudflare.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49997
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; NSID: 35 37 30 6d 36 35 ("570m65")
;; QUESTION SECTION:
;_tcp.aesirmc.com.              IN      TXT

;; AUTHORITY SECTION:
aesirmc.com.            1800    IN      SOA     arely.ns.cloudflare.com. dns.cloudflare.com. 2311142258 10000 2400 604800 1800

;; Query time: 40 msec
;; SERVER: 2606:4700:50::a29f:26a4#53(2606:4700:50::a29f:26a4)
;; WHEN: Mon Jun 05 10:42:30 CEST 2023
;; MSG SIZE  rcvd: 115

It doesn’t seem like your SRV record(s) (e.g. “*._tcp” label) are being exposed anywhere in the world at the time being.

Both oyna.aesirmc.com and play.aesirmc.com does however appear to have successfully propagated out worldwide, and also appeared like that a couple of days ago when I queried them as well (but didn’t get around to respond).

On one of my domains, Cloudflare did successfully export SRV records exactly like the ones appearing in your screenshot (two different priority SRV records pointing to the exact same target), so I would not exclude the possibility of some kind of zone synchronization / export failure, where a “zone rebuild” (as mentioned in the linked thread above) could fix it.

Personally, I would just try deleting one of the useless SRV records, hoping that it would fix it.

If you can at least confirm the findings above (e.g. the naked domain isn’t working, but the sub-domains does, et cetera), it would be nice.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.