On 09/08/2019 14.53, James Knott wrote:
On 2019-08-09 04:58 AM, Carlos E. R. wrote:
Maybe there is a problem with "fc00::" addresses. Do you have any such to try?
There is nothing special with those. They are the IPv6 equivalent of the IPv4 RFC1918 addresses. I use them here as well as my global addresses.
Here is one from my computer as an example: fd48:1a37:2160:0:3a:144:2a16:71cb
My DNS has no problem dealing with them at all.
Incidentally, there is a minor difference between fc and fd addresses. The fc block is supposed to come from some server somewhere, to ensure there's no overlap with someone else. With the fd block, you create your own prefix. Beyond that, there's no difference.
I take it that as my entries are invented, I should have fd addresses? Well, it makes no difference. Telcontar:~ # mcedit /etc/named/zone/valinor (failed reverse-i-search)`bind': mcedit ~/^Cn/bckall2mybook Telcontar:~ # systemctl reload named Telcontar:~ # cat /etc/nscd.conf | egrep -v "^[[:space:]]*$|^#"^C Telcontar:~ # ping -6 Isengard ping: Isengard: Name or service not known Telcontar:~ # systemctl reload nscd Telcontar:~ # ping -6 Isengard ping: Isengard: Name or service not known Telcontar:~ # systemctl restart named Telcontar:~ # ping -6 Isengard ping: Isengard: Name or service not known Telcontar:~ # systemctl restart nscd Telcontar:~ # The address does resolve: Telcontar:~ # host Isengard Isengard.valinor has address 192.168.1.16 Isengard.valinor has IPv6 address fd00::16 Telcontar:~ # Of course, as I have not changed the actual address of the machine: Telcontar:~ # ping -6 fd00::16 connect: Network is unreachable Telcontar:~ # Telcontar:~ # dig Isengard ; <<>> DiG 9.11.2 <<>> Isengard ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2739 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 29978b6c8a21268a716110005d4d9e977195f1db4b9d9811 (good) ;; QUESTION SECTION: ;Isengard. IN A ;; AUTHORITY SECTION: . 8974 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019080901 1800 900 604800 86400 ;; Query time: 33 msec ;; SERVER: 192.168.1.14#53(192.168.1.14) ;; WHEN: Fri Aug 09 18:25:59 CEST 2019 ;; MSG SIZE rcvd: 140 Telcontar:~ # dig is not answering " fd00::16" :-? Maybe it only asks for the "A", not the "AAAA". I prefer the host -v command: Telcontar:~ # host -v Isengard Trying "Isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32981 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2 ;; QUESTION SECTION: ;Isengard.valinor. IN A ;; ANSWER SECTION: Isengard.valinor. 86400 IN A 192.168.1.16 ;; AUTHORITY SECTION: valinor. 86400 IN NS Telcontar.valinor. ;; ADDITIONAL SECTION: Telcontar.valinor. 86400 IN A 192.168.1.14 Telcontar.valinor. 86400 IN AAAA fd00::14 Received 118 bytes from 192.168.1.14#53 in 0 ms Trying "Isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11391 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2 ;; QUESTION SECTION: ;Isengard.valinor. IN AAAA ;; ANSWER SECTION: Isengard.valinor. 86400 IN AAAA fd00::16 ;; AUTHORITY SECTION: valinor. 86400 IN NS Telcontar.valinor. ;; ADDITIONAL SECTION: Telcontar.valinor. 86400 IN A 192.168.1.14 Telcontar.valinor. 86400 IN AAAA fd00::14 Received 130 bytes from 192.168.1.14#53 in 0 ms Trying "Isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38238 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;Isengard.valinor. IN MX ;; AUTHORITY SECTION: valinor. 86400 IN SOA Telcontar.valinor. root.Telcontar.valinor. 2019080901 28800 7200 604800 86400 Received 85 bytes from 192.168.1.14#53 in 0 ms Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)