Scripting News - Latest Comments in A question for DNS gurus out there in InternetLand (Scripting News)

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

marco83 — Mon, 04 Jan 2010 08:30:32 -0000

I have similar problem at http://onexenvps.com but they helped me!!!

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

policeofficer — Sun, 27 Sep 2009 09:47:56 -0000

You may try the following command on a Linux system

dig www.r2.ly NS

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

endonend — Thu, 24 Sep 2009 08:35:38 -0000

Dave - FYI on my system www.r2.ly redirects to:
http://www.adjix.com/WebObj...

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.

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

dave — Wed, 23 Sep 2009 23:30:25 -0000

oy! fixed!!

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

Guan Yang — Wed, 23 Sep 2009 23:17:56 -0000

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.

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

susanbeebe — Wed, 23 Sep 2009 23:15:35 -0000

YAY~! cool to hear it's working!

I love the internet :)

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

dave — Wed, 23 Sep 2009 23:13:10 -0000

THANKS!!!!

http://images.scripting.com...

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

dave — Wed, 23 Sep 2009 23:09:10 -0000

set the ttls to 1200 secs

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

Guan Yang — Wed, 23 Sep 2009 23:08:36 -0000

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.

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

dave — Wed, 23 Sep 2009 23:08:01 -0000

fixed it anyway for the aesthetic and ftw

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

dave — Wed, 23 Sep 2009 23:07:22 -0000

check

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

susanbeebe — Wed, 23 Sep 2009 23:06:30 -0000

R2.ly is now resolving correctly! :)

Non-authoritative answer:
Name: r2.ly
Address: 67.121.212.61

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

Guan Yang — Wed, 23 Sep 2009 22:56:22 -0000

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.

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

Guan Yang — Wed, 23 Sep 2009 22:53:12 -0000

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

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

Richard — Wed, 23 Sep 2009 22:50:48 -0000

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.c...

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

susanbeebe — Wed, 23 Sep 2009 22:49:08 -0000

Ok cool, thanks! Just looked odd at first glance.

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

Guan Yang — Wed, 23 Sep 2009 22:46:24 -0000

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.

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

susanbeebe — Wed, 23 Sep 2009 22:46:13 -0000

TTLs are only helpful for DNS changes, not new domain implementations. For changes, set the TTLS low, e.g. 5.

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

susanbeebe — Wed, 23 Sep 2009 22:45:10 -0000

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.

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

Josh Fraser — Wed, 23 Sep 2009 22:43:30 -0000

Thus the "it won't help you this time" disclaimer. :)

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

dave — Wed, 23 Sep 2009 22:42:23 -0000

It's a new domain

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

Guan Yang — Wed, 23 Sep 2009 22:40:05 -0000

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.

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

Josh Fraser — Wed, 23 Sep 2009 22:36:05 -0000

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.

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

susanbeebe — Wed, 23 Sep 2009 22:34:45 -0000

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

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

susanbeebe — Wed, 23 Sep 2009 22:32:13 -0000

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/inde...

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