RE: [Full-Disclosure] sans.org

From: Jerry Heidtke (jheidtke_at_fmlh.edu)
Date: 09/02/03

  • Next message: B3r3n: "Re: [Full-Disclosure] sans.org"
    To: "Marcus Graf" <m.graf@firmenwelt.de>, <full-disclosure@lists.netsys.com>
    Date: Tue, 2 Sep 2003 16:41:24 -0500
    
    

    The administrator of dshield has this to say about resolving sans.org:

    > I didn't find a NS, which resolves sans.org or isc.sans.org.
    > Anyone else?
    Our registrar (register.com) had problems with sans.org and it did get
    removed from some root servers. Hopefully this will be fixed soon.
    DShield.org may be effected as it uses the same infrastructure. I did
    try to move mail server records to make them work without 'sans.org'.

    -- 
    --------------------------------------------------------------
    Johannes Ullrich
    -----Original Message-----
    From: Marcus Graf [mailto:m.graf@firmenwelt.de] 
    Sent: Tuesday, September 02, 2003 4:12 PM
    To: full-disclosure@lists.netsys.com
    Subject: Re: [Full-Disclosure] sans.org
    > can anyone resolve www.sans.org or www.incidents.org?
    > I tried several name servers and none return an A record.
    no problems: 
    www.sans.org => 65.173.218.106
    www.incidents.org => 63.100.47.45
    but the traceroute from here to www.sans.org dies at 
    sl-escal-1-0-0.sprintlink.net [160.81.98.26]
    and the traceroute to www.incidents.org ist interesting:
    ...
    ... 500.ATM4-0.GW5.IAD5.ALTER.NET [152.63.43.137]
    ... 192.168.11.9 [192.168.11.9]
    misconfigured NAT ???
    Ciao
      Marcus
    -- 
    Windows is not the answer.
    Windows is the question and the answer is no.
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html
    Confidentiality Notice: This e-mail message, including any attachments,
    is for the sole use of the intended recipient(s) and may contain
    confidential and privileged information.  Any unauthorized review, use,
    disclosure or distribution is prohibited.  If you are not the intended
    recipient, please contact the sender by reply e-mail and destroy all
    copies of the original message.
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html
    

  • Next message: B3r3n: "Re: [Full-Disclosure] sans.org"

    Relevant Pages

    • RE: [Full-Disclosure] Sobig has a surprise...
      ... I did find one reference that stated Sobig.e had a list of 22 servers that it tried to contact, ... [Full-Disclosure] Sobig has a surprise... ... Confidentiality Notice: This e-mail message, including any attachments, ...
      (Full-Disclosure)
    • Re: [Full-disclosure] targetted SSH bruteforce attacks
      ... Here's something I use on my servers. ... Full-Disclosure - We believe in it. ... Charter: http://lists.grok.org.uk/full-disclosure-charter.html ... Hosted and sponsored by Secunia - http://secunia.com/ ...
      (Full-Disclosure)
    • Re: [Full-disclosure] Getting Off the Patch
      ... [Full-disclosure] Getting Off the Patch ... What you run a patch management company? ... One doesn't need a server farm to prove as more servers ... now you have 4 servers but 8 connections to verify. ...
      (Full-Disclosure)
    • Re: [Full-disclosure] Getting Off the Patch
      ... [Full-disclosure] Getting Off the Patch ... One doesn't need a server farm to prove as more servers ... now you have 4 servers but 8 connections to verify. ...
      (Full-Disclosure)
    • Re: [Full-Disclosure] Allchin bug p-o-c.
      ... Subject: [Full-Disclosure] Allchin bug p-o-c. ... I don't see this service running on any of our servers here, ...
      (Full-Disclosure)