======================================================================== 33

Received: from ALIJKU11.BITNET by ALIJKU11.EDVZ.Uni-Linz.AC.AT (Mailer R2.08

 PTF008) with BSMTP id 3896; Thu, 17 Feb 94 04:51:04 CET

Received: from ALIJKU11 (NJE origin SMTP@ALIJKU11) by ALIJKU11.BITNET (LMail

 V1.1d/1.7f) with BSMTP id 9049; Thu, 17 Feb 1994 04:51:04 +0100

Received: from alijku04.edvz.uni-linz.ac.at by ALIJKU11.EDVZ.Uni-Linz.AC.AT

   (IBM VM SMTP V2R2) with TCP; Thu, 17 Feb 94 04:50:59 CET

Received: from zephyr.isi.edu by alijku04.edvz.uni-linz.ac.at with SMTP id

 AA15474

  (5.65c/IDA-1.4.4 for <Y000080@edvz.uni-linz.ac.at>); Thu,

 17 Feb 1994 04:49:32 +0100

Received: by zephyr.isi.edu (5.65c/5.61+local-16)

        id <AA11335>; Wed, 16 Feb 1994 19:50:09 -0800

Date: Wed, 16 Feb 1994 19:50:09 -0800

From: postel@ISI.EDU (Jon Postel)

Message-Id: <199402170350.AA11335@zephyr.isi.edu>

To: Y000080@edvz.uni-linz.ac.at

Subject: The .YU Domain

Cc: iana@ISI.EDU, domreg@internic.net





Mirjana Tasic:



Hello.  I am investigating the situation with the YU domain.



Do you have concurance from the operators of the secondary name

servers you list for your YU zone data that they are indeed

willing to act as secondaries for your data?



yu.     86400   NS      ns.eu.net.

yu.     86400   NS      sunic.sunet.se.

yu.     86400   NS      ns.uu.net.



--jon.

