Help please

Glenn · Sep 17, 2011, 19:05:05

Thanks for trying

Lance · Sep 17, 2011, 23:06:20

Could they be blocking Idnet ip addresses?

zappaDPJ · Sep 17, 2011, 23:29:12

That was my first thought Lance but it appears they can access it from IDNet towers

Glenn · Sep 18, 2011, 08:44:19

Simon seems to think it's a problem at the other end, but that doesn't explain why the connection is fast to resolve from other DNS servers?

QuoteThe Authoritative nameserver for this domain is flaky - it only occasionally gives a valid response. This problem is magnified because the the time-to-live for the domain is set to 300 seconds (5 mins), where the norm is 48 hours.

http://www.mob.net/~ted/tools/dns.php3?domain=1914-1918.net

Simon_idnet · Sep 18, 2011, 09:02:49

The link I sent tests a bunch of DNS servers. Try it, then wait 6 minutes (for them to all time-out their caches (as instructed by the domain's time-to-live)) and then run it again in another window and compare.

cavillas · Sep 18, 2011, 09:59:03

Tried Idnet servers and was unable to reach the site but it is still ok on open dns servers. Maybe idnet servers don't like wars.

.Griff. · Sep 18, 2011, 13:58:52

Quote from: Lance on Sep 17, 2011, 23:06:20
Could they be blocking Idnet ip addresses?

That wouldn't explain why Idnet users can access it using other DNS providers.

Lance · Sep 18, 2011, 14:02:59

True.

FWIW, I can get to it fine on my work laptop over VPN but can't get to it on my personal laptop over my idnet connection. Just tried both within seconds of each other.

.Griff. · Sep 18, 2011, 14:19:44

Testing from 50 locations worldwide and their respective DNS servers have no issues resolving the address.

Rik · Sep 19, 2011, 11:50:57

The site is now working, but seems to have a bad record somewhere as it drops out again periodically. If Brian refreshes the name servers, it works, but then disappears again after a while.

The IP address is 212.67.210.10, btw.

Glenn · Sep 19, 2011, 12:12:18

Thanks Rik, I reverted to OpenDNS to help with looking for my Grandfathers WW1 history.

Rik · Sep 19, 2011, 12:13:31

It's still resolving at this point, Glenn.

It looks a useful site.

Simon_idnet · Sep 19, 2011, 14:28:32

It looks like they have fixed the DNS problem today as this site has been resolving fine for me all day so far.

Rik · Sep 19, 2011, 16:48:38

Thanks for that, Simon. Brian kicked the nameservers when I spoke to him and, since then, the site has been behaving perfectly. It's amazing what a good talking to from Brian can do.

Simon_idnet · Sep 20, 2011, 10:33:45

I also kicked our nameservers (resolvers) several times over the weekend.

The problem is that the domain has a very short TTL and their DNS server quite often refuses to answer [probably overloaded as all the domains on the server have silly TTL values] - our resolver then caches that bad record.

The error that is being returned by dig is SERVFAIL which means that the domain does exist and the root name servers have information on this domain, but that the authoritative name servers are not answering queries for this domain.

Rik · Sep 20, 2011, 10:44:12

Thanks for the background, Simon.

Glenn · Sep 20, 2011, 10:55:16

Thanks Simon.

Niall · Sep 20, 2011, 15:37:50

Oo nerdy info. Me like