At 11:42 AM 9/9/98 -0400, Brett Lorenzen wrote:
>Ivan Sergio Borgonovo wrote:
>
>> > NT is very pathetic with DNS. We tried a few of the free MS-supplied
>> > options, which didn't work for squat, and a couple of rumoured freeware
>> > things that never even got off the ground.
>>
>> Well my DNS DB will contain from 4 to 10 machines...
>
>yeah, that's not much busy work at all. I would have to ask, why
>bother? Don't you have someone upstream that can do this for you and
>just assign you IP numbers?
This is MUCH less work than trying to get MS-DNS, and Wins to
play nicely. You are also better off with 4 systems to use
assigned IP numbers instead of trying to implement a DHCP server
(which is available with Red Hat Linux 5.1).
>> Have you heard about BIND? Can you tell me what are the free
>> apps you've found?
>
>Yes. Problem with BIND is that it was developed for UNIX, which means
>NT has a half-assed implementation.
>
>Free apps are from MS--their DNS packages and demos came with the NT
>server package we bought--will ask tech guys to dig those files out
>again when i see them.
>
The only good use for MS's DNS server is to edit the control
files. Then you export the files to your UNIX DNS server and
restart DNS services there.
>> > In the ended we paid the bucks for MetaIP from Checkpoint (who also make
>>
>> TOO HUGE i really want a small thing...
>
>Well, DNS is either on or off. How many domains you run is kind of
>irrelevant after that.
Depending on the traffic, your network overhead is also pretty low.
>> Do you know if I'll use LMHOST will resolve some of my problems?
>
>Nope.
LMHOST (Lan Manager Host) is analagous to /etc/hosts on UNIX. It
is mearly a static list of netbios names.
>> Do you know how I can run the WINS service?
>
>Yeah--MS tech support site has docs on this. This is, though, the core
>of what we found to be the source of the DNS problems we had.
The thing is WINS is for NetBIOS resolution, not Internet IP
resolution. If you run WINS you will still need to run a DNS server.
>> Do you know how they work?
>
>In theory, yes. In application within an MS system, no. That's why I
>hang around with tech guys ;)
WINS is basically a "DNS for Net BIOS". It should be used if you
are doing a network without TCP/IP. If you are running TCP/IP as
your primary protocol, then you should run DNS.
Get the Cricket Book for DNS. It is MEGA helpful.
>Check the "management press" sites for WINS info with searches
>(mecklermedia.com, internet.com, etc.) There are numerous articles on
>the pros and cons and problems of NT DNS in them that can explain a hell
>of a lot more about it than I can. As I noted: once I confirmed the
>fact that the process didn't work well out of the box (as MS said it
>should), and practice confirmed what the trade press had said, I had
>someone throw money at it :P (well, actually it was more like "throw
>money at this or I buy another Linux box and do it that way" ;) ).
Matt Soffen
==============================================
Boss - "My boss says we need some eunuch programmers."
Dilbert - "I think he means UNIX and I already know UNIX."
Boss - "Well, if the company nurse comes by, tell her I said
never mind."
- Dilbert -
==============================================
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
