Can't update domain, can't reach domain

folaht · December 2, 2017, 6:36am

Setup

Yunohost Server (Xroklaus)
- Raspberry Pi 3
  - Debian/Yunohost
    - Duniter
Desktop computer (MyComputer)
- ASRock
  - Arch Linux

I cannot ping or reach my domain.

[me@MyComputer ~]$ ping -6 duniter-folatt.nohost.me
ping: duniter-folatt.nohost.me: Name or service not known

[me@MyComputer ~]$ ssh admin@folatt-duniter.nohost.me
ssh: Could not resolve hostname folatt-duniter.nohost.me: Name or service not known

Locally

admin@Xroklaus:~ $ sudo yunohost dyndns update
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:      0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;nohost.me.			IN	SOA

;; UPDATE SECTION:
_xmpp-client._tcp.duniter-folatt.nohost.me. 0 ANY ANY 
_xmpp-server._tcp.duniter-folatt.nohost.me. 0 ANY ANY 
muc.duniter-folatt.nohost.me. 0	ANY	ANY	
pubsub.duniter-folatt.nohost.me. 0 ANY	ANY	
vjud.duniter-folatt.nohost.me. 0 ANY	ANY	
duniter-folatt.nohost.me. 0	ANY	ANY	
duniter-folatt.nohost.me. 0	ANY	ANY	
mail._domainkey.duniter-folatt.nohost.me. 0 ANY	ANY 
_dmarc.duniter-folatt.nohost.me. 0 ANY	ANY	
duniter-folatt.nohost.me. 0	ANY	ANY	
*.duniter-folatt.nohost.me. 0	ANY	ANY	
_xmpp-client._tcp.duniter-folatt.nohost.me. 3600 IN SRV	0 5 5222 duniter-folatt.nohost.me.
_xmpp-server._tcp.duniter-folatt.nohost.me. 3600 IN SRV	0 5 5269 duniter-folatt.nohost.me.
muc.duniter-folatt.nohost.me. 3600 IN	CNAME	duniter-folatt.nohost.me.
pubsub.duniter-folatt.nohost.me. 3600 IN CNAME	duniter-folatt.nohost.me.
vjud.duniter-folatt.nohost.me. 3600 IN	CNAME	duniter-folatt.nohost.me.
duniter-folatt.nohost.me. 3600	IN	MX	10 duniter-folatt.nohost.me.
duniter-folatt.nohost.me. 3600	IN	TXT	"v=spf1 a mx ip6:2001:983:8610:1:2239:6fcb:6144:21d2 -all"
mail._domainkey.duniter-folatt.nohost.me. 3600 IN TXT "v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDKacF1vAOtfxe9F3nrW6vw+cZj+Y8Klwb5z0pnLs7y5p82kkxoZPdJ/H4jA4qmxnLF4C0scYTZkQLuLyGkSnGJdZink/ZhjdvFKhwVkFqF+sNNGOcaBwnGgTJxLAXvh/vKaOB1zs6alHGNqouX5ppMQzNFCygRx4o3BECrOCFMEwIDAQAB"
_dmarc.duniter-folatt.nohost.me. 3600 IN TXT	"v=DMARC1\; p=none"
duniter-folatt.nohost.me. 3600	IN	AAAA	2001:983:8610:1:2239:6fcb:6144:21d2
*.duniter-folatt.nohost.me. 3600 IN	AAAA	2001:983:8610:1:2239:6fcb:6144:21d2

Success! Your IP address has been updated on DynDNS

admin@Xroklaus:~ $ dig A duniter-folatt.nohost.me

; <<>> DiG 9.9.5-9+deb8u13-Raspbian <<>> A duniter-folatt.nohost.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10438
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;duniter-folatt.nohost.me.	IN	A

;; ANSWER SECTION:
duniter-folatt.nohost.me. 0	IN	A	my.ip.v.4

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Dec 02 06:33:22 UTC 2017
;; MSG SIZE  rcvd: 58

admin@Xroklaus:~ $ dig AAAA duniter-folatt.nohost.me

; <<>> DiG 9.9.5-9+deb8u13-Raspbian <<>> AAAA duniter-folatt.nohost.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41937
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;duniter-folatt.nohost.me.	IN	AAAA

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Dec 02 06:33:37 UTC 2017
;; MSG SIZE  rcvd: 42

From outside

[me@MyComputer ~]$ dig A duniter-folatt.nohost.me

; <<>> DiG 9.11.2 <<>> A duniter-folatt.nohost.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10402
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;duniter-folatt.nohost.me.	IN	A

;; AUTHORITY SECTION:
nohost.me.		10	IN	SOA	ns0.yunohost.org. hostmaster.yunohost.org. 42877 10800 3600 604800 10

;; Query time: 41 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Sat Dec 02 07:31:08 CET 2017
;; MSG SIZE  rcvd: 116
[me@MyComputer ~]$ dig AAAA duniter-folatt.nohost.me

; <<>> DiG 9.11.2 <<>> AAAA duniter-folatt.nohost.me
;; global options: +cmd
;; connection timed out; no servers could be reached

/etc/hosts

::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

::1             folatt-duniter.nohost.me
::1             Xroklaus

folaht · December 5, 2017, 9:27am

bump bump bump

folaht · December 5, 2017, 2:23pm

bump bump bump

Aleks · December 5, 2017, 2:29pm

Spamming the thread and the chat won’t help. Your post does not describe properly your issue, you just pasted command dumps with no proper explanation of what is your setup, what you are doing, what you expect, and what you tried to investigate/understand the issue.

According to : https://www.whatsmydns.net/#AAAA/duniter-folatt.nohost.me , there doesn’t seem to be any issue with your domain name.

