<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks to everyone who provided some useful responses.<br>
The bleating about off-topic, I agree, is more off-topic than this
is. The NOG is useful because it has a 'critical mass' of people
who run networks - as someone posted earlier, try to make your
interwebs work without DNS and see how far you go?<br>
<br>
Geordie's post below is also correct in that tools such as
whatsmydns.net are a very high level tool. Clearly with the closure
of open resolvers there's going to need to be some cooperation
amongst network operators and their support staff in providing
troubleshooting assistance if DNS things go pear-shaped in the
future, but if you can narrow it down to a subset of particular
networks, you should probably engage them directly before opting for
a 'scattergun' approach to a mailing list or similar.<br>
<br>
This of course also means that support teams need to be prepared to
provide technical support without the 'sorry, you havn't given me a
valid username, so you're not my customer, goodbye' that I have
experienced before. :/<br>
<br>
Cheers<br>
Mark.<br>
<br>
<br>
<div class="moz-cite-prefix">On 13/02/2014 1:21 p.m., Geordie Guy
wrote:<br>
</div>
<blockquote
cite="mid:CAHTNzf=hZ9Az5uTCc72syUS7kd86cfWSsXzaKOE3Ag3O-Nyc_A@mail.gmail.com"
type="cite">
<div dir="ltr">It is indeed a simple and useful tool but it only
gives a 10000 ft overview of what's going on. Tools like that
get a collection of servers (or routers with IP dns-server
command run on them for the coterie of NOGgers who insist that
any post that doesn't include three AS numbers and a traceroute
is off topic and layers five through seven of the OSI Reference
Model are some sort of New Testament heresy), one per country or
continent, and shows you what IP they resolve for a given fqdn.
As network operators we know that's a fairly blunt instrument.
Yesterday's drama for us showed that the primary problem we had
in the wake of the whoopsie was that Telstra's DNS
infrastructure for enterprise and business seems to have a
shorter TTL or caching lifetimes on those IP records than the
Bigpond side of their business does, that smaller partners and
customers of ours might use. This allowed us to figure out
where it was working and where it wasn't, but as far as
WhatsmyDNS was concerned all of Australia (represented by a
single DNS server) was ok.
<div>
<br>
</div>
<div>So yeah, if you're the type of wag who unveils a new
business service by changing a DNS record, whatsmyDNS will
give you an idea of the geographies that you can probably
expect your service to be live in and who is still getting the
coming soon page with the animated gifs of the construction
signs, but if you've got a local problem with different
Australian networks having different results then you need
looking glasses or a community of operators who can give you
their view of the world.<br>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Feb 13, 2014 at 10:38 AM,
Nathan Phelan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nathan@interconnekt.com.au" target="_blank">nathan@interconnekt.com.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Nice one
Mark!<br>
<br>
<a moz-do-not-send="true" href="https://www.whatsmydns.net/"
target="_blank">https://www.whatsmydns.net/</a> is a
simple dns tool too.<br>
<br>
Cheers,<br>
Nathan<br>
<div class="HOEnZb">
<div class="h5"><br>
-----Original Message-----<br>
From: AusNOG [mailto:<a moz-do-not-send="true"
href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>]
On Behalf Of Nishal Goburdhan<br>
Sent: Wednesday, 12 February 2014 8:45 PM<br>
To: Mark Foster<br>
Cc: <a moz-do-not-send="true"
href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br>
Subject: Re: [AusNOG] Speaking of DNS...<br>
<br>
<br>
On 12 Feb 2014, at 9:23 AM, Mark Foster <<a
moz-do-not-send="true"
href="mailto:blakjak@blakjak.net">blakjak@blakjak.net</a>>
wrote:<br>
<br>
> ... what's the done method of troubleshooting DNS
problems that only affect certain network(s), now that
open resolvers are (hopefully) a thing of the past?<br>
> I have semi-regularly struggled with
troubleshooting email delivery problems (for example),
due to an inability to see what ISP X sees as my MX
record.<br>
><br>
> Onceuponatime I could just query their DNS servers
myself. Now it seems I either have to hope that their
helpdesk understand what an MX record actually is, or
try to find a shell account on a machine within their
network to tinker with...<br>
><br>
> I didn't realise that DNS was something that was a
candidate for a network of 'looking-glass' systems, but
perhaps it is... Need a nice, rate-limited,
hard-to-abuse web-based DNS lookup tool to become
commonly available, perhaps?<br>
<br>
<br>
<a moz-do-not-send="true"
href="http://www.bortzmeyer.org/dns-lg.html"
target="_blank">http://www.bortzmeyer.org/dns-lg.html</a><br>
<br>
<br>
--n.<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>