Setup SBS 2003 R2 in a domain with a Linux server 1

[bman80]

I'm installing a new SBS 2003 R2 server onto a 6 Windows workstation domain that has a Linux server running DHCP and DNS. (It also runs a stock control app that is required by the workstation users.) I've been advised by the company maintaining the Linux server that enabling SBS to be the DC is okay but point the DNS to the Linux server for DNS resolution and not to turn on DHCP. How do I point the SBS DNS to the Linux server and furthermore still enable the SBS to be the DC?
Thanks

 

[pagy]

As long as the Linux box is running bind 8.2.2 or later then it can support DNS for an active directory environment as that version or later support SRV records. It is recommended that dynamic updates are supported/enabled on the Bind box, it is not essential to have dynamic updates available but if they are'nt then someone will have to create all the dns records for active directory to use.

In your IP address settings on the SBS box you simply set the preferred DNS to the Linux box.

You should probably check with the compnay that support the Linux box that DNS on it can handle SRV records and whether dynamic updates are enabled or not.

You can read more about DNS requirements for AD here;

http://www.microsoft.com/technet/archive/interopmigration/linux/mvc/cfgbind.mspx?mfr=true

Paul
MCSE 2003


If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[LWComputingMVP]

I would be asking the linux people WHY. DNS is a critical component of a Windows and SBS network. While it CAN be configured to run on a Linux system, I would recommend following the design that's best supported - letting the SBS server handle these unless there is a COMPELLING reason for the linux system to do it.

 

[bman80]

Thanks guys. Communication with the Linux box supplier was okay, they vpn'ed into their server and spent 30 mins making adjustments to their box. I don't think they use bind - they wouldn't say - all very hush hush! The bottom line is that I've had to individually set up static IP's for the work stations, have the workstation dns settings point to SBS and append dns suffixes of the local domain to the connection properties.
You may well ask why, but the client has other apps that feed off the Linux box which also requires vpn access. Very convoluted but it all works now!

 

[58sniper]

Why not use DHCP on the SBS box? That would certainly be a far better solution than statically assigning IPs to each workstation. And, that will ensure they get properly registered in DNS, since SBS DHCP will do that automagically.

Pat Richard
Microsoft Exchange MVP
Contributing author The Complete Reference: Microsoft Exchange Server 2007

 

[bman80]

Hi 58sniper, I would love to take dhcp and dns under the control SBS but expediancy and the fact that the Linux supplier states that they need it for their applications to make them work properly has inclined me to let them get on with it. Furthermore the client is aware of many of these shortcomings induced by the Linux supplier so now they are looking at alternatives. Microsoft Dynamics anyone?