[dns-operations] Registrar for .net and .com fails to accept an NS in .edu

Wessels, Duane dwessels at verisign.com
Mon Dec 3 21:55:39 UTC 2018


.com, .net, and .edu share the same backend registry database.  The message that you're getting when attempting to register the .net and .com domains is saying that there should be glue records for uphs{1,2,3}.uphs.upenn.edu in that shared database.

So you would have to go to your .edu registrar and add these hosts under the upenn.edu account in order to make it work.


On 12/3/18, 10:35 AM, "dns-operations on behalf of John W.O'Brien" <dns-operations-bounces at dns-oarc.net on behalf of obrienjw at upenn.edu> wrote:

    Good day DNS Operators,
    I am having some trouble making uphs{1,2,3}.uphs.upenn.edu authoritative
    for a number of domains in net and com. The registrar claims that the
    name servers have to be "registered" but doesn't appear to provide a
    mechanism for doing so. There is already appropriate glue in edu for the
    upenn.edu NS, and in upenn.edu for the uphs.upenn.edu NS, and they are
    all happily answering queries for those domains. I'm struggling to
    understand what it means to be registered and how to do it.
    Could someone wiser than I in the ways of registrars and TLD operators
    shed some light on my predicament?
    John W. O'Brien
    University of Pennsylvania
    OpenPGP key IDs:

More information about the dns-operations mailing list