Hi, I have set up the dynamic DNS with gnudip.datasystems24.net and a domain at freedombox.rocks. I thought everything was working fine (no errors) but I couldn't obtain a let's encrypt certificate. It kept timing out.
ifconfig on the freedombox says: ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 75.213.125.194 netmask 255.255.255.255 destination 66.174.121.64 ppp txqueuelen 3 (Point-to-Point Protocol) RX packets 297762 bytes 283984021 (270.8 MiB) RX errors 151 dropped 0 overruns 0 frame 0 TX packets 273501 bytes 31050182 (29.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 But: nslookup <domain>.freedombox.rocks Server: 192.168.200.27 # internal address of freedombox Address: 192.168.200.27#53 Non-authoritative answer: Name: <domain>.freedombox.rocks Address: 75.213.230.174 Obviously 75.213.230.174 is not 75.213.125.194. No wonder the certificate creation is timing out. I have been watching the status of the dynamic DNS client (via the plinth interface) and it says: DNS record is up to date (Sun Oct 29 19:35:05 EDT 2017) DNS record is up to date (Sun Oct 29 19:40:05 EDT 2017) DNS record is up to date (Sun Oct 29 19:45:04 EDT 2017) ... But I keep getting the same 75.213.230.174 returned by nslookup. In all this time the IP of ppp0 hasn't changed. Traceroute returns this: traceroute <domain>.freedombox.rocks traceroute to <domain>.freedombox.rocks (75.213.230.174), 30 hops max, 60 byte packets 1 <internal freedombox name >(192.168.200.27) 0.601 ms 0.465 ms 0.448 ms 2 66.174.121.64 (66.174.121.64) 3362.013 ms 3361.992 ms 3361.938 ms 3 66.174.19.196 (66.174.19.196) 3362.821 ms 3362.713 ms 3362.658 ms 4 69.83.15.242 (69.83.15.242) 3377.494 ms 3378.284 ms 3378.201 ms 5 69.83.15.97 (69.83.15.97) 3380.092 ms 3379.013 ms 3378.990 ms 6 69.83.15.226 (69.83.15.226) 3380.889 ms 3379.553 ms 3400.791 ms 7 69.83.15.228 (69.83.15.228) 3400.747 ms 3114.389 ms 3130.753 ms 8 69.83.15.101 (69.83.15.101) 3131.903 ms 2731.327 ms 2731.212 ms 9 69.83.15.240 (69.83.15.240) 2731.097 ms 2748.558 ms 2748.509 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * whois 69.83.15.240 # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/whois_tou.html # # If you see inaccuracies in the results, please report at # https://www.arin.net/public/whoisinaccuracy/index.xhtml # # # The following results may also be obtained via: # https://whois.arin.net/rest/nets;q=69.83.15.240?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2 # NetRange: 69.82.0.0 - 69.83.255.255 CIDR: 69.82.0.0/15 NetName: WIRELESSDATANETWORK NetHandle: NET-69-82-0-0-1 Parent: NET69 (NET-69-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Cellco Partnership DBA Verizon Wireless (CLLC) RegDate: 2003-10-09 Updated: 2012-03-02 Ref: https://whois.arin.net/rest/net/NET-69-82-0-0-1 OrgName: Cellco Partnership DBA Verizon Wireless OrgId: CLLC Address: 180 Washington Valley Road City: Bedminster StateProv: NJ PostalCode: 07039 Country: US RegDate: 2001-10-01 Updated: 2017-10-12 Ref: https://whois.arin.net/rest/org/CLLC OrgTechHandle: NDBM-ARIN OrgTechName: NDBM OrgTechPhone: +1-908-306-7000 OrgTechEmail: vzwndbmipcont...@verizonwireless.com OrgTechRef: https://whois.arin.net/rest/poc/NDBM-ARIN OrgAbuseHandle: ABUSE716-ARIN OrgAbuseName: Abuse OrgAbusePhone: +1-908-306-7000 OrgAbuseEmail: ab...@verizonwireless.com OrgAbuseRef: https://whois.arin.net/rest/poc/ABUSE716-ARIN # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/whois_tou.html # # If you see inaccuracies in the results, please report at # https://www.arin.net/public/whoisinaccuracy/index.xhtml # Has anyone else encountered this issue? It certainly looks like the dynamic DNS server is not returning the right IP. Is there anything I can do to figure this thing out? Any suggestions to try to find where the problem is? I wouldn't put it past verizon to mangle the IP address so that nothing can reach me from the outside. The whois data seems to point the finger at verizon. Is this a hopelsss situation? Thanks! Augustine _______________________________________________ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss