i continued my session with chatgpt to diagnose this weird name resolution issue today a little. as the session got longer the browser tab got slower and eventually crashed on my old overloaded system here is the dns resolver chatgpt made, in its typical procedural style. the output looks nice, it successfully resolves the name when glibc 2.40 won't. most of the session was working with system configuration issues, using other versions of glibc etc. i didn't get to the point of making a clear network log of the failing and working cases. but it looks like even the latest glibc fails on this request. it's stonkson.xyz from 8.8.8.8 today when connected to Lowe's wifi here Sending DNS query for stonkson.xyz Packet data (size: 30): 00000000 35 80 01 00 00 01 00 00 00 00 00 00 08 73 74 6f |5............sto| 00000010 6e 6b 73 6f 6e 03 78 79 7a 00 00 01 00 01 |nkson.xyz.....| Received DNS response Packet data (size: 73): 00000000 35 80 81 80 00 01 00 01 00 00 00 00 08 73 74 6f |5............sto| 00000010 6e 6b 73 6f 6e 03 78 79 7a 00 00 01 00 01 c0 0c |nkson.xyz.......| 00000020 00 05 00 01 00 00 00 01 00 1f 08 73 69 6e 6b 68 |...........sinkh| 00000030 6f 6c 65 10 70 61 6c 6f 61 6c 74 6f 6e 65 74 77 |ole.paloaltonetw| 00000040 6f 72 6b 73 03 63 6f 6d 00 |orks.com.| Response ID: 0x3580 Flags: 0x8180 Questions: 1, Answers: 1, Authority Records: 0, Additional Records: 0 Answer 1: Type: 5, TTL: 1, Data length: 31 CNAME: .sinkhole.paloaltonetworks.com.