Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: New cvs setup?
Date: Tue, 30 Oct 2001 12:07:10 -0800	[thread overview]
Message-ID: <m1d734riy2.fsf@reader.newsguy.com> (raw)
In-Reply-To: <87ady8udg6.fsf@mclinux.com> (Josh Huber's message of "Tue, 30 Oct 2001 14:37:13 -0500")

Josh Huber <huber@alum.wpi.edu> writes:

> Richard Hoskins <rmh3@alltel.net> writes:
>
>> Could all this just be a case of Harry's (and the other poster) DNS
>> not being updated properly?
>
> possibly.  my CVS/Root files look like:
>
> :pserver:gnus@quimby.gnus.org:/usr/local/cvsroot
>
> since I changed the hostname from cvs to quimby, but the DNS records
> for cvs have been updated.  cvs is working fine for me...
>
> (to the people who cvs isn't working for)
> what is your external IP visible on the internet?  does it have a
> reverse lookup+forward lookup defined?

A note here is that updating has worked from this IP in the past.

I'm not sure how to tell.
The IP is  66.51.210.228
Can the information you asked about be devined remotely by someone
here who knows how?

Or does this help?
   fwhois 66.51.210.228@whois.arin.net

   [whois.arin.net]
   DSL Extreme (NETBLK-DSLEXTREME-NWK-1)
      7209 Balboa Blvd.
      Van Nuys, CA 91406
      US
   
      Netname: DSLEXTREME-NWK-1
      Netblock: 66.51.192.0 - 66.51.223.255
      Maintainer: DSLE
   
      Coordinator:
         Murphy, Jim  (JM2150-ARIN)  jim@dslextreme.com
         818-902-4821 x104
   
      Domain System inverse mapping provided by:
   
      NS1.DSLEXTREME.COM		63.203.107.16
      NS2.DSLEXTREME.COM		63.203.107.17
   
      ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
   
      Record last updated on 29-Aug-2001.
      Database last updated on 30-Oct-2001 03:20:27 EDT.
   [...]




  reply	other threads:[~2001-10-30 20:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  0:18 Harry Putnam
2001-10-30  0:53 ` Katsumi Yamaoka
2001-10-30  1:56   ` Harry Putnam
2001-10-30  2:12     ` Katsumi Yamaoka
2001-10-30  2:30       ` Harry Putnam
2001-10-30  2:45         ` Katsumi Yamaoka
2001-10-30  3:39           ` Harry Putnam
2001-10-30  4:06             ` Katsumi Yamaoka
2001-10-30  5:03               ` Harry Putnam
2001-10-30  5:34                 ` Katsumi Yamaoka
2001-10-30  5:41                   ` Katsumi Yamaoka
2001-10-30  6:20                   ` Harry Putnam
2001-10-30  7:09                     ` Katsumi Yamaoka
2001-10-30 13:57                     ` news
2001-10-30 14:48                       ` Harry Putnam
2001-10-30 15:03                       ` Harry Putnam
2001-10-30 16:40                         ` Robert Epprecht
2001-10-30 15:27                     ` Dan Christensen
2001-10-30 17:27                       ` Harry Putnam
2001-10-30 17:40                         ` Richard Hoskins
2001-10-30 19:26                           ` Harry Putnam
2001-10-30 19:37                           ` Josh Huber
2001-10-30 20:07                             ` Harry Putnam [this message]
2001-10-30 20:25                               ` Paul Jarc
2001-10-30 21:19                                 ` Josh Huber
2001-10-30 21:46                                   ` Matt Armstrong
2001-10-31  3:01                                     ` Harry Putnam
2001-10-31  4:57                                       ` Paul Jarc
2001-10-30 21:59                             ` Robert Epprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1d734riy2.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).