folaht · December 5, 2017, 4:57pm

It did. You posted. But my apologies for not understanding why I was not recieving an answer.
I’ve been having IPv6 issues for a month now and I got frustrated.
It’s the one thing (or one of two things) standing in the way of starting my own Duniter cryptocoin (j’espere).

Your post does not describe properly your issue,

The issue is simple. I can’t reach my domain.

you just pasted command dumps with no proper explanation of what is your setup

It’s a Raspberry Pi running Yunohost and Duniter.

what you are doing, what you expect

I have updated my folatt-duniter.nohost.me domain with IPv6 records and without IPv4 records.
I’m assuming and expecting an answer section when I do dig AAAA duniter-folatt.nohost.me and no answer when I do dig A duniter-folatt.nohost.me. It returns the opposite.

and what you tried to investigate/understand the issue.

Nothing. The dyndns update went succesfully, but it doesn’t show from outside.
I concluded that this is an issue with the Yunohost server that I have no access to
and that the only people who can help me are those who have access to it.

I did not know about the whatsmydns.net site.

jibecfed · December 5, 2017, 10:23pm

As far as I know, there is no support for a fully IPv6 ready YunoHost, please restore a more common DNS record if you want it to work.
If you have motivation (and time), you can dig yourself on reasons why YunoHost isn’t fully compatible on ipv6 only settings. You’ll be then able to explain whats the source of the issue to devs and fix it for your configuration

Once you fix it for you and explained it, the few people doing some devs can then decide if your fix is applicable for most configuration, or needs a rework (there is so many hedges-cases with networks…).

I’m exited to see what you will come with, because having a fully compatible IPV6-only YunoHost is a great goal

folaht · December 6, 2017, 1:06am

I can’t go to IPv4. My personal server is on that ip and I need port 80/443 for both servers.
So I’ll have to dig into this.

folaht · December 6, 2017, 1:29am

More oddness with not being able to find ipv6 addresses.

[me@MyComputer ~]$ nslookup -querytype=aaaa google.com
Server:		192.168.178.1
Address:	192.168.178.1#53

Non-authoritative answer:
Name:	google.com
Address: 2a00:1450:4013:c00::65

[me@MyComputer ~]$ nslookup -querytype=a mydomain.tld
Server:		192.168.178.1
Address:	192.168.178.1#53

Non-authoritative answer:
Name:	mydomain.tld
Address: my.ip.v.4

[me@MyComputer ~]$ nslookup -querytype=aaaa mydomain.tld
;; connection timed out; no servers could be reached

[me@MyComputer ~]$ nslookup -querytype=aaaa duniter-folatt.nohost.me
;; connection timed out; no servers could be reached

folaht · December 6, 2017, 10:01am

I have been told the following from freenode #networking:

ns0.yunohost.org doesn’t have an AAAA record.
ns1.yunohost.org has one, is pingable, but doesn’t respond to dns queries.

I’ve asked them if this means that Yunohost’s dns servers are broken?

And they’ve responded with: ‘That seems to be the case. Good luck.’

[me@MyComputer ~]$ dig -6 -t aaaa duniter-folatt.nohost.me @ns0.yunohost.org
dig: couldn't get address for 'ns0.yunohost.org': not found

[me@MyComputer ~]$ dig -6 -t aaaa duniter-folatt.nohost.me @ns1.yunohost.org

; <<>> DiG 9.11.2 <<>> -6 -t aaaa duniter-folatt.nohost.me @ns1.yunohost.org
;; global options: +cmd
;; connection timed out; no servers could be reached
[me@MyComputer ~]$ dig -6 -t aaaa duniter-folatt.nohost.me @publicdns.google.com

; <<>> DiG 9.11.2 <<>> -6 -t aaaa duniter-folatt.nohost.me @publicdns.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62626
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;duniter-folatt.nohost.me.	IN	AAAA

;; Query time: 2055 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Wed Dec 06 10:06:06 CET 2017
;; MSG SIZE  rcvd: 53

I’ve replaced duniter-folatt.nohost.me with:
libre-energie.nohost.me
pyche.nohost.me
cosmicweb.noho.st
and several others giving me the same result.

folaht · December 6, 2017, 1:24pm

For whatever reason, this now has recently changed and I can finally find all nohost.me AAAA records.

[me@MyComputer ~]$ dig -t aaaa duniter-folatt.nohost.me @ns0.yunohost.org

; <<>> DiG 9.11.2 <<>> -t aaaa duniter-folatt.nohost.me @ns0.yunohost.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47956
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;duniter-folatt.nohost.me.	IN	AAAA

;; ANSWER SECTION:
duniter-folatt.nohost.me. 3600	IN	AAAA	2001:983:8610:1:2239:6fcb:6144:21d2

;; AUTHORITY SECTION:
nohost.me.		3600	IN	NS	ns0.yunohost.org.
nohost.me.		3600	IN	NS	ns1.yunohost.org.

;; Query time: 30 msec
;; SERVER: 91.224.148.92#53(91.224.148.92)
;; WHEN: Wed Dec 06 14:22:58 CET 2017
;; MSG SIZE  rcvd: 129

However I cannot ping any of the domain names. Not my own, not others.

[me@MyComputer ~]$ ping duniter-folatt.nohost.me
ping: duniter-folatt.nohost.me: Name or service not known
[me@MyComputer ~]$ ping klimek.nohost.me
PING klimek.nohost.me(200116b80217a300fd416e402cc7ff06.dip.versatel-1u1.de (2001:16b8:217:a300:fd41:6e40:2cc7:ff06)) 56 data bytes