Hikvision DVR connection to BGW320 problem

The last entry is set to 192.168.254.1 when I am guessing it should be 192.168.1.254

I saw that too, but my assumption is that the DVR is creating a private /24 subnet for the cameras to operate on, because higher on the page, there's an IP in the 192.168.1.0/24 space that appears to be this DVR (192.168.1.206).  I suppose I should have asked to confirm that. :-)

The other thing I note on that page is IPv6 addresses.  It may be a good idea to turn off IPv6 on the Gateway and see if that smooths any feathers.

Yes, the ip address on the bottom does “look” like a transposed address but you are right, it is a private NIC that the cameras use to isolate them from the home network. I didnt think about the ipv6 addresses, mainly because I never do anything with them but with them being on the recorder it may be messing them up. They are normally blank but when I had dhcp on the filled in and I can’t find a way to take them out. 
sorry for the delay in responding but I am back to where this system is and still working with it. 

I’m sorry if I am confuing the issue. The BGW210-700 was on an entirely different system that I did a couple of months ago. I mentioned that because I knew the job had ATT fiber and I know that I went into the router to put in the port forwarding and did it successfully. But when I went back on some pictures from that other job I realized that the fiber came into a gateway and then the gateway was connected to the BGW210 which is where I went into to set the port forwarding. Sorry if I left it open to believe this unit was on the system that I am having the problem with. It is strictly just the BGW320-500 with no other router cascaded with it. 

I turned off Ipv6 in the modem, restarted the modem and also restarted the DVR, and had no change in the performance, ie the ddns didn’t send an update and Hik-Connect cannot reach its cloud services. Have tried dns of 192.168.1.254 and 8.8.8.8 and niether make a difference. 

The general page was posted earlier but here is one with the current dns selections as well as the NAT, and email pages. The email is showing the current error when pressing the test button. I am fairly confident in the entries for the email page as they were working when we swapped out to ATT fiber and the new modem that comes with it. (BGW320)

Assuming that this display is directly connected to the DVR (instead connected via internal networking), do you have the ability to PING or TRACERT from that device?  I just wonder if you're able to PING 192.168.1.254 and beyond that to anything on the Internet.

I’m not aware of any way I can ping from the DVR. I didn't thing to bring my computer with me. I could hook the internet to a laptop and do that. It may shed some more light on the problem. I’ll bring it next trip up here but not sure if it will be next weekend or not. All I have accessible is my friends Mac Book but I don't think it even has an ethernet jack on it. Everything on wifi seems to work ok. This is the only thing on ethernet at this point. 
I feel a bit incompetent sometimes. I’m not computer illiterate but all I know about networking is just enough to get by and sometimes thats not enough.  I appreciate all the ideas and hope I can keep enough info coming till we can figure it out. Even on systems where I can’t put the port forwarding into the router (locked out or whatever reason) the Hikvision cloud services always works without issue as long as it has a dns and internal gateway IP address of the router. Just to clarify, everything worked on the other ISP just before we switched. I keep thinking something will click in my head and I’ll see something obvious that I overlooked, but haven’t yet.  

When things don't connect up and work like they're supposed to, trying to figure out why is like solving a jigsaw puzzle, usually with the pieces flipped upside down because you don't have all the diagnostic tools you might want. The thing is saying DNS isn't working, but that could be because IP isn't working at all.  If the DVR had diagnostic tools, that'd be ideal, but yeah, hooking up laptop or something and pinging from it would establish some known working things.

I’ll bring the laptop next time I come up and work on that. No the dvr (or actually in this case NVR) doesn’t have any diagnostics. Just also a little bit additional info….. computer, iphones etc (all connected via wifi) all work fine… its just the video recorder connected to ethernet that has the problem. Also, I think I mentioned it before, but I can get back in to the recorder from remote locations by way of manually setting the external ip address of the modem at the ddns site and going through the port forwading in the gateway/router to get to the recorder and view the cameras, but if, or rather when, the external ip changes, the recorder can’t update the ddns site.  (may or may or may not be info that is helpful)

thanks again for the continued ideas to follow up on. 

But I can get back in to the recorder from remote locations by way of manually setting the external ip address of the modem at the ddns site and going through the port forwading in the gateway/router to get to the recorder and view the cameras, but if, or rather when, the external ip changes, the recorder can’t update the ddns site.  (may or may or may not be info that is helpful)

Thanks for that reminder.  So the network is working at the IP level.  Taking the e-mail error message at its word, your thing says that either it couldn't reach the DNS server or it didn't return an IP for gmail.google.com, which is crazy for Google's DNS not to be returning an answer.  Have you tried swapping the IPs to see if Cloudflare is better; it normally won't go to the secondary unless the primary doesn't answer at all; if it answers "I don't know" then the secondary isn't asked.  Also, retype the gmail.google.com to ensure there are no leading or trailing spaces and that those periods are periods, just in case.

The DDNS sounds like the same DNS resolution problem, but again 8.8.8.8 and 1.1.1.1 are fine DNS servers.  Re-enter those too, for fun.