Re: resolver

[His Holiness the Reverend Doktor Xenophon Fenderson, the Carbon(d)ated]

>>>>> "LJ" == Layne Jester <[EMAIL PROTECTED]> writes:

    LJ> nslookup of mail.bullets.net shows the following:

I received the following from NSLOOKUP:

    nemesis:~>nslookup
    Default Server:  bradbury.irtnog.org
    Address:  208.165.241.161

    > set type=ns
    > mail.bullets.net
    Server:  bradbury.irtnog.org
    Address:  208.165.241.161

    Non-authoritative answer:
    mail.bullets.net    canonical name = srv-mail-000.bullets.net
    srv-mail-000.bullets.net    canonical name = dev-edge-000.bullets.net
    dev-edge-000.bullets.net    canonical name = inet-000-seq-001.bullets.net
    inet-000-seq-001.bullets.net        canonical name = 
ici-208-025-046-226.bullets.net

    Authoritative answers can be found from:
    bullets.net
        origin = ns1.vsat.net
        mail addr = root.vsat.net
        serial = 1998052401
        refresh = 86400 (1D)
        retry   = 7200 (2H)
        expire  = 2592000 (4w2d)
        minimum ttl = 86400 (1D)
    > set type=a
    > ici-208-025-046-226.bullets.net
    Server:  bradbury.irtnog.org
    Address:  208.165.241.161

    Non-authoritative answer:
    Name:    ici-208-025-046-226.bullets.net
    Address:  208.25.46.226

Looks like "mail.bullets.net" points to a chain of four CNAMEs.  As
you can see, the last name does resolve properly (although you'll have
to switch the type back to "A" (address) records in NSLOOKUP to get
it).  Executing 'host mail.bullets.net' gives:

    mail.bullets.net is a nickname for srv-mail-000.bullets.net
    srv-mail-000.bullets.net is a nickname for dev-edge-000.bullets.net
    dev-edge-000.bullets.net is a nickname for inet-000-seq-001.bullets.net
    inet-000-seq-001.bullets.net is a nickname for ici-208-025-046-226.bullets.net
    ici-208-025-046-226.bullets.net has address 208.25.46.226

I'm running Red Hat Linux/Alpha 5.2 on a DEC AlphaStation 200 (kernel
2.1.131ac2).  I have "bind-utils-8.1.2-5" installed.

I don't think gethostbyname(3) can handle this many CNAMEs.  I don't
think it is legal for a CNAME to point to another CNAME, though.

But anyway, things should work right, now, because it seems that DNS
has been updated.  "mail.bullet.net" is now a CNAME for "bullet.net",
which resolves as expected.  My name server started resolving things
properly between 8:15 and 8:55AM EST on Dec. 31 (this morning).

-- 
Rev. Dr. Xenophon Fenderson, the Carbon(d)ated, KSC, DEATH, SubGenius, mhm21x16
Pope, Patron Saint of All Things Plastic fnord, and Salted Litter of r.g.s.b
"Abraham came not to sacrifice, but to know once and for all whether this God
was a god to be trusted and obeyed. No other test would do." (Fall of Hyperion)