[61252] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: relays.osirusoft.com

daemon@ATHENA.MIT.EDU (Crist Clark)
Tue Aug 26 18:56:33 2003

Date: Tue, 26 Aug 2003 15:55:10 -0700
From: "Crist Clark" <crist.clark@globalstar.com>
Reply-To: Crist.Clark@globalstar.com
To: "Gary E. Miller" <gem@rellim.com>
Cc: Richard Welty <rwelty@averillpark.net>, nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu


"Gary E. Miller" wrote:
> 
> Yo Richard!
> 
> returning 127.0.0.2 for everything would be an ugly way to bow out.
> 
> I am just seeing timeouts for XXX.relays.osirusoft.com now.

I'm seeing timeout issues too, which would match with DoS attacks. But
in my logs I see,

  Aug 26 01:17:51 aurora named[284]: [ID 866145 daemon.info] lame server resolving '130.38.76.211.relays.osirusoft.com' (in 'relays.osirusoft.COM'?): 127.0.0.1#53

(That's PDT), and in my cache I see,

  $ dig relays.osirusoft.com ns

  ; <<>> DiG 9.2.2 <<>> relays.osirusoft.com ns
  ;; global options:  printcmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59238
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; QUESTION SECTION:
  ;relays.osirusoft.com.          IN      NS

  ;; ANSWER SECTION:
  relays.osirusoft.com.   33863   IN      NS      ns2-relays.osirusoft.com.
  relays.osirusoft.com.   33863   IN      NS      ns1-relays.osirusoft.com.

  ;; ADDITIONAL SECTION:
  ns1-relays.osirusoft.com. 33863 IN      A       127.0.0.1

  ;; Query time: 7 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Tue Aug 26 15:49:15 2003
  ;; MSG SIZE  rcvd: 104

-- 
Crist J. Clark                               crist.clark@globalstar.com

home help back first fref pref prev next nref lref last post