Windows cannot find the network path when joining to the dom
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Windows cannot find the network path when joining to the dom
Goto page Previous  1, 2
 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS
Author Message
Kevin D. Goodknecht Sr. [
Guest





Posted: Wed Jan 26, 2005 6:47 am    Post subject: Re: Windows cannot find the network path when joining to the Reply with quote

In news:uLY$$evAFHA.3528@tk2msftngp13.phx.gbl,
Keith Ng <ngkeith@triumf.ca> commented
Then Kevin replied below:
Quote:
Kevin, I really apprciate for your help.

Our DNS is running on BIND and our AD domain is
windows.mycompany.com. As I mentioned perviously, our DNS
admin has just created a subdomain called
windows.mycompany.com and registered the DC under this
subdomain.

I can't really delegate this subdomain to the DC as we
have almost 900 nodes in the network and they are mixed
with Windows and Linux machines. It would be very
difficult to assign the DNS IP to the Windows clients
through DHCP as our DHCP server does not distribute IP
address to PCs based on what OSs they are running. And
the other things is I am not the DNS/DHCP admin and I
don't have control of those servers

You would not have to add the DCs DNS to any client if you delegate the name
windows in the BIND DNS to the DC.
The DC would hold a zone named windows.mycompany.com any client looking for
windows.mycompany.com in the BIND DNS would cause the BIND DNS to get the
answer from the DC. It is really very simple and would not cause the DC to
work much harder because BIND will cache the requested DCs records for the
TTL value of the record. It would also free up the BIND admin from having to
maintain the AD records. BIND will do that with its caching.

All he really need to do is add this to the mycompany.com zone file.

; delegate windows.mycompany.com to Windows 2000 DNS server

windows.mycompany.com. IN NS dc1.windows.mycompany.com.
'dc1.windows.mycompany.com. IN A <dcipaddress>

Thats's it the DC is now handling DNS registration but BIND will handle
resolution for windows.mycompany.com through the delegation. The clients
would not even contact the Windows DNS, BIND will. Even if the client were
registering in the the Windows DNS BIND will send the registration on behalf
of the client.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB