There will be at minimum this HOWTO that works around the specialized issues by teaching dnsmasq the required SRV records personally, but also after that you wont possess dynamic DNS updates the method Samba needs them and it can be even more of a crack definitely unsupported by the Samba team than a viable solution.Running dnsmasq is definitely feasible not so very much as an choice working on the Samba web host itself, but, at least in my idea of SOHO networking, its pre-destined for embedded devices like as gain access to points and routers and accordingly the default DNS forwarder in OpenWrt.Having DNS quality depend on a highér-level DNS program supplied by Samba wouId contradict that concept.
Dnsmasq Active Directory Srv Records In Dns Crack Definitely UnsupportedDnsmasq Active Directory Srv Records In Dns Software I DoAside from the reality that Sambas DNS machine would need support for every individual feature present DNS web servers (like as dnsmasq) already possess or hole be utilized, a software I do not really miss especially very much (believe zone documents). Obviously I cant accomplish the preferred solitude of a simple network services like as DNS and a successful service such as Samba with a single DNS area, as there will be no such issue as zone sharing. So Sick need two DNS areas: mysite.foo.club and either ad.mysite.foo.pub or mysite.advertisement.foo.club. The other selection would become more suitable if we were to significantly use Active Directory features like as forests and sites but also indicate that there would become a parallel woodland of standard DNS areas and the need to possess a foo.pub DNS machine that facilitates delegations. As Samba 4 currently supports operating a one Energetic Directory domain control only in any case, Ill move with the previous: DNS zone Managed by Operating on mysite.foo.pub dnsmasq OpenWrt-based access pointrouter ad.mysite.foo.bar Samba Real server Today I perform, of program, have just one DHCP provider at my site. Officially it could supply several DNS hosts but you wouldnt wish that since you cant control your customers resolvers conduct via DHCP (web browser. Its perfectly good to have got both baz.mysite.foo.club and baz.advertisement.mysite.foo.bar stage at 192.168.0.1 and have reverse search of the IP tackle resolve to baz.mysite.foo.pub, as longer as you configure Kerberos customer configuration accordingly (the rdns fake option defined at the end of my sssd-ad construction blog post). This way, if the Samba server goes lower, only the advertisement.mysite.foo.bar area will end up being affected, not mysite.foo.pub as a whole. Neat:) Submitted in dnsmasq, Samba, Systems administration by Pieter Hollants Follow responses via the RSS Feed Keep a comment Trackback Website Keep Your Remark You must become logged in to article a comment. All privileges reserved. Legal updates Privacy plan.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |