🚀 go-pugleaf

    It seems that internet mail going to hpiosa.hp.com is getting rejected
    as being for a non-existent host.
   
Oh, it exists.  I just peeked over the partition and it's still there.
 
    The story is this:  Our root nameserver (the NIC) tells me that there
    are three nameservers for HP.COM
    	1. sde.hp.com
    	2. nnsc.nsf.net
    	3. hplabs.hp.com
    
    When querying these, sde.hp.com doesn't respond - perhaps it's broken.
   
I just checked sde and it responds.  I think there was a bit a trouble this
past weekend, but it's been worked out.
 
    nnsc.nsf.net responds, and its authority records lists sd.hp.com, so I'm
    going to assume that it's done a zone transfer or something to serve as
    a secondary server.  It doesn't know anything about 'hpiosa'.
    
It shouldn't.  hpiosa is hpiosa.corp.hp.com.  nnsc should have NS records
pointing to corp.hp.com's three master servers, though, one of which is
sde.hp.com.

    hplabs.hp.com responds too.  The serial number of the authority records
    from hplabs is MUCH higher than the one I got from nnsc, and the host
    I'm looking for IS listed with hplabs.
    
I'll check into this.

    The short-term workaround is for my poor suffering luser to address his
    mail to "@hplabs.hp.com:user@hpiosa.hp.com" so that the host resolution
    will be done on hplabs, which presumably knows about the contents of its
    nameserver.
    
That'll work, but it's unacceptable for the long term.  Your "poor suffering
luser" should be able to send mail to user@hpiosa.corp.hp.com.  I'll get on
it.

cricket

Integrated Office Systems			cricket@hpiosa.corp.hp.com
Hewlett-Packard Corporate			(415) 424-3723
Palo Alto, California