[Frage] Fritzbox 6360 (KD) Ipv6 deaktivieren

[disn]

Tomaten vor den Augen... sorry
DNS-Updates aus der ddnslog Datei (Teile der IP's mit xxx ersetzt)

##### BEGIN SECTION dyndns DynDNS
dyndns
-rw-r--r--    1 root     root         11149 Oct 30 14:13 /var/tmp/ddnslog_1.txt
ddnslog_1.txt:
[1970-01-01 01:00:41 v4 No-IP.com dbg]: ep=0x4294800 ddns_add_account:3996 offline -> offline
[1970-01-01 01:00:43 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[1970-01-01 01:00:43 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[1970-01-01 01:00:44 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[1970-01-01 01:00:44 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[1970-01-01 01:01:00 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[1970-01-01 01:01:00 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[1970-01-01 01:01:01 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[1970-01-01 01:01:01 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[2015-10-30 10:30:30 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 10:30:30 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[2015-10-30 10:30:34 dbg]: #### IPv4-Only WAN connection. ####
[2015-10-30 10:30:34 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 10:30:34 dbg]: v4 new 1 cnt 1
[2015-10-30 10:30:34 dbg]: !!! NEW IPv4 CONNECTION !!!
[2015-10-30 10:30:34 v4 No-IP.com dbg]: ddns_update: offline (178.xxx.xxx.27)
[2015-10-30 10:30:34 v4 No-IP.com dbg]: ep=0x4294800 ddns_update:3232 offline -> checking
[2015-10-30 10:30:34 v4 No-IP.com dbg]: new address
[2015-10-30 10:30:34 v4 No-IP.com dbg]: starting update (new address) [update_v6_addr 0] {178.xxx.xxx.27}
[2015-10-30 10:30:34 v4 No-IP.com dbg]: ep=0x4294800 do_connect:2300 checking -> updating
[2015-10-30 10:30:34 v4 No-IP.com dbg]: ep=0x4294800 ddns_closecb:2396 updating -> updated
[2015-10-30 10:30:34 v4 No-IP.com dbg]: verify handle 70054272 (delay 240)
[2015-10-30 10:30:35 dbg]: #### Dual-Stack WAN connection. ####
[2015-10-30 10:30:35 dbg]: v6 new 1 cnt 1
[2015-10-30 10:30:35 dbg]: !!! NEW IPv6 CONNECTION !!!
[2015-10-30 10:34:34 v4 No-IP.com dbg]: dns_handle created 0x4298460 for 178.xxx.xxx.27
[2015-10-30 10:34:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298460
[2015-10-30 10:34:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:34:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 10:38:34 v4 No-IP.com dbg]: dns_handle created 0x4298240 for 178.xxx.xxx.27
[2015-10-30 10:38:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298240
[2015-10-30 10:38:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:38:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 10:42:34 v4 No-IP.com dbg]: dns_handle created 0x4298680 for 178.xxx.xxx.27
[2015-10-30 10:42:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298680
[2015-10-30 10:42:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:42:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 10:46:34 v4 No-IP.com dbg]: dns_handle created 0x4298460 for 178.xxx.xxx.27
[2015-10-30 10:46:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298460
[2015-10-30 10:46:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:46:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 10:50:34 v4 No-IP.com dbg]: dns_handle created 0x4298760 for 178.xxx.xxx.27
[2015-10-30 10:50:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298760
[2015-10-30 10:50:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:50:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 10:54:34 v4 No-IP.com dbg]: dns_handle created 0x4298680 for 178.xxx.xxx.27
[2015-10-30 10:54:34 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298680
[2015-10-30 10:54:34 v4 No-IP.com dbg]: verify failed, is 91.xxx.xxx.25, but should be 178.xxx.xxx.27
[2015-10-30 10:54:34 v4 No-IP.com dbg]: ep=0x4294800 restart_verify_set_timer:1488 updated -> offline
[2015-10-30 10:54:34 v4 No-IP.com dbg]: verify failed: DNS reply: noerror.
[2015-10-30 10:54:34 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 10:54:34 v4 No-IP.com dbg]: Retry update in 300 secs.
[2015-10-30 10:59:35 v4 No-IP.com dbg]: ddns_update: offline (178.xxx.xxx.27)
[2015-10-30 10:59:35 v4 No-IP.com dbg]: ep=0x4294800 ddns_update:3232 offline -> checking
[2015-10-30 10:59:35 v4 No-IP.com dbg]: new address
[2015-10-30 10:59:35 v4 No-IP.com dbg]: starting update (new address) [update_v6_addr 0] {178.xxx.xxx.27}
[2015-10-30 10:59:35 v4 No-IP.com dbg]: ep=0x4294800 do_connect:2300 checking -> updating
[2015-10-30 10:59:38 v4 No-IP.com dbg]: ep=0x4294800 ddns_closecb:2396 updating -> updated
[2015-10-30 10:59:38 v4 No-IP.com dbg]: verify handle 70054144 (delay 240)
[2015-10-30 11:03:38 v4 No-IP.com dbg]: dns_handle created 0x4298ae0 for 178.xxx.xxx.27
[2015-10-30 11:03:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298ae0
[2015-10-30 11:03:38 v4 No-IP.com dbg]: ep=0x4294800 ddns_verify_complete:1527 updated -> complete
[2015-10-30 11:03:38 v4 No-IP.com dbg]: verified 178.xxx.xxx.27
[2015-10-30 12:42:32 dbg]: #### no WAN connection. ####
[2015-10-30 12:42:32 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 complete -> offline
[2015-10-30 12:42:32 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[2015-10-30 12:42:33 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 12:42:33 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[2015-10-30 12:42:37 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 12:42:37 v4 No-IP.com dbg]: ep=0x4294800 ddns_second:3524 offline -> offline
[2015-10-30 12:42:38 dbg]: #### IPv4-Only WAN connection. ####
[2015-10-30 12:42:38 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 12:42:38 dbg]: v4 new 1 cnt 2
[2015-10-30 12:42:38 dbg]: !!! NEW IPv4 CONNECTION !!!
[2015-10-30 12:42:38 v4 No-IP.com dbg]: ddns_update: offline (178.xxx.xxx.222)
[2015-10-30 12:42:38 v4 No-IP.com dbg]: ep=0x4294800 ddns_update:3232 offline -> checking
[2015-10-30 12:42:38 v4 No-IP.com dbg]: new address
[2015-10-30 12:42:38 v4 No-IP.com dbg]: starting update (new address) [update_v6_addr 0] {178.xxx.xxx.222}
[2015-10-30 12:42:38 v4 No-IP.com dbg]: ep=0x4294800 do_connect:2300 checking -> updating
[2015-10-30 12:42:38 v4 No-IP.com dbg]: ep=0x4294800 ddns_closecb:2396 updating -> updated
[2015-10-30 12:42:38 v4 No-IP.com dbg]: verify handle 70054016 (delay 240)
[2015-10-30 12:42:40 dbg]: #### Dual-Stack WAN connection. ####
[2015-10-30 12:42:40 dbg]: v6 new 1 cnt 2
[2015-10-30 12:42:40 dbg]: !!! NEW IPv6 CONNECTION !!!
[2015-10-30 12:46:38 v4 No-IP.com dbg]: dns_handle created 0x4298b30 for 178.xxx.xxx.222
[2015-10-30 12:46:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298b30
[2015-10-30 12:46:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 12:46:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 12:50:38 v4 No-IP.com dbg]: dns_handle created 0x42987b0 for 178.xxx.xxx.222
[2015-10-30 12:50:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x42987b0
[2015-10-30 12:50:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 12:50:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 12:54:38 v4 No-IP.com dbg]: dns_handle created 0x4298760 for 178.xxx.xxx.222
[2015-10-30 12:54:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298760
[2015-10-30 12:54:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 12:54:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 12:58:38 v4 No-IP.com dbg]: dns_handle created 0x4298b30 for 178.xxx.xxx.222
[2015-10-30 12:58:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x4298b30
[2015-10-30 12:58:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 12:58:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 13:02:38 v4 No-IP.com dbg]: dns_handle created 0x42987b0 for 178.xxx.xxx.222
[2015-10-30 13:02:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x42987b0
[2015-10-30 13:02:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 13:02:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror -> retry verify in 240 secs
[2015-10-30 13:06:38 v4 No-IP.com dbg]: dns_handle created 0x400b300 for 178.xxx.xxx.222
[2015-10-30 13:06:38 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x400b300
[2015-10-30 13:06:38 v4 No-IP.com dbg]: verify failed, is 178.xxx.xxx.27, but should be 178.xxx.xxx.222
[2015-10-30 13:06:38 v4 No-IP.com dbg]: ep=0x4294800 restart_verify_set_timer:1488 updated -> offline
[2015-10-30 13:06:38 v4 No-IP.com dbg]: verify failed: DNS reply: noerror.
[2015-10-30 13:06:38 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 13:06:38 v4 No-IP.com dbg]: Retry update in 300 secs.
[2015-10-30 13:11:39 v4 No-IP.com dbg]: ddns_update: offline (178.xxx.xxx.222)
[2015-10-30 13:11:39 v4 No-IP.com dbg]: ep=0x4294800 ddns_update:3232 offline -> checking
[2015-10-30 13:11:39 v4 No-IP.com dbg]: new address
[2015-10-30 13:11:39 v4 No-IP.com dbg]: starting update (new address) [update_v6_addr 0] {178.xxx.xxx.222}
[2015-10-30 13:11:39 v4 No-IP.com dbg]: ep=0x4294800 do_connect:2300 checking -> updating
[2015-10-30 13:11:39 v4 No-IP.com dbg]: ep=0x4294800 ddns_closecb:2396 updating -> updated
[2015-10-30 13:11:39 v4 No-IP.com dbg]: verify handle 70054208 (delay 240)
[2015-10-30 13:15:39 v4 No-IP.com dbg]: dns_handle created 0x400bc40 for 178.xxx.xxx.222
[2015-10-30 13:15:39 v4 No-IP.com dbg]: ddns_verify_complete mit dns->handle 0x400bc40
[2015-10-30 13:15:39 v4 No-IP.com dbg]: ep=0x4294800 ddns_verify_complete:1527 updated -> complete
[2015-10-30 13:15:39 v4 No-IP.com dbg]: verified 178.xxx.xxx.222
[2015-10-30 14:13:34 v4 No-IP.com dbg]: ep=0x4294800 ddns_add_account:3996 offline -> offline
[2015-10-30 14:13:35 dbg]: #### Dual-Stack WAN connection. ####
[2015-10-30 14:13:35 v4 No-IP.com dbg]: ep=0x4294800 reset_account:943 offline -> offline
[2015-10-30 14:13:35 dbg]: v4 new 1 cnt 2
[2015-10-30 14:13:35 dbg]: v6 new 1 cnt 2
[2015-10-30 14:13:35 dbg]: !!! NEW IPv4 CONNECTION !!!
[2015-10-30 14:13:35 v4 No-IP.com dbg]: ddns_update: offline (178.xxx.xxx.222)
[2015-10-30 14:13:35 v4 No-IP.com dbg]: ep=0x4294800 ddns_update:3232 offline -> checking
[2015-10-30 14:13:35 dbg]: !!! NEW IPv6 CONNECTION !!!
[2015-10-30 14:13:35 v4 No-IP.com dbg]: no update needed
[2015-10-30 14:13:35 v4 No-IP.com dbg]: ep=0x4294800 ddns_check_complete:3083 checking -> complete
##### END SECTION dyndns

 

[PeterPawn]

Wie man schon am Eintrag in der ar7.cfg erkennt, fühlt sich der DynDNS-Client der FRITZ!Box im Zusammenhang mit dem "originalen" no-ip.com-Eintrag nur für die Änderung von IPv4-Adressen zuständig (ddnsmode = ddns_v4. Auch im Protokoll ist das deutlich zusehen, nach jeder (relevanten) Uhrzeit steht immer nur "v4".

Irritierend ist es zwar, daß da offenbar das "Durchschlagen" der Änderungen bis zum befragten DNS-Server auch sehr lange braucht, aber eine IPv6-Adresse wird da (seitens des AVM-Clients) gar nicht berücksichtigt.

Hier hilft ggf. ein "Benutzerdefinierter DynDNS-Account", bei der Frage, ob bei no-ip.com dann zwei getrennte Updates erforderlich sind und wie das in einer FRITZ!Box funktioniert, hilft wieder die Suchfunktion für dieses Forum (IPv4- und IPv6-Adresse aktualisieren).

In Abhängigkeit von den Gegebenheiten bei no-ip.com könnte man allerdings auch hingehen und den DynDNS-Eintrag in der FRITZ!Box für no-ip.com so anpassen, daß es dann für beide IP-Adresstypen funktioniert. Wie das konkret aussehen müßte, hängt davon ab, wie ein Update bei no-ip.com ausgeführt werden muß. Eine Änderung des Eintrags in der ar7.cfg ist z.B. mit dem FBEditor und anschließendem Import der geänderten Export-Datei auch bei der 6490 möglich.

 

[disn]

Also 3 Möglichkeiten:
- Vertragsumstellung von Dual auf IPV4
- DNS Provider der beide IP-Adresstypen unterstützt
- FRITZ!Box DNS für no-ip.com so anpassen, daß es für beide IP-Adresstypen funktioniert

Vielen Dank - das bringt mich weiter!