|
Mime-Version: |
1.0 |
Sender: |
|
Date: |
Fri, 26 Mar 1999 16:12:37 -0500 |
Reply-To: |
|
Subject: |
|
From: |
|
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Content-Type: |
multipart/signed; boundary="==_Exmh_1073362344P"; micalg=pgp-md5;
protocol="application/pgp-signature" |
Comments: |
|
On Fri, 26 Mar 1999 13:25:14 MST, you said:
> The machine that LISTSERV is running on apparently cannot access DNS services to
> find the host 'LISTSERV.OPM.GOV'. That domain does exist in DNS so it's an
> internal network problem of some kind. Perhaps DNS services for that machine
> are not turned on. This is not (strictly speaking) a LISTSERV problem but a
> local network problem although it will keep LISTSERV from working.
Umm.. Ben? Maybe something is screwed up locally, but I fail to find
an A record for listserv.opm.gov, and 2 MX entries, as follows:
listserv.opm.gov. 4158 MX 10 serv1.opm.gov.
listserv.opm.gov. 4158 MX 5 servfwDC.opm.gov.
This may require major tap-dancing, assuming 'servfwDC' is supposed to
do Listserv. In any case, I would *really* recommend having either
an A record or at least a CNAME to an actual A record for the listserv host.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
|
|
|