From: Benjamin Huntsman <BHuntsman@mail2.cu-portland.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dns SRV records
Date: Thu, 28 Apr 2011 23:49:10 +0000 [thread overview]
Message-ID: <5782C16A7C920E469B74E11B5608B8E708A30DFE@Kriegler.ntdom.cupdx> (raw)
In-Reply-To: <BANLkTinBzxkinZC727hrPMC=Fp37c8RSYg@mail.gmail.com>
>Investigating the possibility of replacing the MS DNS on Plan9 DNS,not found in the man ndb mention of records of type SRV.
>It is necessary to support Microsoft Active Directory. Maybe I missed something?
>http://en.wikipedia.org/wiki/SRV_record
I got AD to work with Plan 9 DNS just last year. It didn't work very well, and I had problems with the DNS
service dying from time to time and I'd have to go restart it. Much as I'd preferred to have stayed on Plan 9 DNS,
I switched to BIND 9 on OpenBSD and have had far fewer problems. But anyway, here's the Active Directory support
portion of my /ndb/local. This supported a domain whose domain was "testad". Like I said, it works, but not as
seamlessly as MS DNS or BIND 9 with dynamic updates enabled... (pardon the excessive comments)
#################################################
#
# Active Directory support
# See http://technet.microsoft.com/en-us/library/dd316373.aspx
#
#################################################
#
# Domain Controllers:
#
ip=10.0.0.20 sys=kfdc1 dom=kfdc1.testad.test.local
ether=
ip=10.0.0.21 sys=kfdc2 dom=kfdc2.testad.test.local
ether=005056b36086
#
# requisite CNAME aliases
#
cname=kfdc2.testad.test.local
dom=testad.test.local
cname=kfdc2.testad.test.local
dom=8df1f9af-8c89-4263-9c30-a40ad5ac728f._msdcs.testad.test.local
#
# SRV records, etc
#
dom=testad.test.local soa=
refresh=3600 ttl=3600
ns=ns2.test.local
#ns=ns1.test.local
dnsdomain=testad.test.local
dom=_ldap._tcp.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_kerberos._tcp.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=88
srv=kfcd2.testad.test.local pri=1 weight=1 port=88
dom=_kpasswd._udp.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=464
srv=kfdc2.testad.test.local pri=1 weight=1 port=464
dom=_kpasswd._tcp.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=464
srv=kfdc2.testad.test.local pri=1 weight=1 port=464
dom=_ldap._tcp.dc._msdcs.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_ldap._tcp.gc._msdcs.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
# only one PDC
dom=_ldap._tcp.pdc._msdcs.testad.test.local soa=
srv=kfdc2.testad.test.local pri=0 weight=0 port=389
dom=_ldap._tcp.KlamathFalls._sites.gc._msdcs.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_kerberos._tcp.dc._msdcs.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=88
srv=kfdc2.testad.test.local pri=1 weight=1 port=88
dom=gc._msdcs.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=3268
srv=kfdc2.testad.test.local pri=1 weight=1 port=3268
dom=_gc._tcp.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=3268
srv=kfdc2.testad.test.local pri=1 weight=1 port=3268
dom=_ldap._tcp.e3514235-4b06-11d1-ab04-00c04fc2dcd2.domains._msdcs.testad.test.local
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
# Key Management Service
dom=_VLMCS._tcp.testad.test.local soa=
srv=kfdc2.testad.test.local pri=0 weight=0 port=1688
dom=_ldap._tcp.KlamathFalls._sites.domaindnszones.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_ldap._tcp.domaindnszones.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_ldap._tcp.KlamathFalls._sites.forestdnszones.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
dom=_ldap._tcp.forestdnszones.testad.test.local soa=
srv=kfdc1.testad.test.local pri=0 weight=0 port=389
srv=kfdc2.testad.test.local pri=1 weight=1 port=389
#################################################
#
# End Active Directory Support
#
#################################################
next prev parent reply other threads:[~2011-04-28 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 8:22 Sergey Kornilovich
2011-04-28 9:38 ` Sergey Zhilkin
2011-04-28 17:18 ` Steve Simon
2011-04-28 18:39 ` geoff
2011-05-03 8:30 ` Sergey Kornilovich
2011-05-04 11:41 ` Pavel Klinkovsky
[not found] ` <2ef2821c-eb63-427a-95c5-0e36a6c73b28@j26g2000yqa.googlegroups.co>
2011-05-04 13:10 ` erik quanstrom
2011-05-05 9:42 ` Sergey Kornilovich
2011-05-05 12:45 ` erik quanstrom
2011-05-05 15:35 ` Sergey Kornilovich
2011-05-05 15:44 ` erik quanstrom
2011-04-28 23:49 ` Benjamin Huntsman [this message]
2011-04-29 7:04 ` Sergey Zhilkin
2011-04-29 13:14 ` Sergey Kornilovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5782C16A7C920E469B74E11B5608B8E708A30DFE@Kriegler.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).