| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 6040.1 | Yes, you can. | TPOVC::SIMONLEE | | Mon May 26 1997 09:51 | 4 |
|
Hello, I am sure you can do that. In DNS manager, there is a pop-up
window in which you can fill in the names of forwarders and there is a
check-box that you can check to make the server slave.
|
| 6040.2 | thank you for this info | BACHUS::ROELANDTS | Wa d'es ma da ve ne stuut | Tue May 27 1997 00:23 | 8 |
|
Thank you very much for this answer, we will install it and will try
it.
Rgds,
Guy
|
| 6040.3 | | TECO::tecotoo.mro.dec.com::mayer | Danny Mayer | Tue May 27 1997 07:57 | 5 |
| The NT 4.0 (and previous versions of NT) DNS Server is known to have
problems. You may want to go with a commercial DNS, like MetaInfo's DNS
which is used for the AltaVista NT Firewall.
Danny
|
| 6040.4 | | BIGUN::nessus.cao.dec.com::Mayne | Meanwhile, back on Earth... | Tue May 27 1997 20:20 | 8 |
| > The NT 4.0 (and previous versions of NT) DNS Server is known to have
> problems.
I suppose the fact that versions previous to 4.0 didn't have a DNS server could
be counted as a problem. 8-)
PJDM
|
| 6040.5 | | TECO::tecotoo.mro.dec.com::mayer | Danny Mayer | Wed May 28 1997 07:00 | 10 |
| >> The NT 4.0 (and previous versions of NT) DNS Server is known to have
>> problems.
>
> I suppose the fact that versions previous to 4.0 didn't have a DNS server could
> be counted as a problem. 8-)
>
The DNS Server was in the Resource Kit in NT 3.5 and 3.51 and was known
for its lack of reliability and usability.
Danny
|
| 6040.6 | Is there another DNS to recommend? | HBAHBA::REED | John Reed @CBO = Network Services | Mon Jun 02 1997 08:08 | 27 |
| Hello.
I have this arrangement (Two NT Alphas) one is the firewall running
Altavista Firewall (not 97) and the next is running the Web Server and
DNS for the internal site. (10.x.y.z) with a forwarding address sent to
the Firewall.
NT is 4.0 on both machines, and I am running the DNS that came from
Microsoft on the internal DNS Alpha.
But the DNS drops out, and must be rebooted every seven or eight days.
It says that it is working, the process shows up in the NT Diagnostics,
the DNS manager screen shows the database correctly. But no machine
can ping by DNS name. I can ping by address (from the firewall) but
not by name, internally or externally. If I reboot the alpha with
the DNS running on it, it will work again for a week.
Any hints is this is the "known problem" with the microsft NT 4.0 DNS
server software ? Or do I have a different issue here. I have sold
this same config to some other customers, so I want to know if I should
change vendors for DNS code, before I install them.
Thanks for any help.
John Reed
Network Services
|
| 6040.7 | | TECO::tecotoo.mro.dec.com::mayer | Danny Mayer | Mon Jun 02 1997 08:58 | 10 |
| > NT is 4.0 on both machines, and I am running the DNS that came from
> Microsoft on the internal DNS Alpha.
Dump Microsoft's DNS. It's known to have problems. Use either MetaInfo's
DNS (which is what the firewall machines run) or the free Bind for NT. I don't
have a pointer for the Free DNS, but it was ported by Larry Kahn (though I
think that Paul Vixie may be doing it now).
Danny
|