Rsync fail to resolve host after change to static ip

Hello again!

I recently discovered that my server wasn't on a static IP address. After fixing that mistake, rsync now gives me an ssh error saying that it's failing to resolve the host and the receiver closed off the connection. I know the host site works, I pinged it but also Filezilla connects just fine to it. I'm not sure what's going on or why rsync is failing here. I use an SSH certificate to communicate with the host, and that certificate was made when the server had a different IP address. Could that be the issue?

The Error:

ssh: Could not resolve hostname brontes.feralhosting.com: Name or service not known

rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]

rsync error: unexplained error (code 255) at io.c(235) [Receiver=3.1.3]

ERROR: The synchronisation failed.

Zitat von gderf

You might try disabling the use of DNS in the sshd configuration. Add this line to the Extra Options on the OMV | Services | SSH page:

Code

UseDNS no

Rsync still returns the same error, which feels weird because doesn't this command tell it to not care about host name?

After a little bit of poking around, I think I've set up the static IP wrong (?!). How, I don't really know. It should be dead simple but could I have someone look over this for me?

Method: Static
Address: 192.168.0.100
Netmask: 255.255.255.0
Gateway: 192.168.0.1 (the router IP)

I think so? Currently I have a rented router (I know, I know, the new one is in the mail), but there's only one subnet mask field and it has 255.255.255.0 entered into it.

I've also made sure the router reserves the NAS address as well.

Yeah. I set my DNS to 8.8.8.8 via the web gui.