On Wed, 06 Aug 2014 14:20:34 +0200
Philip Homburg <philip.homburg at ripe.net> wrote:
> On 2014/08/06 13:51 , David Precious wrote:
> > The DHCP server gives out the IP of my internal gateway/router (a
> > Linux box) as the DNS server to use; that's the box all other
> > devices on my network use, too, so if it had problems I'd certainly
> > have noticed!
> >
> > Presumably the probe attemptign to connect that one observed time
> > means it resolved that hostname, no?
>> I changed something in the probe setting to make it connect even if
> DNS resolving doesn't work. When that takes effect it will be
> possible to figure out what is going on exactly.
I see a connection now. In digging around more to get more logs of
what's going on, I think I found the culprit: for security, I'd denied
the probe from talking to my home server/gateway (but maintaining
forwarding to elsewhere) as it has no business talking to that box (or
anything else internal). However - that also stops it doing DNS from
that same box - d'oh!
In other words, looks like I was being an idiot and the problem was at
this end!
Thanks for your assistance - will keep an eye on the Atlas control
panel to see it appear online.
--
David Precious ("bigpresh") <davidp at preshweb.co.uk>
http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter
www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook
www.preshweb.co.uk/cpan www.preshweb.co.uk/github

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacy policy. You can accept our cookies either by clicking here or by continuing to use the site.