Re: txt record not returning a value

On 11/8/24 10:37, Frank @ Kiwazo via Pdns-users wrote:
>
>
>> On 8 Nov 2024, at 16:23, Brian Candler via Pdns-users 
>> <[email protected]> wrote:
>>
>> On 08/11/2024 15:18, Curtis Maurand via Pdns-users wrote:
>>> From the sql query “select * from records where domain_id=’47’ and 
>>> type=’txt’” I get
>>>
>>> | 638 |        47 | circadianinfo.com._report._dmarc.xyonet.com | 
>>> TXT | v=DMARC1
>>>
>>> Dig returns nothing.
>>>
>>> ; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> txt @localhost 
>>> circadininfo.com.
>>
>> circadininfo != circadianinfo
>>
>
> Besides that, your ns1 and ns2 seem to disagree:
>
> ns1 doesn't have the info:
>
> ❯ dig txt circadianinfo.com._report._dmarc.xyonet.com @ns1.xyonet.com.
>
> ; <<>> DiG 9.10.6 <<>> txt circadianinfo.com._report._dmarc.xyonet.com 
> @ns1.xyonet.com.
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32216
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
> ;; WARNING: recursion requested but not available
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;circadianinfo.com._report._dmarc.xyonet.com. INTXT
>
> ;; Query time: 116 msec
> ;; SERVER: 208.105.217.26#53(208.105.217.26)
> ;; WHEN: Fri Nov 08 16:33:34 CET 2024
> ;; MSG SIZE  rcvd: 72
>
> While ns2 does have the record:
>
> ❯ dig txt circadianinfo.com._report._dmarc.xyonet.com @ns2.xyonet.com.
>
> ; <<>> DiG 9.10.6 <<>> txt circadianinfo.com._report._dmarc.xyonet.com 
> @ns2.xyonet.com.
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14455
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
> ;; WARNING: recursion requested but not available
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;circadianinfo.com._report._dmarc.xyonet.com. INTXT
>
> ;; ANSWER SECTION:
> circadianinfo.com._report._dmarc.xyonet.com. 3600 IN TXT "v=DMARC1"
>
> ;; Query time: 106 msec
> ;; SERVER: 173.198.227.84#53(173.198.227.84)
> ;; WHEN: Fri Nov 08 16:34:05 CET 2024
> ;; MSG SIZE  rcvd: 93
>
>
> I suggest you check what's going on there... On top of that, there 
> seem to be dnssec errors as well for that zone. Inserting things into 
> a DB backend directly is considered bad. Doing that for a dnssec 
> signed zone is very bad. Try to run a rectify-zone and see if that 
> improves...
>

I never checked that.  Interesting.  ns2 is running bind. So pdns 
authoritative pushed the record to the slave, but doesn't serve up the 
record itself.  Have I found a bug?  maybe I should delete the record in 
the primary and add it via pdns-util.  hmm

--Curtis
>
>
> Frank
>
> _______________________________________________
> Pdns-users mailing list
> [email protected]
> https://mailman.powerdns.com/mailman/listinfo/pdns-users

_______________________________________________
Pdns-users mailing list
[email protected]
https://mailman.powerdns.com/mailman/listinfo/pdns-users