I have a client with a 100D that's functioning perfectly, but things
happen and we want to build out some in the box redundancy just in case.
They do a lot with the unit; DHCP, lots of port running in interface
mode to keep their network segmented. B...
According to this thread
https://www.wmlcloud.com/internet-protocols/problem-can-fortigate-automatically-update-dns-records/
.....it doesn't, and explains the problems I'm having. I have a thread
below in which I complain about devices not being able...
Greetings... I have very simple network with my 200D acting as a sole
DNS server (no AD or anything else). I have a very large mix of
proprietary devices on the network that don't work as smoothly as
workstations when it comes to registering themselv...
Greetings, Our faithful 1500D currently fails over to our T1 (phone)
when our cable connection dies, which does occur from time to time.
Since we need 24/7 uptime and we process credit cards we need 24/7 SLA.
I do not need load balancing nor want to ...
Dealing with an odd issue with a customer's 100D (v5.4.1) . Their
network is fairly simple with production and business running on one
interface and guest wifi and things that don't need to to see internal
production on another interface. If anything...
I appreciate the quick response. I know where we are going with the
"Enterprise Feature" argument, but it's a circular debate. I can make
the same point about DHCP on an Enterprise Firewall :) Again, I
appreciate the quick response.
Yeah, I tried all this but I'm not the strongest when it comes to
centralized DNS services, but I need to get this working ASAP. My Forti
handles all my DHCP and DNS, so that's not an issue. The domain name
context i'm working with is 'production.loc...
I unchecked both your answers as unhelpful. (1) I never said I was
connecting to wifi. Why would I connect to my own internal wifi when it
outbounds on my ISP connection that I'm trying to provide redundancy?
(2) I'm sure Companies like Cradlepoint d...
Nevermind - found it. What threw me was the rogue DHCP reservation was
on the Fortigate....so naturally you blame the Fortigate, right?The
problem turned out to be wifi. These guys have Ubiquiti AP's on both
sides of the split networks, and Ubiquiti ...
