From: Frank Hoffmann <fh.pad@sni.de>
Subject: Problems with rlogin... and DNS
Keywords: DNS named
Organization: Siemens Nixdorf Info.Sys. AG, Paderborn, Germany
Date: Wed, 12 Aug 1992 12:59:11 GMT

We're having some trouble with ODT 1.1.1c / TCP RunTime 1.1.3f regarding
rlogin and that stuff while relying on a Domain Nameserver.

If we try to Login to the SCO machine from another *NIX system by rlogin,
the ODT/TCP asks the Nameserver in a reverse lookup for the correct name of
the requestor. The Server delivers the information instantly. Afterwards
the ODT/TCP asks for something looking as follows:
		<hostname>.<domain>.<domain>.
The hostname and the domain (succeeded by a dot) were correctly delivered
by the server. ODT/TCP adds the full domain path disregarding the trailing
dot and here we have the finest mess.

I insert a cutout of the DNS dump file here.
The name delivered by the DNS is : faui11.ap.pdb.sni.de.
144.145.6.10 is the DNS for sni.de. domain.

Communication starts here ->

datagram from 129.103.33.92 port 1088, fd 4, len 44
req: nlookup(11.33.103.129.in-addr.arpa) id 256 type=12
req: found '11.33.103.129.in-addr.arpa' as '11.33.103.129.in-addr.arpa' (cname=0)
finddata: added 1 class 1 type 12 RRs
req: foundname = 1 count = 1 founddata = 1 cname = 0
sort_response(1)
findns: SOA found
req: leaving (11.33.103.129.in-addr.arpa, rcode 0)
req: answer -> 129.103.33.92 6 (1088) id=1 Local

datagram from 129.103.33.92 port 1089, fd 4, len 52
req: nlookup(faui11.ap.pdb.sni.de.ap.pdb.sni.de) id 512 type=1
req: found 'faui11.ap.pdb.sni.de.ap.pdb.sni.de' as 'ap.pdb.sni.de' (cname=0)
findns: SOA found
req: leaving (faui11.ap.pdb.sni.de.ap.pdb.sni.de, rcode 3)
req: answer -> 129.103.33.92 6 (1089) id=2 Local

datagram from 129.103.33.92 port 1090, fd 4, len 49
req: nlookup(faui11.ap.pdb.sni.de.pdb.sni.de) id 768 type=1
req: found 'faui11.ap.pdb.sni.de.pdb.sni.de' as 'pdb.sni.de' (cname=0)
findns: 1 NS's added for 'pdb'
ns_forw()
nslookup(nsp=x7ffffaa0,qp=x44c2d8)
nslookup: NS nixpbe.sni.de c1 t2 (x0)
nslookup: 1 ns addrs
nslookup: 1 ns addrs total
forw: forw -> 144.145.6.10 4 (53) nsid=35 id=3 81ms retry 4 sec

datagram from 144.145.6.10 port 53, fd 4, len 107
USER response nsid=35 id=3
resp: ancount 0, aucount 1, arcount 0
doupdate(zone 0, savens 7ffff170, flags 19)
doupdate: dname pdb.sni.de type 6 class 1 ttl 86400
db_update(pdb.sni.de, 0x46631c, 0x46631c, 031, 0x44c578)
db_update: new ttl 713690298, +86400
update failed (DATAEXISTS)
resp: leaving auth NO
send_msg -> 129.103.33.92 (UDP 6 1090) id=3

datagram from 129.103.33.92 port 1091, fd 4, len 45
req: nlookup(faui11.ap.pdb.sni.de.sni.de) id 1024 type=1
req: found 'faui11.ap.pdb.sni.de.sni.de' as 'sni.de' (cname=0)
findns: using cache
findns: 9 NS's added for ''
ns_forw()
nslookup(nsp=x7ffffaa0,qp=x44c2d8)
nslookup: NS NS.NIC.DDN.MIL c1 t2 (x0)
nslookup: 1 ns addrs
nslookup: NS AOS.BRL.MIL c1 t2 (x0)
nslookup: 5 ns addrs
nslookup: NS KAVA.NISC.SRI.COM c1 t2 (x0)
nslookup: 6 ns addrs
nslookup: NS C.NYSER.NET c1 t2 (x0)
nslookup: 7 ns addrs
nslookup: NS TERP.UMD.EDU c1 t2 (x0)
nslookup: 8 ns addrs
nslookup: NS NS.NASA.GOV c1 t2 (x0)
nslookup: 10 ns addrs total
forw: forw -> 144.145.6.10 4 (53) nsid=36 id=4 0ms retry 4 sec

datagram from 144.145.6.10 port 53, fd 4, len 99
USER response nsid=36 id=4
resp: ancount 0, aucount 1, arcount 0
doupdate(zone 0, savens 7ffff170, flags 19)
doupdate: dname sni.de type 6 class 1 ttl 86400
db_update(sni.de, 0x46631c, 0x46631c, 031, 0x44c578)
db_update: new ttl 713690298, +86400
update failed (DATAEXISTS)
resp: leaving auth NO
send_msg -> 129.103.33.92 (UDP 6 1091) id=4

datagram from 129.103.33.92 port 1092, fd 4, len 38
req: nlookup(faui11.ap.pdb.sni.de) id 1280 type=1
req: found 'faui11.ap.pdb.sni.de' as 'faui11.ap.pdb.sni.de' (cname=0)
finddata: added 1 class 1 type 1 RRs
req: foundname = 1 count = 1 founddata = 1 cname = 0
sort_response(1)
findns: SOA found
req: leaving (faui11.ap.pdb.sni.de, rcode 0)
req: answer -> 129.103.33.92 6 (1092) id=5 Local

<- Communication ends here.

Last not least we scrumbled all down to the original domain ap.pdb.sni.de.

This traffic leads to excess LAN usage and to timeouts and error messages
like 'Address already in use' or 'Invalid address' ...

If someone has experience with SCO and DNS probably he gives us a clue,
whether this is the normal behaviour for ODT 1.1 or how we can change it.

thanx in advance ...

frank

PS: This doesn't happen with ODT 2.0 ?? (strange ...)
-------------------------------------------------------------------------------
    __________                  Frank Hoffmann        Voice: [+49] 5251 812 209
     /             /    Siemens-Nixdorf Info. Systems  Data: [+49] 5251 812 207
    /__           /      Dept: AP 52 / SW-Production    Fax: [+49] 5251 811 599
   /' _  _   __  //            Fuerstenallee 7          USA: fh.pad@sni-usa.com
__/__/__(_(_/ /_/^\__    W-4790 Paderborn / Germany    !USA: fh.pad@sni.de
-------------------------------------------------------------------------------
( * )  <--- The green dot.  This mail is reusable. Copy to /dev/null instantly.
-------------------------------------------------------------------------------
Newsgroups: biz.sco.general