Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!FRIDAY!KVC From: KVC@FRIDAY.A-T.COM (Kevin V. Carosso) Newsgroups: bit.listserv.pmdf-l Subject: RE: Trouble with the Fusion TCP/IP MASTER Message-ID: Date: 9 Feb 90 14:34:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 23 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"rlb@rtpvv1.rtp.semi.harris-atd.com" X-To: rlb@rtpvv1.rtp.semi.harris-atd.com, info-pmdf@YMIR I wrote the Fusion TCP/IP channel for PMDF back when I was working at NRC. It should be using name2adr() just like all the other Fusion utilities. If the logical name FNS_NAME_SERVER is defined to be "BIND", it ought to use the resolver, if not then it will use MACHINE.DB. I remember something about looking in MACHINE.DB first if we are using the resolver, allowing for aliases and shortform names without generating a resolver query. In any case, it ought to work the same as any other Fusion utility. It might be that they've changed something since I left (over a year ago) that breaks the FTCP_LOCAL master channel code. I used PMDF when I was at NRC, but I doubt if they do now. We don't run Fusion so we cannot really support it very well. We do run TGV MultiNet, which pretty much assures that PMDF will work best with that. Since Wollongong is has the same interface as MultiNet, PMDF does well with that too. /Kevin Carosso kvc@friday.a-t.com Innosoft kvc@ymir.bitnet ps. Oh, by the way -- the Fusion channel does not support MX records. I didn't have time to do that between the time I got the BIND resolver/server working for NRC and the time I left. Perhaps someone else has done so?