HP3000-L Archives

December 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 12 Dec 1996 22:56:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Chris Bartram wrote:
> A 3000 can't (yet) be a DNS Server. It can "resolve" but not serve.
> Hopefully this will change someday (i.e. if someone gets BIND ported).

Let me clarify this - it is of general relevance although it might
appear as a <plug>.  The 3000 DNS "client" (resolver) can only resolve
A-records for a given name.  It doesn't handle other entries (MX in
particular).  <semi-plug> Chris finally did his own internal DNS
resolution in his NetMail/DeskLink products since the 3000 didn't do MX
queries </semi-plug>.  It also has problems with PTR and CNAME entries,
but I'm
getting too detailed.

The 3000 cannot be a DNS server, and is only a crippled DNS resolver.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2