nslookup alpine-usa.com
fdiprete at comcast.net
fdiprete at comcast.net
Wed Sep 10 11:01:11 EDT 2008
oh crap. it's a routing problem.
I'm getting a destination unreachable for 24.30.200.19 from my router.
Thanks for the testing guys.
-------------- Original message ----------------------
From: fdiprete at comcast.net
>
>
> this is getting stranger and stranger
>
> on my dns server I can't switch either:
>
> > > server ns1.biz.rr.com
> nslookup: couldn't get address for 'ns1.biz.rr.com': failure
>
> I got the address for ns1.biz.rr at work (I'm ssh'd to my home dns server)
>
> > server 24.30.200.19
> Default server: 24.30.200.19
> Address: 24.30.200.19#53
> > www.alpine-usa.com
>
> ;; connection timed out; no servers could be reached
>
>
> -------------- Original message ----------------------
> From: "Ben Scott" <dragonhawk at gmail.com>
> > On Wed, Sep 10, 2008 at 7:39 AM, Frank DiPrete <fdiprete at comcast.net> wrote:
> > > I am not getting a response while trying to lookup alpine-usa.com
> >
> > When you say "not getting a response", please explain exactly what
> > you're doing, and what happens. :) What command are you running, or
> > what are you doing to test? Are you getting an error message? If so,
> > what does it say? Or does the program you're using just sit there as
> > if it's working, but never finish?
> >
> > In general, the <alpine-usa.com.> zone looks okay.
> >
> > There is no A record associated with <alpine-usa.com.>. There's
> > nothing technically wrong with that, but it's customary to give the IP
> > address of your web server. That will let people type
> > "alpine-usa.com" into any web browser and still get your web site.
> > This won't cause timeouts or other errors, though.
> >
> > Details:
> >
> > I get two nameservers for the delegation from the GTLD parent zone
> > (<com.>). Both appear to be hosted at the Road Runner ISP:
> >
> > $ dig +short NS alpine-usa.com. @a.gtld-servers.net.
> > ns1.biz.rr.com.
> > ns2.biz.rr.com.
> >
> > Querying each of those, I get a response, but it appears there are
> > no A (address) records associated with <alpine-usa.com.>. There are
> > NS (nameserver), SOA (start of authority), and MX (mail exchanger)
> > records, though. Here's what I see:
> >
> > $ dig +noall +ans ANY alpine-usa.com. @ns1.biz.rr.com.
> > alpine-usa.com. 86400 IN MX 10 mail.alpine-usa.com.
> > alpine-usa.com. 86400 IN MX 10 smtp.alpine-usa.com.
> > alpine-usa.com. 86400 IN SOA ns1.biz.rr.com.
> > dnsadmin.rr.com. 2006091250 3600 604800 3600 0
> > alpine-usa.com. 86400 IN NS ns1.biz.rr.com.
> > alpine-usa.com. 86400 IN NS ns2.biz.rr.com.
> > alpine-usa.com. 86400 IN NS dns4.rr.com.
> >
> > (That's what I get when I ask <ns1.biz.rr.com.>; I get the same from
> > <ns2.biz.rr.com.>.)
> >
> > There are some A records for various likely subdomains:
> >
> > $ dig +noall +ans ANY www.alpine-usa.com. @ns2.biz.rr.com.
> > www.alpine-usa.com. 86400 IN A 72.3.185.216
> > $ dig +noall +ans ANY smtp.alpine-usa.com. @ns2.biz.rr.com.
> > smtp.alpine-usa.com. 86400 IN A 67.53.118.39
> > $ dig +noall +ans ANY mail.alpine-usa.com. @ns2.biz.rr.com.
> > mail.alpine-usa.com. 86400 IN A 67.53.118.39
> >
> > -- Ben
> > _______________________________________________
> > gnhlug-discuss mailing list
> > gnhlug-discuss at mail.gnhlug.org
> > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
>
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
More information about the gnhlug-discuss
mailing list