How do I cancel desec.io

NextBox
1

I have just bought a new Nextbox and tried to follow the Guided Dynamic DNS instructions using desec. io
I created mydomain.dedyn. io and then couldn’t work out what to do about port forwarding on my BT Smart Hub 2.

I am now unable to get to Nextbox or Nextcloud. When I enter http:// nextbox.local or its local address 192.168.1.71 in a browser it redirects me to http:// mydomain. dedyn. io which after a few seconds changes to 192.168.1.1 and displays my routers home page.

I tried soft and hard resets as starting again would be ok for me but it doesn’t help.

Any ideas? (as new user I put spaces in links as it won’t let me post more than 2 links)

2

Hello,

I think you need to login to https://desec.io/ website and remove the rules that you have created here.

Also check if you did any dynDNS/port forwarding rules in your router and delete those as-well.

3

OK. I tried that. The rules showed A, AAAA and NS entries.
An A record set to my IPv4 address
An AAAA set to my IPv6 address
and NS record set to ns1.desec.io. and ns2.desec.org.

I deleted the A and AAAA records but it won’t let me delete the NS ones

It says “Cannot modify NS records for this domain” which makes sense I think.

Perhaps I need to wait for this to propogate?

There is also a forum at deSEC so I might try posting there as well.

Thanks for suggestions.

4

Accessing my Nextbox again — partial success

I am able to access my Nextbox again.
There are still some problems, but here are some of the things that worked.

1. On my BT Smart Hub 2 router

  • Advanced Settings → Firewall → Port Forwarding

    • I set up rules for ports 80 and 443.

  • Advanced Settings → IP6 → Configuration

    • Set “ULA Enabled” to “YES”.

I realised that when I was typing http://nextbox.local and it redirected to mydomain.dedyn.io,
the problem I hadn’t noticed was that it was actually using https://mydomain.dedyn.io.
Changing this to http instead of https let me into my Nextbox.

I was then able to progress to getting my TLS Certificate,
and then using https started working.

2. In the Nextbox App

  • Under Guided Dynamic DNS:

    • Shows “Successfully Resolved” for both IPv4 and IPv6.

    • This DNS configuration is active for the domain: mydomain.dedyn.io.

  • Under Remote Access:
    There is still one problem.

    • Successfully resolved: mydomain.dedyn.io to <my ip>.

    • Successfully tested reachability for <my ip>, mydomain.dedyn.io, and found a Nextcloud instance.

    • Successfully resolved: mydomain.dedyn.io to <IPv6 ip>.

    • Failed reachability for [IPv6 ip].

Please see the following topics at
docs.nitrokey.com/nextbox
to troubleshoot: DNS-Rebind Protection, (Dynamic) DNS.

I am still looking into DNS-Rebind Protection. And apologies for the overuse of Markdown. I let AI have a go ! I think it looks worse than plain text.

5

This is good news.

For the IPV6 problems I recommend looking this:

If you are not able to fix this you should ignore it since IPV4 is sufficient for remote access.