New answers tagged pfsense
Mappings Names to IP Addresses is the purpose of a DNS server
In addition to mfinni's answer, I would setup Server01 to be a DNS Server for your domain, and point your DHCP server (I'm guessing PFSense) To hand out that address for DNS. Having Windows manage it's own DNS for services such as AD will greatly reduce your headaches in the future.
This is Active Directory 101 - AD clients have to be using a DNS server that has the records for the DNS domain being used by AD. In most scenarios, this/these DNS servers are also domain controllers, but they're not required to be. They simply need to hold the zone that contains the DC-related records. These have SRV records for LDAP and Kerberos, and also ...
Definitely better to use HA w/CARP in that case. That gives you redundancy that you can't get at the hypervisor level, like not going down when doing upgrades.
I had to enable vlan on the wifi part of the hotspot, and disable vlan on the ethernet port. Now it works as it should.
I definitely think CARP is better suited for this task, as when a Virtualization host is going down, pfSense would need to be restarted on another machine first. (I don't know exactly how VMWare FT works, but I think it has some limitations on it's own) What we actually do is, we have 2 virtual pfSense appliances going with CARP, each on a separate ...
Top 50 recent answers are included