Rambler OP wrote on December 18, 2020 at 4:13 PM

Reply to comment by cypherpunks in Help accessing YGG domains. by Rambler

I guess I'm wondering : Where exactly do I use his DNS servers at?

Is this something I add to my yggdrasil.conf, something I add to a local host file, etc. Couldn't quite figure it out as everything failed when attempted. I tried adding them in several areas locally with no success.

I am pleased to see that ramble.ygg resolves however, that's a relief.

cypherpunks wrote on December 18, 2020 at 7:05 PM

Depends on your system. In case it's Linux, it should go to /etc/resolv.conf, but it usually gets overwritten by network manager of choice.

Rambler OP wrote on December 18, 2020 at 7:25 PM

Yeah, that's what I thought.

resolv.conf is overwritten, I would assume by my network manager that I use to connect to my wireless network. When adding in 'additional DNS servers' under IPV6 settings, I choose one provided by wyrd (ex: 300:4523::53 ) and save it.

Disconnect / reconnect, no go.

I'll just add 300:4523::53 anywhere I can set anything DNS related until it works I guess, haha.

Rambler OP wrote on December 19, 2020 at 1:27 AM (edited on December 19, 2020 at 2:08 AM)

Works via terminal, nowhere else. It loaded a few times via Firefox for me but that's it. Clearing everything, private window this, new browser that... Nothing.

Via terminal though, it's fine. I'm done messing with it. If it works for you and others, that's the important thing. Otherwise, the IPV6 works fine for me. I just like accessing the site through various networks depending on what I'm doing. Seems lately it's been a pretty consistent mix of I2P, Loki and clearnet. But as soon as I type in http://[ firefox completes the IPv6 for me so it's not that big of a deal on my end.


$ curl -Is ramble.ygg | head -1
HTTP/1.1 200 OK


$ ping ramble.ygg
PING ramble.ygg(200:718d:c499:3fce:c5e:65c6:73d6:f46d
(200:718d:c499:3fce:c5e:65c6:73d6:f46d)) 56 data bytes
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=1 ttl=64 time=246 ms
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=2 ttl=64 time=325 ms
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=3 ttl=64 time=250 ms

```

Rambler OP wrote on December 18, 2020 at 10:54 PM

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 on December 19, 2020 at 11:52 AM

your OS won't do AAAA lookups if you don't have any ipv6 default route.

Rambler OP wrote on December 19, 2020 at 12:09 PM

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.