DNS Exit using ::1

bmanning at vacation.karoshi.com bmanning at vacation.karoshi.com
Thu Jul 8 00:22:50 CEST 2010


On Thu, Jul 08, 2010 at 07:50:35AM +0930, Mark Smith wrote:
> On Wed, 07 Jul 2010 14:19:23 -0700
> Seth Mattinen <sethm at rollernet.us> wrote:
> 
> > I recently ran across this gem while trying to troubleshoot a domain for
> > a customer:
> > 
> > ns1.dnsexit.com.        28800   IN      A       69.57.160.118
> > ns1.dnsexit.com.        28800   IN      AAAA    ::1
> > ns2.dnsexit.com.        59400   IN      A       64.182.102.188
> > ns2.dnsexit.com.        59400   IN      AAAA    ::1
> > ns3.dnsexit.com.        57600   IN      A       67.214.175.73
> > ns3.dnsexit.com.        57600   IN      AAAA    ::1
> > ns4.dnsexit.com.        57600   IN      A       67.214.161.154
> > ns4.dnsexit.com.        57600   IN      AAAA    ::1
> > 
> > I was trying to figure out why dig kept saying no servers were reachable
> > until I tried from a IPv4 only site and saw the above. So far it just
> > seems like a nice way to intentionally break things.
> > 
> 
> >From their webpage -
> 
> "Our DNS still keeps 100% uptime history since we started in 1998."
> 
> Not any more ... their DNS servers a ::1 don't work :-)
> 
> 
> 
> > ~Seth

	Bosh! of course it works...  as long as the zones are defined
	on the nameserver running at ::1 ...

--bill


More information about the ipv6-ops mailing list