dns omg wtf

We're in the process of changing registrars on the various jwz/dna domains (to Domain Direct from Verisign/Register), and rumor has it that there has been some pooch-screwage in the process. It all looks fine to me, but I'm on the inside, so who knows. Are www.jwz.org and www.dnalounge.com working for the world-at-large?
Tags: , , ,

64 Responses:

  1. adameros says:

    Works for me.

  2. ammonoid says:

    They both worked for me.

  3. zare_k says:

    Works for me

  4. ajbrown says:

    I can see both.

  5. bdu says:

    Both fine here.

  6. zotz says:

    Also yes for both.

  7. bitwise says:

    I saw breakage on jwz.org (a domain parking page) from last night until this morning, then it started working again. dnalounge.com was working the whole time.

  8. dzm6 says:

    dig also seems to return data, though I'd be hard-pressed to tell you if it reflects the old DNS or the new DNS.

    The serial number returned for dnalounge.com is 2004081600. That would appear to be nicely fresh.

    whois claims that Domain Direct is your registrar.

    Yep. Everything looks to be working. What kind of pooch screwing was reported?

    • jwz says:

      A few people said they were seeing "Your Domain Here" kind of crap on jwz.org. The IP addresses should all be the same as before the switch: one of 209.157.128.39, 209.237.228.50, or 209.157.129.108.

      • bitwise says:

        this guy is right. I belive that last night jwz.org was resolving to 216.40.33.117, because if I punch that into /etc/hosts for http://www.jwz.org, I get the parking page I was seeing earlier.

      • dzm6 says:

        # nslookup http://www.dnalounge.com
        Server: 192.168.0.6
        Address: 192.168.0.6#53

        Non-authoritative answer:
        Name: http://www.dnalounge.com
        Address: 209.157.129.108

        # nslookup http://www.jwz.org
        Server: 192.168.0.6
        Address: 192.168.0.6#53

        Non-authoritative answer:
        Name: http://www.jwz.org
        Address: 209.157.128.39

        My local DNS server is giving good DNS for you. So - your web pages look dandy when viewed from my minitor.

        • dzm6 says:

          Teh Intarweb is broken.

          # nslookup http://www.dnalounge.com
          Server: 192.168.0.6
          Address: 192.168.0.6#53

          Non-authoritative answer:
          Name: http://www.dnalounge.com
          Address: 216.40.33.117

          This bounces me to a parking page.

          http://www.jwz.org appears to be all happy though.

          The DNS record for http://www.dnalounge.com _looks_ current though:

          # dig ALL http://www.dnalounge.com

          ; < <>> DiG 9.2.1 < <>> ALL http://www.dnalounge.com
          ;; global options: printcmd
          ;; Got answer:
          ;; ->>HEADER< <- opcode: QUERY, status: NXDOMAIN, id: 8381
          ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

          ;; QUESTION SECTION:
          ;ALL. IN A

          ;; AUTHORITY SECTION:
          . 10617 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2004081601 1800 900 604800 86400

          ;; Query time: 1 msec
          ;; SERVER: 192.168.0.6#53(192.168.0.6)
          ;; WHEN: Tue Aug 17 09:16:47 2004
          ;; MSG SIZE rcvd: 96

          ;; Got answer:
          ;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 63527
          ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

          ;; QUESTION SECTION:
          ;www.dnalounge.com. IN A

          ;; ANSWER SECTION:
          http://www.dnalounge.com. 386 IN A 216.40.33.117

          ;; AUTHORITY SECTION:
          dnalounge.com. 3417 IN NS ns.meer.net.
          dnalounge.com. 3417 IN NS ns2.meer.net.

          ;; ADDITIONAL SECTION:
          ns.meer.net. 33417 IN A 140.174.164.2
          ns2.meer.net. 33417 IN A 216.206.136.2

          Directly asking your authoritative servers gives the correct IP information, though the serial number of the DNS record is the same as the bad information I get from my local DNS server:

          # dig @ns.meer.net ALL http://www.dnalounge.com

          ; < <>> DiG 9.2.1 < <>> @ns.meer.net ALL http://www.dnalounge.com
          ;; global options: printcmd
          ;; Got answer:
          ;; ->>HEADER< <- opcode: QUERY, status: NXDOMAIN, id: 7203
          ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

          ;; QUESTION SECTION:
          ;ALL. IN A

          ;; AUTHORITY SECTION:
          . 10769 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2004081601 1800 900 604800 86400

          ;; Query time: 12 msec
          ;; SERVER: 140.174.164.2#53(ns.meer.net)
          ;; WHEN: Tue Aug 17 09:20:52 2004
          ;; MSG SIZE rcvd: 96

          ;; Got answer:
          ;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 45368
          ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

          ;; QUESTION SECTION:
          ;www.dnalounge.com. IN A

          ;; ANSWER SECTION:
          http://www.dnalounge.com. 3600 IN A 209.157.129.108

          ;; AUTHORITY SECTION:
          dnalounge.com. 3600 IN NS ns.meer.net.
          dnalounge.com. 3600 IN NS ns2.meer.net.

          ;; ADDITIONAL SECTION:
          ns.meer.net. 3600 IN A 140.174.164.2
          ns2.meer.net. 3600 IN A 216.206.136.2

          ;; Query time: 12 msec
          ;; SERVER: 140.174.164.2#53(ns.meer.net)
          ;; WHEN: Tue Aug 17 09:20:52 2004
          ;; MSG SIZE rcvd: 126

          • dzm6 says:

            It seems that teh intarweb has magically been healed. The chicken sacrifices probably did it, though I suspect that somebody may have recompiled teh intarweb's kernel or something.

  9. marcus132 says:

    Both are working from here.

  10. charles says:

    I got a "Thankyou for shopping at Domains-r-Us" page yesterday when I was trying to find something on jwz.org, but it seems to work now.

  11. brad says:

    From Germany: (because the Internet is so different here)

    http://www.jwz.org
    This domain is currently Under Construction. Please check back soon.

  12. greatbiggary says:

    dna's fine, but jwz just gives me a hex dump, and it's all green... and I am SO clever.

  13. jabberwokky says:

    Me too!

    (via SBC, AmerData Tech and Hotel 8's wifi leaking into the Dennys).

    The first two are home/server and the last is when I read that your site had been sniped on a blog, went to it and it was fine. Now, after this "me too" post, can I do a "first post"?

  14. ralesk says:

    using datanet.hu here, and even THAT works. whatthef.

  15. novalis says:

    Works For Me.

  16. coralscars says:

    dnalounge.com-yes, jwz.org-no.

  17. ijon says:

    both work fine from over here, in Israel.

  18. erorus says:

    Both fine on Adelphia in Northeast PA.. intact pooches here.

  19. starjewel says:

    Why on gods green earth would you want to switch *to* Verisign? I've heard such horror stories about them... (I use godaddy.com)

    • srcosmo says:

      or from, even

    • edm says:

      Jamie doesn't want to switch to Verisign either:

      (to Domain Direct from Verisign/Register)

      Both (jwz.org and dnalounge.com) seem fine from here (TelstraClear connected ISP in New Zealand -- even their transparent proxy seems to have sensible data, which is unusual when pooch screwage has happened.)

      Ewen

  20. buz says:

    All I see is drivel.
    So Yeah - it works from inside the District Court Netwerx.
    oooOOOOooooo!

  21. schnee says:

    Both work fine for me.

  22. chrisglass says:

    Thumbs up from Cincinnati

  23. wilecoyote says:

    Both working from Spain.

  24. wntd says:

    Ill-conceived green-on-black color scheme x2 here

  25. romulusnr says:

    Reading you clear from Speakeasy in Seattle.

  26. recursive says:

    Worked earlier, now http://www.dnalounge.com is giving me ads for paternity testing. And there's this... WHITE background color.

    I even hit shift-reload to be sure.

    • jwz says:

      What's your name server/isp?

      • recursive says:

        Ugh, I'm an idiot. I was sitting at the win2k box, and it's client dns cache was being idiotic as usual.

        (The DNS server is my own, on a comcast cable modem, and things are resolving as expected now.)

    • saintnobody says:

      same here. i'm on roardunner out of albany, new york. jwz.org is fine, though.

      saintnobody@seraph:~$cat /etc/resolv.conf
      nameserver 24.92.32.23
      nameserver 24.92.33.21
      nameserver 24.92.32.22
      search nycap.rr.com
      saintnobody@seraph:~$host -a www.dnalounge.com
      Trying "www.dnalounge.com"
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52821
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

      ;; QUESTION SECTION:
      ;www.dnalounge.com. IN ANY

      ;; ANSWER SECTION:
      www.dnalounge.com. 90 IN A 216.40.33.117

      ;; AUTHORITY SECTION:
      dnalounge.com. 90 IN NS ns2.meer.net.
      dnalounge.com. 90 IN NS ns.meer.net.

      Received 94 bytes from 24.92.32.23#53 in 9 ms
      • jwz says:

        Well ns.meer.net is the authority for both jwz.org and dnalounge.com, and your ISP seems to know that, so I have no fucking idea who one has to blow to get them to flush their fucking cache.

        • havardk says:

          dnalounge.com i still wrong at the level above:

          $ dig @k.gtld-servers.net http://www.dnalounge.com

          ; < <>> DiG 9.2.1 < <>> @k.gtld-servers.net http://www.dnalounge.com
          ;; global options: printcmd
          ;; Got answer:
          ;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 35447
          ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 3

          ;; QUESTION SECTION:
          ;www.dnalounge.com. IN A

          ;; AUTHORITY SECTION:
          dnalounge.com. 172800 IN NS ns1.domaindirect.com.
          dnalounge.com. 172800 IN NS ns2.domaindirect.com.
          dnalounge.com. 172800 IN NS ns3.domaindirect.com.

          ;; ADDITIONAL SECTION:
          ns1.domaindirect.com. 172800 IN A 216.40.33.21
          ns2.domaindirect.com. 172800 IN A 216.40.33.22
          ns3.domaindirect.com. 172800 IN A 204.50.180.58

          ;; Query time: 75 msec
          ;; SERVER: 192.52.178.30#53(k.gtld-servers.net)
          ;; WHEN: Tue Aug 17 11:02:26 2004
          ;; MSG SIZE rcvd: 150

          In addition, Domaindirect's dns servers return different results, so it depends on your luck if you get the right page or not:

          havardk@pluto:~$ host http://www.dnalounge.com ns1.domaindirect.com
          Using domain server:
          Name: ns1.domaindirect.com
          Address: 216.40.33.21#53
          Aliases:

          http://www.dnalounge.com has address 209.157.129.108
          havardk@pluto:~$ host http://www.dnalounge.com ns2.domaindirect.com
          Using domain server:
          Name: ns2.domaindirect.com
          Address: 216.40.33.22#53
          Aliases:

          http://www.dnalounge.com has address 216.40.33.117
          havardk@pluto:~$ host http://www.dnalounge.com ns3.domaindirect.com
          Using domain server:
          Name: ns3.domaindirect.com
          Address: 204.50.180.58#53
          Aliases:

          http://www.dnalounge.com has address 216.40.33.117

          The first one has a later serial number so why the others haven't synched up is a good question.

  27. cabrius says:

    jwz.org works, dnalounge.com doesn't. Here's what 'dig +trace' has to say:

    ; DiG 9.2.2  +trace www.dnalounge.com
    ;; global options: printcmd
    [...the usual root server junk omitted...]
    dnalounge.com. 172800 IN NS ns1.domaindirect.com.
    dnalounge.com. 172800 IN NS ns2.domaindirect.com.
    dnalounge.com. 172800 IN NS ns3.domaindirect.com.
    ;; Received 150 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 86 ms

    www.dnalounge.com. 600 IN A 216.40.33.117
    dnalounge.com. 600 IN NS ns.meer.net.
    dnalounge.com. 600 IN NS ns2.meer.net.
    ;; Received 126 bytes from 216.40.33.21#53(ns1.domaindirect.com) in 186 ms
    • j_b says:

      In my experience, this is the best test, if dig +trace <yourdomain> works, it's all good and everyone else will be fixed when their caches expire.

  28. baconmonkey says:

    the internet is designed to be a self-organizing communications network, capable of surviving large sectional outages.
    Then DNS comes along and pokes you in the eye.

  29. thaths says:

    jwz.org is going to a domain parking page of Domain Direct from here in India. dnalounge.com is pointing correctly.

    Here is what dig and whois are saying:

    thaths@homer:~ [1] $ dig jwz.org

    ; < <>> DiG 9.2.4rc5 < <>> jwz.org
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 53869
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;jwz.org. IN A

    ;; ANSWER SECTION:
    jwz.org. 3600 IN A 209.237.228.50

    ;; AUTHORITY SECTION:
    jwz.org. 3600 IN NS ns.meer.net.
    jwz.org. 3600 IN NS ns2.meer.net.

    ;; ADDITIONAL SECTION:
    ns.meer.net. 3600 IN A 140.174.164.2
    ns2.meer.net. 3600 IN A 216.206.136.2

    ;; Query time: 948 msec
    ;; SERVER: 203.129.240.34#53(203.129.240.34)
    ;; WHEN: Tue Aug 17 10:10:10 2004
    ;; MSG SIZE rcvd: 116

  30. ioerror says:

    Related Categories
    SwabTest Paternity Test
    100% money back accuracy guarantee. The recognized name for DNA Testing
    http://www.swabtest.com
    $149 DNA Paternity Test
    Fast Reliable Accurate Test Kits ISO17025 Accredited. Order Now!
    http://www.metaphasegenetics.com
    SwabTest DNA Testing Lab
    ISO17025 and AABB Accredited Lab. Money Back Guarantee. Order Today!
    http://www.swabtest.com
    $149: Complete DNA Test
    Results: 3-5 days. Accurate (AABB) Reliable (BBB Member) Free Shipping
    http://www.paternityexperts.com
    DNA Paternity Testing
    Low Cost Legal Tests Available. Free DNA Banking Included for 7 yrs
    http://www.PaternityTesters.com
    1-888-986-TEST. toll free
    DNA Testing through 5000 collection centers. World Wide Locations.
    http://www.genetictestlab.com/
    Trace Genetics
    trace your genetic ancestry through the analysis of DNA.
    http://www.tracegenetics.com
    Genealogy and DNA
    Determine if two people are related DNA is the "Gene" in Genealogy
    http://www.familytreedna.com
    DNA Paternity Testing
    High reliability and accuracy in determining paternity. Affiliate.
    thegenesite.com
    Ancestry Fast Painless
    The gene test that works Link your genealogy with our test
    http://www.ancestrybydna.com

  31. anonymous says:

    It's broken for me also, I'm using a UUNet satellite circuit terminating somewhere in Germany. Cossacks...

    Trying "www.dnalounge.com"
    ;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 7177
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;www.dnalounge.com. IN ANY

    ;; ANSWER SECTION:
    http://www.dnalounge.com. 451 IN A 216.40.33.117

    ;; AUTHORITY SECTION:
    dnalounge.com. 451 IN NS ns.meer.net.
    dnalounge.com. 451 IN NS ns2.meer.net.

    ;; ADDITIONAL SECTION:
    ns.meer.net. 172500 IN A 140.174.164.2
    ns2.meer.net. 172500 IN A 216.206.136.2

    Received 126 bytes from 213.193.63.130#53 in 587 ms

  32. anonymous says:

    Currently this is what I'm seeing:

    dig a @ns1.domaindirect.com. http://www.dnalounge.com returns 209.157.129.108
    dig a @ns2.domaindirect.com. http://www.dnalounge.com returns 216.40.33.117
    dig a @ns3.domaindirect.com. http://www.dnalounge.com returns 216.40.33.117

    Umm...yeah.

  33. anonymous says:

    using upc/netherlands dnalounge.com goes toa 'Coming Soon' page, and 'this domain was registered at Domain Direct'

  34. splashed says:

    http://www.dnalounge.com/ doesn't work for me, http://www.jwz.org/ does:

    http://www.dnalounge.com has address 216.40.33.117
    http://www.jwz.org has address 209.157.128.39

  35. wisn says:

    6:35 am EDT aug 17: http://www.jwz.org works, http://www.dnalounge.com points to Domain Direct's filler page.

  36. anonymous says:

    I get the Domain Direct "under construction" page when I go to dnalounge.com. jwz.org is working fine, though.

  37. boggyb says:

    Both work fine here (1225 GMT+1, Demon Internet UK).

  38. anonymous says:

    When I posted ">my blog entry on this subject, jwz.org was marked as parked. Now, having gone to work, and so perhaps using different DNS servers, it's fine but dnalounge.com is coming up as parked.

    nslookup tells me:
    Non-authoritative answer:
    Name: dnalounge.com
    Address: 209.237.228.50
    - which is one of the addresses jwz listed in another comment as correct.

    Going through those IPs:
    http://209.157.128.39 - jwz.org front page
    http://209.237.228.50 - domain parking for dnalounge.com
    http://209.157.129.108 - dnalounge.com front page

    Gerv

  39. aliasrob says:

    Maybe it's because I'm in Europe(UK), but I'm seeing the domain direct holding page...

  40. jason0x21 says:

    Still borked (both of them) coming from bi01p1.nc.us.ibm.com (not sure who our provider is).

  41. cfs_calif says:

    Both domains seem to get where they need to go. Appended are the data I get back from DNS and whois. I would be more censor happy with the whois data, but since that is very happy public stuff and 98% of the world's humans and chimps have your e-mail address, I didn't think it was worth the extra effort. Enjoy!


    > www.jwz.org.
    Server: somedot.com
    Address: 555.555.555.555

    ;; res_mkquery(0, www.jwz.org, 1, 1)
    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 19391, rcode = NOERROR
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 1, authority records = 2, additional = 0

    QUESTIONS:
    www.jwz.org, type = A, class = IN
    ANSWERS:
    -> www.jwz.org
    internet address = 209.157.128.39
    ttl = 2766 (2766)
    AUTHORITY RECORDS:
    -> jwz.org
    nameserver = ns2.meer.net
    ttl = 2766 (2766)
    -> jwz.org
    nameserver = ns.meer.net
    ttl = 2766 (2766)

    ------------
    Non-authoritative answer:
    Name: www.jwz.org
    Address: 209.157.128.39

    > www.dnalounge.com.
    Server: somedot.com
    Address: 555.555.555.555

    ;; res_mkquery(0, www.dnalounge.com, 1, 1)
    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 19390, rcode = NOERROR
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 1, authority records = 2, additional = 0

    QUESTIONS:
    www.dnalounge.com, type = A, class = IN
    ANSWERS:
    -> www.dnalounge.com
    internet address = 209.157.129.108
    ttl = 31 (31S)
    AUTHORITY RECORDS:
    -> dnalounge.com
    nameserver = ns.meer.net
    ttl = 31 (31S)
    -> dnalounge.com
    nameserver = ns2.meer.net
    ttl = 31 (31S)

    ------------
    Non-authoritative answer:
    Name: www.dnalounge.com
    Address: 209.157.129.108

    Domain ID:D1796666-LROR
    Domain Name:JWZ.ORG
    Created On:03-Aug-1998 04:00:00 UTC
    Last Updated On:16-Aug-2004 23:39:33 UTC
    Expiration Date:02-Aug-2007 04:00:00 UTC
    Sponsoring Registrar:R11-LROR
    Status:CLIENT TRANSFER PROHIBITED
    Status:CLIENT UPDATE PROHIBITED
    Registrant ID:tuPnHq7jtdgosVSv
    Registrant Name:Jamie Zawinski
    Registrant Organization:DNA Lounge
    Registrant Street1:375 11th Street
    Registrant City:San Francisco
    Registrant State/Province:CA
    Registrant Postal Code:94103
    Registrant Country:US
    Registrant Phone:+1.4156261409
    Registrant Email:jz480@jwz.org
    Admin ID:tuPdX6HdymvxJgca
    Admin Name:Jamie Zawinski
    Admin Organization:DNA Lounge
    Admin Street1:375 11th Street
    Admin City:San Francisco
    Admin State/Province:CA
    Admin Postal Code:94103
    Admin Country:US
    Admin Phone:+1.4156261409
    Admin Email:jz480@jwz.org
    Tech ID:tuNvrf9XCP3bGE8M
    Tech Name:meer.net meer.net
    Tech Organization:meer.net
    Tech Street1:PO BOX 390804
    Tech City:MOUNTAIN VIEW
    Tech State/Province:CA
    Tech Postal Code:94039-0804
    Tech Country:US
    Tech Phone:+1.4165555555
    Tech Email:jg@MEER.NET
    Name Server:NS.MEER.NET
    Name Server:NS2.MEER.NET


    Registrant:
    DNA Lounge
    375 11th Street
    San Francisco, CA 94103
    US

    Domain name: DNALOUNGE.COM

    Administrative Contact:
    Zawinski, Jamie jz480@jwz.org
    375 11th Street
    San Francisco, CA 94103
    US
    +1.4156261409
    Technical Contact:
    Domain, Direct dnstech@domaindirect.com
    96 Mowat Avenue
    Toronto, ON M6K 3M1
    CA
    +1.4165350123 Fax: +1.4165312516



    Registration Service Provider:
    Domain Direct, help@domaindirect.com
    1-416-531-2084
    http://www.domaindirect.com
    This company may be contacted for domain login/passwords,
    DNS/Nameserver changes, and general domain support questions.


    Registrar of Record: TUCOWS, INC.
    Record last updated on 16-Aug-2004.
    Record expires on 28-Apr-2012.
    Record created on 27-Apr-1995.

    Domain servers in listed order:
    NS.MEER.NET 140.174.164.2
    NS2.MEER.NET 216.206.136.2
  42. rcr203 says:

    I'm sure you've gotten enough responses, but no problems here (east coast)

  43. voidptr says:

    http://www.dnalounge.com/backstage/log/latest.html kicks a "This domain is currently Under Construction. Please check back soon." from Domain Direct.

    The homepage works fine.

    jwz.org works fine all over.

    I guess I'm the only person who tried to click further than the home page.

  44. http://www.jwz.org works fine
    http://www.dnalounge.com is a parking page at domaindirect

    0747 in Phx,AZ

  45. All looks pimpy from Seattle...