Setting up Cloudron again as Server Crashed - queryNs ESERVFAIL

[skeats]

Hello,

I had to reinstall Cloudron an another server as the server it was on crashed. Taking my backup is not working and I am using the same IP (as server is hosted internally) so I can make sure that I do have to setup new Port Forwarding rules. It is giving me the following Error:

I did do the host -t NS (hostname) and it came back with NS servers on Godaddy and when I did a host -t NS (hostname) 127.0.0.1 I was getting no response at all and nothing was found. I did this on the server side. I am confused as to why it is doing this and I need to get my server backup.

[joseph]

I replied from support@ but can you check if unbound is running?

systemctl status unbound and also try systemctl restart unbound . If unbound is running, you need to investigate further why host domain.com 127.0.0.1 is not working. Maybe you have to configure unbound to forward all queries? Is there some firewall blocking outbound DNS requests? See https://docs.cloudron.io/networking/#dns

[skeats]

Hi @joseph I checked this and unbound was running and active. Now I did check and host domain.com 127.0.0.1 and that failed. I followed the link in the document and created the customer.conf file and added in what it required and restarted the unbound service and did a check again to host domain.com 127.0.0.150 and that worked, but the problem is, the URL is pointing to the wrong IP and I did not set that up. I need that changed to my custom IP I use for this service, which I know I entered when I tried to get this working. How do I change that when GoDaddy is setup fine and my firewall has all the rules forwarding that customer IP to the internal IP of the Cloudron server

[skeats]

never mind, I fixed the issue with the IP. I went into GoDaddy and noticed the IP was different, so I changed it back, restarted unbound service and now my dashboard is loading with my domain. Now to restoring all of the apps with my backups.