Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!rutgers!netnews.upenn.edu!scotty.dccs.upenn.edu!hagan
From: hagan@scotty.dccs.upenn.edu (John Dotts Hagan)
Newsgroups: comp.unix.ultrix
Subject: Re: Name server problems in Ultrix 4.0
Keywords: name server, bind
Message-ID: <1990Oct5.185756@scotty.dccs.upenn.edu>
Date: 5 Oct 90 22:57:56 GMT
References: <6066@ge-dab.GE.COM>
Sender: news@netnews.upenn.edu
Reply-To: hagan@scotty.dccs.upenn.edu (John Dotts Hagan)
Organization: University of Pennsylvania
Lines: 79

We have the server duplication problem as well.  For example:

Script started on Fri Oct  5 18:59:21 1990
% nslookup
Default Server:  LOCALHOST.upenn.edu
Address:  127.0.0.1

> set q=ns
> upenn.edu.
Server:  LOCALHOST.upenn.edu
Address:  127.0.0.1

upenn.edu       server name = GRASP.CIS.UPENN.EDU
upenn.edu       server name = OPERATIONS.DCCS.UPENN.EDU
upenn.edu       server name = REMOTE.DCCS.UPENN.EDU
GRASP.CIS.UPENN.EDU     inet address = 130.91.6.7
GRASP.CIS.UPENN.EDU     inet address = 130.91.6.7
GRASP.CIS.UPENN.EDU     inet address = 130.91.6.7
OPERATIONS.DCCS.UPENN.EDU       inet address = 128.91.254.1
OPERATIONS.DCCS.UPENN.EDU       inet address = 128.91.254.1
OPERATIONS.DCCS.UPENN.EDU       inet address = 128.91.254.1
OPERATIONS.DCCS.UPENN.EDU       inet address = 128.91.254.1
OPERATIONS.DCCS.UPENN.EDU       inet address = 128.91.254.1
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
REMOTE.DCCS.UPENN.EDU   inet address = 128.91.2.13
> set q=a
> operations.dccs.upenn.edu
Server:  LOCALHOST.upenn.edu
Address:  127.0.0.1

Name:    operations.dccs.upenn.edu
Addresses:  128.91.254.1, 128.91.254.1, 128.91.254.1, 128.91.254.1
          128.91.254.1

> remote.dccs.upenn.edu
Server:  LOCALHOST.upenn.edu
Address:  127.0.0.1

Name:    remote.dccs.upenn.edu
Addresses:  128.91.2.13, 128.91.2.13, 128.91.2.13, 128.91.2.13
          128.91.2.13, 128.91.2.13

> server grasp.cis.upenn.edu
Default Server:  grasp.cis.upenn.edu
Addresses:  130.91.6.7, 130.91.6.7, 130.91.6.7

> operations.dccs.upenn.edu
Server:  grasp.cis.upenn.edu
Addresses:  130.91.6.7, 130.91.6.7, 130.91.6.7

Name:    operations.dccs.upenn.edu
Address:  128.91.254.1

> ^D% exit
% 
script done on Fri Oct  5 19:00:02 1990


Notice that A records are reported back multiple times - in fact,
operations.dccs.upenn.edu
is listed 5 times in the NS request, and reports 5 addresses (all the same)! 
Then,
remote.dccs.upenn.edu is listed 6 times in the NS request, and has the same A
record come
back 6 times!

The last server, GRASP.CIS.UPENN.EDU, is not running the Ultrix 4.0 named.  It
is using bind 4.8
on a Sun.  It reports the correct information, but got its zone information from
then primary
name server operations.dccs.upenn.edu.  So I don't think it is a problem of
configuration - just
a bug with the Ultrix 4.0 name server.

--Kid.