SRV records

  • Thread starter Thread starter Blake
  • Start date Start date
B

Blake

I apologize that this message is somewhat off-topic. We have a proprietary
system that is running BIND 9.1.3 and I need to populate this server with
the appropriate records for our domain controllers.

If someone could point me to a HOWTO I would greatly appreciate it.

Blake
 
I apologize that this message is somewhat off-topic. We have a
proprietary system that is running BIND 9.1.3 and I need to populate this
server with the appropriate records for our domain controllers.
Click to expand...
If someone could point me to a HOWTO I would greatly appreciate it.
Click to expand...

Did you see this webcast ?

http://support.microsoft.com/default.aspx?scid=kb;en-us;324858

Regards

--

* ObiWan

Microsoft MVP: Windows Server - Networking
http://www.microsoft.com/communities/MVP/MVP.mspx
http://italy.mvps.org

DNS "fail-safe" for Windows clients.
http://www.ntcanuck.com

Newsgroups and forums
news://news.ntcanuck.com
http://forums.ntcanuck.com

408+ XP/2000 tweaks and tips
http://www.ntcanuck.com/tq/Tip_Quarry.htm
 
In
Blake said:
I apologize that this message is somewhat off-topic. We have a
proprietary system that is running BIND 9.1.3 and I need to populate
this server with the appropriate records for our domain controllers.

If someone could point me to a HOWTO I would greatly appreciate it.

Blake
Click to expand...

The webcast link posted by Obiwan is a good one. Here's a some links that
may help as well:

Windows 2003 Interoperability with unix DNS Servers:
http://www.avidware.net/Linux/Windows-2003-linux-dns-server.asp

Configuring Berkeley Internet Name Domain (BIND) to Support AD:
http://www.microsoft.com/technet/itsolutions/migration/linux/mvc/cfgbind.mspx

BIND Your Windows 2000 DNS - from MCP Mag:
http://www.mcpmag.com/features/article.asp?EditorialsID=273


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================
 
I appreciate all the links, guys.

All I need is for the BIND machine to able to point clients to the
appropriate DCs. It is a single application, so I don't need a lot of
functionality. Based on the webcast, I think my best bet is zone delegation
for _udp, _tcp, _msdcs, etc. That way I can keep the data on the Windows
DNS boxes.
 
In
Blake said:
I appreciate all the links, guys.

All I need is for the BIND machine to able to point clients to the
appropriate DCs. It is a single application, so I don't need a lot of
functionality. Based on the webcast, I think my best bet is zone
delegation for _udp, _tcp, _msdcs, etc. That way I can keep the data
on the Windows DNS boxes.
Click to expand...

Blake,

You mean delegation for the AD namespace? E.g. domain.com is your Internet
domain name, and you use ad.domain.com for your AD DNS domain name? If that
is what you mean, yes, that's a good choice. Makes it easier
administrative-wise. You can also choose a private name, such as domain.net,
which of course is not one you would be using on the Internet.

Ace
 
We have been running MS DNS in our production environment for years with no
problems.

Our network people have put a small number of clients on a subnet that can
only get to a single server. That server runs BIND and resolves everything
to itself. The problem is the clients need to be able to log onto the
domain. I would like to simply delegate the subdomains:

_udp.ourdomain.edu
_tcp.ourdomain.edu
_sites.ourdomain.edu
_msdcs.ourdomain.edu

Once these clients jump through a hoop, they go on our production network
and our regular AD integrated DNS on Windows 2000. All I need is a single
domain logon per client, then they get on the regular network. So I need
the absolute minimum on the BIND box so that the clients can log onto the
domain the first time.

Thanks
Blake


"Ace Fekay [MVP]"
 
In
Blake said:
We have been running MS DNS in our production environment for years
with no problems.

Our network people have put a small number of clients on a subnet
that can only get to a single server. That server runs BIND and
resolves everything to itself. The problem is the clients need to be
able to log onto the domain. I would like to simply delegate the
subdomains:
_udp.ourdomain.edu
_tcp.ourdomain.edu
_sites.ourdomain.edu
_msdcs.ourdomain.edu

Once these clients jump through a hoop, they go on our production
network and our regular AD integrated DNS on Windows 2000. All I
need is a single domain logon per client, then they get on the
regular network. So I need the absolute minimum on the BIND box so
that the clients can log onto the domain the first time.

Thanks
Blake
Click to expand...

I see. How about conditional forwarding for "ourdomain.edu" namespace to the
internal Windows DNS server? BIND supports conditional forwarding. Unless of
course the BIND server is hosting the ourdomain.edu namespace, which
forwarding wouldn't work the delegation would be the key.

Also, if the BIND server doesn;t host ourdomain.edu, you can create a
secondary on that server. If it is a public nameserver, I wouldn't put any
internal data on it, delegated or not and would rather opt to place another
separate DNS server (not part of a domain) that has a secondary zone just to
serve your domain clients.

Ace

Ace
 
Back
Top