DNS query for TXT record type does not return domain connect info at GoDaddy

[sql-sith]

DNS query for TXT record type does not return domain connect info at GoDaddy

[arnoldblinn]

The spec actually says that it should respond to a TXT record query.

Directly from the spec:

As a practical matter of implementation, the DNS Provider may or may not contain a copy of this data in each and every zone. Instead, the DNS Provider must simply respond to the DNS query for the _domainconnect TXT record with the appropriate data.

How this is implemented is up to the DNS Provider.

For example, the DNS Provider may not store the data inside a TXT record for the domain, opting instead to put a CNAME in the zone and have the TXT record in the target of the CNAME. Another DNS Provider may simply respond with the appropriate records at the DNS layer without having the data in each zone.

[sql-sith]

Hi Arnold, and thanks for the reply. I didn't read the whole spec, but I did look at every reference to TXT records, including the one you cite. Reading your response has led me to shift my focus a bit.

It looks like you're saying that the DNS system should respond to a TXT query for _domainconnect. If so, I agree completely.

However, my example shows that querying for TXT records for the databaseguy.com zone does not return _domainconnect information. It does not matter if I explicitly request the _domainconnect record or just request all the TXT records.

Rather, in order to get the _domainconnect information, I either have to query it as a string without a record type (eg: dig _domainconnect.databaseguy.com.) or specifically as a CNAME (dig CNAME _domainconnect.databaseguy.com.).

So the GoDaddy implementation does not "respond to the DNS query for the _domainconnect TXT record," as the spec states, regardless of how the information is stored.

[pawel-kow]

Hi @sql-sith,

Everything is OK, you just need to query TXT on _domainconnect.databaseguy.com not databaseguy.com. Using CNAME for the record, which in results returns required TXT is just an implementation choice that is fully in compliance with DNS spec and part of normal DNS resolution. We do the same at 1&1 IONOS.

root@localhost:~# dig +noadditional +noauthority TXT _domainconnect.databaseguy.com.

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +noadditional +noauthority TXT _domainconnect.databaseguy.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49481
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 8, ADDITIONAL: 17

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_domainconnect.databaseguy.com.        IN      TXT

;; ANSWER SECTION:
_domainconnect.databaseguy.com. 3510 IN CNAME   _domainconnect.gd.domaincontrol.com.
_domainconnect.gd.domaincontrol.com. 3510 IN TXT "domainconnect.api.godaddy.com"

[sql-sith]

@arnoldblinn / @pawel-kow, thank you both for setting me straight. I can now simultaneously hang my head in embarrassed shame for lack of knowledge, but hold that same head high for (finally) beginning to learn about the domain connect spec.