DISQUS

Scripting News: A question for DNS gurus out there in InternetLand (Scripting News)

  • joec0914 · 3 months ago
    It does take some time for the DNS records to propagate through the various DNS servers. I just pinged r2.ly and it's resolving to 208.69.36.132, which seems like it might be a slicehost address. I have a slicehost account and my server's IP address starts with 209, which is close. Did you set up the DNS records on slicehost to respond to r2.ly?

    How do you know it's not resolving to your IP addresses?

    JoeC
  • dave · 3 months ago
    r2.ly should point to 67.121.212.61 and s3.r2.ly should be a CNAME for s3.amazonaws.com.

    I guess I'm over eager it's only been 5 or 6 hours since I got the notice.
  • Josh Fraser · 3 months ago
    Did you change the TTL on the records you added? The TTL will tell DNS servers how long to cache your records. You should set it at 300 to make your DNS changes go faster. It won't help you this time, but it's a good change to make if you are planning on making a lot of DNS changes in the near future.
  • dave · 3 months ago
    It's a new domain
  • Josh Fraser · 3 months ago
    Thus the "it won't help you this time" disclaimer. :)
  • susanbeebe · 3 months ago
    TTLs are only helpful for DNS changes, not new domain implementations. For changes, set the TTLS low, e.g. 5.
  • dave · 3 months ago
    set the ttls to 1200 secs
  • jeremy · 3 months ago
    Looks like it's still propagating. When I do a "nslookup r2.ly" from my Windows machine, I get my openDNS resolver, which returns 208.69.36.132 when I ping it.

    But when I use this (http://network-tools.com/nslook/Default.asp) to do an nslookup, it sees that slicehost has it. Should probably fix itself soon. Assuming that you've gotten word within the last few hours, of course. If it's been a day, then I'd start to wonder.
  • Chris · 3 months ago
    I think something is messed up on the registrar's side. I tried doing a query using dig and it failed miserably:

    dig r2.ly

    ; <<>> DiG 9.6.0-APPLE-P2 <<>> r2.ly
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached

    I am also unable to do a WHOIS query on the domain too, which points me back to thinking that the registrar messed something up on their end when it comes to the nameservers or activating the domain.
  • susanbeebe · 3 months ago
    Hmm. I just tried to Ping your r2.ly domain - NOT working correctly (non-existent domain?) Odd.

    DIG website tool is showing your r2.ly domain lacks the full "A" record configuration (possible cause?) http://tools.whois.net/index.php?fuseaction=ipa...

    Yep, as others mentioned here... one must wait for DNS propogation to take affect for any new DNS changes (sometimes a full day), which are purely dependent upon global internet "Name Servers" for propogating your new DNS info. Sometimes I accelerate this process by repeatedly "pinging" the new domain name to cause the name servers to return new info.

    Use the Dig website referenced above and also download OstroNet freebie software tool for DNS troubleshooting.

    See also http://rscott.org/dns/a.html for more on A records.

    Cheers!

    @SusanBeebe
  • susanbeebe · 3 months ago
    Non-authoritative Answer
    r2.ly SOA IN ns1.slicehost.net hostmaster@r2.ly
    serial 2009092103
    refresh 28800
    retry 7200
    expire 604800
    minimum 3600
    r2.ly NS IN ns1.slicehost.com
    r2.ly NS IN ns2.slicehost.com
    r2.ly NS IN ns2.slicehost.com
    r2.ly NS IN ns1.slicehost.com
    ns1.slicehost.com A IN 67.23.4.57
    ns2.slicehost.com A IN 173.45.224.132
  • Guan Yang · 3 months ago
    Regardless of how far this has propogated, it is always possible to query the authoritative servers directly.

    There seem to be 5 name servers for .ly. As far as I can tell, they all respond correctly by pointing to ns1.slicehost.com and ns2.slicehost.com. But these servers don't appear to respond to r2.ly, which would suggest that you either did not set this up correctly with Slicehost, or it takes some time for Slicehost's name servers to add a new domain.

    Here's a transcript of my queries: http://gist.github.com/192471

    You can see on lines 60 and 80 and the two Slicehost servers both respond NXDOMAIN, which means that the domain doesn't exist.
  • Guan Yang · 3 months ago
    Sorry, I shouldn't have stopped there.

    The Slicehost servers respond with a SOA record on r2.ly, so it appears that it knows something about the domain name. And s3.r2.ly seems to work! See here: http://gist.github.com/192484

    But you pointed s3.r2.ly at s3.amazonaws.com.r2.ly ; I think what happened is that you just typed in s3.amazonaws.com into the field and Slicehost appended the .r2.ly. It will probably work correctly if you type in s3.amazonaws.com. with a period at the end.

    I think you just fixed something as I was typing, because now the A record at r2.ly is also correct: http://gist.github.com/192489
  • susanbeebe · 3 months ago
    Just noticed you've got

    the SOA record tied to ns1.slicehost.NET and
    the A record tied to ns1.slicehost.COM.

    Not sure if that's a correct configuration or not? Is it .net or .com - notice the different IPs there, etc.
  • Guan Yang · 3 months ago
    Slicehost's name servers seem to be available at both .net and .com with identical IP addresses, so ns1.slicehost.net is the same as ns1.slicehost.com.
  • susanbeebe · 3 months ago
    Ok cool, thanks! Just looked odd at first glance.
  • dave · 3 months ago
    fixed it anyway for the aesthetic and ftw
  • Richard · 3 months ago
    The thing that trips most people up when dealing with Slicehost DNS is adding the domain's nameservers themselves to the Slicehost records. So for example, you would have to add NS records to the domain:

    1. in the domain's settings, add an NS record with the name 'r2.ly.' and data 'ns1.slicehost.net.' (both values without quotes, and note the period at the end of each).
    2. add two more NS records with the same value for Name, and 'ns2.slicehost.net.' and 'ns3.slicehost.net.'

    I don't think it matters whether it's .com or .net since the .com resolves to the same IPs as .net, but it does require that the NS records are added too.

    They have some pretty good documentation on DNS at http://articles.slicehost.com/2007/10/24/creati...
  • Guan Yang · 3 months ago
    Dave, I can tell that you just followed Richard's advice. But I think you may have left out the period at the end of ns1.slicehost.com. and it is now responding as ns1.slicehost.com.r2.ly because Slicehost appended the .r2.ly when there's no period at the end. This will cause failures since ns1.slicehost.com.r2.ly doesn't exist. Adding the . at the end will fix things.
  • dave · 3 months ago
    check
  • susanbeebe · 3 months ago
    R2.ly is now resolving correctly! :)

    Non-authoritative answer:
    Name: r2.ly
    Address: 67.121.212.61
  • Guan Yang · 3 months ago
    Same here!

    Dave, the only problem I can see now is that you still have s3.amazonaws.com without the dot at the end for s3.r2.ly. If you add the dot, so it's s3.amazonaws.com. then everything should be fine.

    Update: This seems to be correct now.
  • dave · 3 months ago
  • susanbeebe · 3 months ago
    YAY~! cool to hear it's working!

    I love the internet :)
  • Guan Yang · 3 months ago
    One final little thing: You seem to have a CNAME from www.r2.ly to rs.ly. Did you mean to point it to r2.ly?

    rs.ly seems to be some Ruby on Rails site hosted at Dreamhost.
  • dave · 3 months ago
    oy! fixed!!
  • endonend · 3 months ago
    Dave - FYI on my system www.r2.ly redirects to:
    http://www.adjix.com/WebObjects/Adjix.woa/

    I pinged the domain and got this IP 67.121.212.61, which looks right.

    Thought it might be my corporate IT DNS caching, but I checked my phone too and got the same result.
  • policeofficer · 2 months ago
    You may try the following command on a Linux system

    dig www.r2.ly NS