Dnsmasq Active Directory Srv Records In Dns
Working alongside my EdgeRouter-X in the core of my network is a Synology DS218+ NAS as my Active Directory server, among other roles. Active Directory works its magic through DNS. Without appropriate DNS records setup, clients can’t find the domain controller. This can be used for Split DNS, or making undesirable domains (e.g. Myspace.com) resolve to a non-existent IP address. On pfSense 2.1 and later, Host Overrides work for both IPv4 and IPv6 addresses. On pfSense 2.2, The DNS Forwarder is not active by default. It has been replaced by Unbound as a DNS Resolver. It may still be used, and is still active on upgraded configurations. To use the DNS Forwarder (dnsmasq) on 2.2, first disable Unbound and then enable the DNS Forwarder.
Hi Everyone, First off, love Untangle! Use it at home and work! Download game ps 1 metal slug x pc portable dell. At work, I manage a hybrid Windows/Linux/Mobile network of 75 or so network devices that are protected by an Untangle box. We have a fairly hefty server running Ubuntu linux that hosts a bunch of VMs - one of which is our Active Directory domain controller. We have a hot spare backup server that provides fault tolerance in case our primary server goes down. This setup works well since we don't have to dedicate a box to being a domain controller - which for our small network would be a waste of power, noise & money and be one more piece of equipment to maintain and fail. For reasons known only to Microsoft, AD seems to require SRV records to be able to do even basic functionality - like join a domain, search the directory, etc.
Not having SRV records in Untangle's DNS hasn't been a problem in the last 2 years or so; I'm guessing something was changed via Windows Update recently because the two machines I tried to join to the domain this week failed for the same reason - no SRV record. Here are my options as I see it: 1.
Use Microsoft's DNS server and DHCP servers. I can't see how this would work in my environment - or any small environment like mine that doesn't have a rack full of servers. Everything on my network is DHCP'ed - even my VM host is DHCP'ed (static lease). The bottom line is, I'd have to reconfigure my whole network and even after I did so, this would create unnecessary dependencies among devices (such as our office printer and the AD VM, mobile phones and the AD VM, the VM host wouldn't even be able to resolve a host name without one of its VMs running). If I need to bring down the VM host for maintenance, it would be nice to be able to access the internet as well in case I need to look something up. In summary, this option just sounds like an overall bad idea.
Use Microsoft's DNS server and Untangle's DHCP server. I'd have to come up with a way to sync the DHCP'ed DNS entries to Microsoft's DNS server, which sounds like a nightmare. Even if it could be done, same dependency issues as #1. Abandon Untangle's DNS server and install BIND on the VM host.
I'd have to figure out a way to get the DHCP'ed DNS entries in there. Continue to use Untangle's DNS and DHCP servers and find a way to appease Active Directory by adding SRV record(s) in Untangle's DNS server. This is my preferred solution since it sounds like it might be possible after reading the dnsmasq docs. Has anyone done this?
Find a way to reconfigure AD to remove this dependency on SRV records. Has anyone had to solve this problem? Is there anything I haven't thought of? The SRV records are how AD clients find AD servers, and they are created using a dynamic DNS call to an Active Directory integrated DNS zone by the AD server as it comes online. In short, if you want to support AD, you've ALWAYS needed to use MSDNS to do so. This is not new.