Rambler OP wrote
Reply to comment by cypherpunks in Help accessing YGG domains. by Rambler
Crazy thing is when I use dig, it responds. In the browser, nothing. No .ygg will load for me. Maybe I'm misinterpreting this.
$ dig ramble.ygg AAAA @301:2522::53
; <<>> DiG 9.10.3-P4-Ubuntu <<>> ramble.ygg AAAA @301:2522::53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60331
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; CLIENT-SUBNET: 200:ac7f:495d:c674:5851:6714:128f:0/112/0
;; QUESTION SECTION:
;ramble.ygg. IN AAAA
;; ANSWER SECTION:
ramble.ygg. 3600 IN AAAA 200:718d:c499:3fce:c5e:65c6:73d6:f46d
;; AUTHORITY SECTION:
ygg. 300 IN NS ns2.ygg.
ygg. 300 IN NS ns1.ygg.
;; ADDITIONAL SECTION:
ns1.ygg. 300 IN AAAA 301:2923::53
ns2.ygg. 300 IN AAAA 301:2522::53
;; Query time: 687 msec
;; SERVER: 301:2522::53#53(301:2522::53)
;; WHEN: Fri Dec 18 17:47:51 EST 2020
;; MSG SIZE rcvd: 181
boobs wrote
your OS won't do AAAA lookups if you don't have any ipv6 default route.
Rambler OP wrote
Got it.
It works via Lynx, not sure what the deal is with the other browsers I've tried it with, but it is "working". The thing I wanted to do most was just confirm it was resolving for others, and it appears to be doing that just fine. The issues I'm experiencing seem isolated to me and only me and since I access the site mostly via I2P or Loki recently, I don't mind using the longform IPV6 if need be to access it over Yggdrasil.
I've got a ton of other stuff I'm working on and it seems that the .ygg is working, so that's good. I can access it via curl, dig, load it in lynx all fine now. Why I can't via a normal web browser even after clearing everything out, private browsing windows, etc is beyond me. Sometimes it works, sometimes it doesn't in the browser. But if it's working normally and reliably for everyone else I'm not going to fuss with it anymore, haha.
Viewing a single comment thread. View all comments