T.R | Title | User | Personal Name | Date | Lines |
---|
543.1 | nevermind | NEASSG::MARTINELLO | Don't Panic | Fri May 02 1997 10:24 | 11 |
| Hi,
Found our Netscape problem it seems the systems running Netscape are
using DHCP (no name registration in the DNS server)and our FTP server
will not respond to a system that it can not resolve its name. This is
a wonderful feature since most of my customers are using or are moving
to DHCP.
Regards,
joe martinello
|
543.2 | A problem easily solved... | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Fri May 02 1997 11:13 | 15 |
| RE: .1
> Found our Netscape problem it seems the systems running Netscape are
> using DHCP (no name registration in the DNS server)and our FTP server
> will not respond to a system that it can not resolve its name.
Go flog your system administrator(s). Just laziness or ignorance on their
part. There's absolutely no reason that all the IP addresses in the DHCP
address pool shouldn't have DNS registrations to match! Granted the names
will be generic, e.g. dhcp1737.lkg.dec.com, but who cares?
Regards,
Dave
|
543.3 | Don't blame the system admins... | twick.nio.dec.com::PETTENGILL | mulp | Thu May 08 1997 00:14 | 12 |
| You have to flog the name server managers, who have enough problems as it is.
There are no tools that automate managing DNS servers AND that support all the
wierdness that you need to do with DNS to sort of simulate a modern transport.
Even the LAT architecture and at least the VMS LAT implementation handle
path failover, and LAT has been pretty much abandoned for at least 5 years.
Given the wide use of dialup lines, wireless, and dynamic address assignment,
"authenticating" by checking for a valid back and forward translation is
rather stupid. And expensive. DEC appears to have abandoned it for allowing
access to the web firewall passthru.
|
543.4 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Thu May 08 1997 09:40 | 32 |
| RE: .3
> There are no tools that automate managing DNS servers...
But there is ongoing work in the ITEF around dynamic DNS updates, and how to
tie that in with DHCP.
> ...AND that support all the wierdness that you need to do with DNS to sort
> of simulate a modern transport.
What _are_ you babbling about? DNS simulating a transport? Huh?
> Even the LAT architecture and at least the VMS LAT implementation handle
> path failover, and LAT has been pretty much abandoned for at least 5 years.
Yea, and your point is?
> ..."authenticating" by checking for a valid back and forward translation is
> rather stupid.
Perhaps. But we still seem to be doing it for anonymous ftp access from
customer sites!
> DEC appears to have abandoned it for allowing access to the web firewall
> passthru.
Would that that were so in all cases.
Regards,
Dave
|