hollandm@prlhp1.prl.philips.co.uk (Martin Holland) (07/05/88)
I am looking for a machine to act as a name server for our local site. We have a large, diverse number of machines running TCP/IP. (e.g. IBM, HP, SUN, Apollo, PC, VAX) over our local Ethernet. Trying to keep all the local Hostname Tables in step with each other is becoming a real bind. We thought of using the IBM system as a name server as their implementation of TCP/IP allows for a name server. However it transpires that a prerequisite is SQL to contain the database. We don't have SQL and the cost is horrendous. Does anyone know of any name server software that can either be installed onto one of the existing machines or perhaps a stand-alone system perhaps based on a PC which isn't too expensive. Thanks in advance. M. C. Holland.
jbvb@VAX.FTP.COM (James Van Bokkelen) (07/10/88)
It ought to be a relatively simple matter to build the current Bind domain server for use on a Sun, HP, Unix Vax or Apollo. The source is public-domain, and available for anonymous FTP on the Internet (but I'm not sure where - neither ucbvax nor ucbarpa seem to have it). I think it has also been distributed on netnews. If you can't get it any other way, we include Bind 4.7.3 and the matching Sendmail.MX (uses MX records) in one of our public-domain source diskettes (our part PC-801). If you want a dedicated machine, or a supported product, we ported Bind v4.7.3 (the last version before the current 4.8, which itself has gone through some bug fixes since it was first available) to our DOS socket library. Of course, it runs in the foreground on a dedicated PC, but it doesn't need hard disk (unless you want to log things and support high query rates simultaneously). It will initiate zone transfers, but it won't accept incoming requests, so it isn't a good primary server for a dynamic, multi-server domain. I don't know if Unix Bind supports TCP queries, but if it does, we've never tested them on the PC (UDP only). Unmodified 4.7.3 on our Ultrix 2.0 uVax will handle about 45 queries per second (local addresses in its cached database). Our port to DOS will support about 37 queries per second, on an 8Mhz AT clone with a good Ethernet card in it, less on slower machines and with poorer cards. James VanBokkelen FTP Software Inc.
torben@DORSAI.ICS.HAWAII.EDU ("Torben N. Nielsen") (07/10/88)
>It ought to be a relatively simple matter to build the current Bind >domain server for use on a Sun, HP, Unix Vax or Apollo. The source >is public-domain, and available for anonymous FTP on the Internet >(but I'm not sure where - neither ucbvax nor ucbarpa seem to have it). I just checked and it's in ``~ftp/pub/4.3" on ``ucbarpa.Berkeley.Edu". The version currently there is dated April 21. I had no problems compiling it under SunOS4.0. However, I haven't gotten the various network programs such as ``ftp", ``rlogin", .... to work properly with the nameserver. I tried moving 4.3BSD osurces over and after resolving some problems with ``signal", I got everything compiled. However, only ``finger" appears to work correctly. ``Ftp" certainly doesn't. Anyone made the modifications to 4.3BSD sources to get them to work properly with the nameserver and SunOS4.0? Torben
wesommer@athena.mit.edu (William Sommerfeld) (07/10/88)
In article <8807092141.AA19885@vax.ftp.com> jbvb@VAX.FTP.COM (James Van Bokkelen) writes: >It ought to be a relatively simple matter to build the current Bind >domain server for use on a Sun, HP, Unix Vax or Apollo. The source >is public-domain, and available for anonymous FTP on the Internet >(but I'm not sure where - neither ucbvax nor ucbarpa seem to have it). You didn't look hard enough: arpa.berkeley.edu:pub/4.3/bind.4.8.tar.Z 4.8 is known to run on Apollos under SR10.0; if you build libresolv.a into a single object module (using `ld -r'), and then `inlib' it, it magically replaces the gethostbyname in libc, so you don't even have to relink the utilities which call gethostbyname. (SR10 includes a slightly older version of bind). - Bill
ron@topaz.rutgers.edu (Ron Natalie) (07/10/88)
The Berkeley name server will run on most Berkeley UNIX derivatives like your Sun (and your VAX, if it is running BSD or Ultrix). The VAX, if running Wollongong's VMS will also run their version of the name server (probably also BIND, but I've never had to look at it to find out). -Ron
edm@nwnexus.WA.COM (Ed Morin) (07/11/88)
In article <504@prlhp1.prl.philips.co.uk> hollandm@prlhp1.prl.philips.co.uk (Martin Holland) writes: >the local Hostname Tables in step with each other is becoming a real bind. ^^^^ AAAAARRRRRRGGGGGGHHHHHH! (The same from Berkeley could solve some of your problems...) Ed Morin Northwest Nexus Inc. edm@nwnexus.wa.com
cire@CLASH.CISCO.COM (07/12/88)
>> I had no problems compiling it under SunOS4.0. However, I haven't gotten the >> various network programs such as ``ftp", ``rlogin", .... to work properly >> with the nameserver. I tried moving 4.3BSD osurces over and after resolving >> some problems with ``signal", I got everything compiled. However, only >> ``finger" appears to work correctly. ``Ftp" certainly doesn't. Anyone made >> the modifications to 4.3BSD sources to get them to work properly with the >> nameserver and SunOS4.0? >> >> Torben On implementations I've seen the interface to the name server was imbeded in different gethostbyname and similar routines. These routines are contained in libc, libnet, libBSD, or some similar library set. Where is vendor dependent. These libraries need to have the name server version put into them or you need to link with the appropriate object prior to linking with the library. -c cire|eric Eric B. Decker cisco Systems Menlo Park, California email: cire@cisco.com uSnail: 1360 Willow Rd., Menlo Park, CA 94025 Phone : (415) 326-1941
torben@DORSAI.ICS.HAWAII.EDU ("Torben N. Nielsen") (07/13/88)
Eric, Yes, the stuff is imbedded in the library. The problem I'm having is that it *looks* like the nameserver Sun is distributing is pre-4.8 and I wanted to use BIND4.8 and take advantage of the newer features and the bug fixes. However, I do not yet have sources (on order...) for SunOS4.0 and just bringing up the new nameserver doesn't cut it. I *believe* Sun has interfaced the libraries to YP and that they do something non-standard through that.... And I *don't* run YP at all. So I thought the easiest thing to do was to just port the 4.3BSD sources over - compiling them against my now separate nameserver library..... But it isn't that easy; at least not with the version of the 4.3BSD sources I have from the original distribution tape.... The Sun binaries definitely do not appear to work with BIND4.8... Just looking to see if anyone else has a similar problem and maybe a solution :-).... ---Torben
nowicki@SUN.COM (Bill Nowicki) (07/14/88)
I am looking for a machine to act as a name server for our local site. We have a large, diverse number of machines running TCP/IP. (e.g. IBM, HP, SUN, Apollo, PC, VAX) over our local Ethernet. There is no reason you need to FTP sources and compile, unless you have lots of spare time (or expect the experience to be educational). The Domain Name Server has shipped for almost two years as part of the basic Sun Operating System (since SunOS 3.2). The version in SunOS 4.0, which has been shipping for several months, is based on BIND 4.7.3. The current release under development is based on BIND 4.8. You can obtain an up-to-date version of BIND 4.8 through Sun customer service (ask for the "name server kit" patch tape). Yellow Pages is another network name service that Sun, DEC, HP, and some other vendors are using to name users, groups, aliases, etc. in addition to machines. This is in standard SunOS, PC-NFS, Ultrix 2.0, plus others. There is a mechanism that causes the YP server to optionally use the domain name resolver to look up names outside of the current domain. Unfortunately this was broken in SunOS 4.0; the fix is in the name server kit. While I am at it, let me address a few of the other issues recently discussed on the TCP-IP list. Regarding ARPs: the 0.x.y.z request is an artifact of the old software you are using. SunOS 4.0 got rid of the Network Disk protocol entirely and uses NFS for booting. ARPs for self serve two purposes: warn you if someone else on the net is also set to your IP address, and more importantly flush the caches of other people on the net with your previous Ethernet address. Remember DECnet (and sometimes XNS) requires you to change your Ethernet address. You need this ARP or else your server will continue to send to the old address when you reboot. The current release in development has a simple timer that limits ARP broadcasts to one per second. It also has NFS timers that are automatically determined instead of requiring a user to guess at them. Most NFS implementations already have exponential backoff. On broadcasts: our solution: accept all six kinds of broadcasts, but default to SENDING the old one (net.0 or net.subnet.0) until we can be reasonable assured that all SunOS 3.2 or earlier systems are gone. -- Bill Nowicki Sun Microsystems