Dnsmasq Active Directory Srv Records In Dns

[Dnsmasq-discuss] OS X hosted dnsmasq for AD SRV records [Dnsmasq-discuss] OS X hosted dnsmasq for AD SRV records Peet McKinney Mon Nov 22 21:35:55 GMT 2010 • Previous message: • Next message: • Messages sorted by: All, dnsmasq has been an absolute life-saver in my environment. OS X Directory services isn't playing nicely with GC discovery in my Active Directory environment, so I've brought up a couple instances of dnsmasq to help force it into being a good citizen. I've compiled dnsmasq on 10.6.4 from the 2.55 source and configured it to respond correctly to my SRV lookups. I've also installed the launchd plist. (Though I have to wonder the value of having that plist configured with '--log-queries' and '--log-facility=/var/log/dnsmasq.log' by default.

KMS Auto Discovery. The WolfTech Active Directory is configured so that your workstations will automatically locate the KMS service. This method is called “auto discovery”. Client computers use DNS SRV records to automatically locate the KMS service. The SRV records are already in place for computers joined to the WolfTech active direcotry.

Admittedly, I'm an idiot for not checking and ending up with a 24GB dnsmasq.log, but considering there's not a default rotation for the log it seems a bit of an odd choice for a default launchd setup.) Since cleaning up my silly logging issues, I'm left with what my simply be a standard behavior of dnsmasq, but one that I'd really like to find a way around. When I query SRV records that are in my dnsmasq config, they are *always* returned in the same order with no randomization. Please see below: jodr:~ jadmin$ host -t SRV _gc._tcp.umontana.edu _gc._tcp.umontana.edu has SRV record 0 100 3268 dbsaddc3.dbsad.umt.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 gsdc1.gs.umt.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 gsdc0.gs.umt.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 msodc13.umt.edu.

The particular degree this agreement we can locate certain regarding the old christ in a gospels is debated. Where it sufficient time for a unique text to make do duplicating challenges and moreover talk alters, inclusions, to omissions. State of the art testament content criticism is closely reliant in codices about 4th and therefore 5th centuries, too the most seasoned manuserscript pieces which might be preserved for coming from your are 2nd century.

_gc._tcp.umontana.edu has SRV record 0 100 3268 mumtdc5.umt.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 mumtdc2.umt.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 mitosdc2.missoula.campus. _gc._tcp.umontana.edu has SRV record 0 100 3268 mitosdc0.missoula.campus. _gc._tcp.umontana.edu has SRV record 0 100 3268 umontanadc2.umontana.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 umontanadc1.umontana.edu.

When I lookup against the AD DNS servers they are randomized. Of course the results below include servers that I don't want to see returned as results, but you can see that two lookups in quick succession provided completely different answers: j010-peet:~ jadmin$ host -t SRV _gc._tcp.umontana.edu;; Truncated, retrying in TCP mode. _gc._tcp.umontana.edu has SRV record 0 100 3268 umontanadc2.umontana.edu. _gc._tcp.umontana.edu has SRV record 0 100 3268 mumtdcctw.umt.edu.

_gc._tcp.umontana.edu has SRV record 0 100 3268 mitosdc2.missoula.campus. _gc._tcp.umontana.edu has SRV record 0 100 3268 mitosdc0.missoula.campus. _gc._tcp.umontana.edu has SRV record 0 100 3268 gsdc1.gs.umt.edu.