Hey guys check out my project I've been working on! It's a neofetch clone written in C
#Screenshots from developers & #Unix people (2002)
not exactly #unixporn 😜
Is it just me, or does Google and Quad9 modify the maximum TTL of #dns records?
"dig -t TXT ttltest01.bgp.rocks @220.127.116.11" and "dig -t TXT ttltest01.bgp.rocks @18.104.22.168" gives me a TTL of 3600 (correct).
"dig -t TXT ttltest02.bgp.rocks @22.214.171.124" and "dig -t TXT ttltest02.bgp.rocks @126.96.36.199" gives me a TTL of 22600 and 43200 but it should be 86400. Asking any other servers (like 188.8.131.52) gives me the correct TTL.
Issue fixed which made my day a lot better
A instance dedicated - but not limited - to people with an interest in the GNU+Linux ecosystem and/or general tech. Sysadmins to enthusiasts, creators to movielovers - Welcome!