RE: Can FreeBSD be a PDC for microsoft machines?

2004-02-01 Thread Richard van Vliet 
 

 -Oorspronkelijk bericht-
 Van: L.I. Benjamín Guerrero Del Angel [mailto:[EMAIL PROTECTED] 
 Verzonden: zondag 1 februari 2004 5:03
 Aan: [EMAIL PROTECTED]
 Onderwerp: Can FreeBSD be a PDC for microsoft machines?
 
 I am a new user about FreeBSD, I have installed two computers 
 with this OS and I think is good.
 
 I want to know if FreeBSD can operate as a Primary Domain 
 Controller in a Network, because where I live everybody has 
 microsoft computers so I want to use FreeBSD as server 
 instead Windows NT o 2000.

You can use samba for PDC (NT 4.0 domain structure) or Active Directory
Memberserver 
Not yet as a Domain Controler.

 If you know how to do that, plaese let me know. Or tell me 
 what to read about.

You have to use FreeBSd 5.X because (Pleasy people correct me if i'm wrong)
for domain control you need winbind witch in turn needs NSS and that is not 
available in FreeBSD 4.x

The only problem 5.X is still technology relase so make your own dission 
in using 5.X

You can read about it at www.samba.org
Read the release notes of the version you are using for its features

 Thank you!

No problem

Regards Ricard.

 
 Benjamin Guerrero
 Reynosa, Tamaulipas Mexico
 ___
 [EMAIL PROTECTED] mailing list 
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 [EMAIL PROTECTED]
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: BIND 8.3 going insane on FreeBSD 4.9

2004-01-29 Thread Richard van Vliet 
Be sure that jou server can recieve query's directly from the rootservers,
it happend at my place when the firewall blocked these rootname server
query's.

I had the same problem logs filling up in minutes...

Configure your private BIND server to use forwarders only, it wil then query
itself for its one zones and the forwarder for any other.

Regards Richard. 

 -Oorspronkelijk bericht-
 Van: Mark Edwards [mailto:[EMAIL PROTECTED] 
 Verzonden: vrijdag 30 januari 2004 2:17
 Aan: [EMAIL PROTECTED]
 Onderwerp: BIND 8.3 going insane on FreeBSD 4.9
 
 So, I've seen this twice now.  BIND completely flips its lid 
 and utterly destroys the server.  Logs say:
 
 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs 
 found for root NS (K.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs 
 found for root NS (D.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs 
 found for root NS (A.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs 
 found for root NS (H.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs 
 found for root NS (C.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs 
 found for root NS (G.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs 
 found for root NS (F.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs 
 found for root NS (B.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs 
 found for root NS (J.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs 
 found for root NS (K.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs 
 found for root NS (M.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs 
 found for root NS (I.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs 
 found for root NS (L.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs 
 found for root NS (D.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs 
 found for root NS (A.ROOT-SERVERS.NET)
 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs 
 found for root NS (H.ROOT-SERVERS.NET)
 
 
 My root hints are up to date, and I've seen this both using 
 forwarders and not.
 
 I've read that this is some incompatibility between BIND 8.3 
 and other servers.  Is the only solution to this problem to 
 run BIND 9?
 
 I really have to make sure this doesn't happen again, because 
 it has catastrophic effects on the server.  Thanks for any help!
 
 ___
 [EMAIL PROTECTED] mailing list 
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 [EMAIL PROTECTED]
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]