If you are using the IDNet DNS, can you try this website please http://www.1914-1918.net/ yesterday it said it was not available when I tried at home, but was reported as up when I check with http://www.downforeveryoneorjustme.com/
I just happened to have popped indoors, so tried it, and 'server not found', Glenn.
Server not found here too, Glenn.
I don't know if it helps but the site loads perfectly here in Spain using Telefonica's DNS.
I agree it's up and fine on OpenDNS still no go IDNet DNS.
OK thanks guys
Hi guys, hopefully this should now be working could you check please?
Still not working for me, Glenn.
Or me :dunno:
Ray,
Brian has asked if clearing the DNS cache helps, could you try for me please? Just need to run ipconfig /flushdns from a dos prompt.
Still the same, Glenn, I've even cleared the Browser cache as well.
Thanks Ray.
Couple of more things Brian has ask to check;
QuoteCan they set the DNS in the TCP/IP settings of their PC?
Also are they able to ping the site?
Support are able to access the site from their office
I can try when I get home, but if someone could answer the above questions it would be appreciated.
I can't reach it or ping it, Glenn, and I've got DNS set in the TCP/IP settings.
OK thanks, I'll let Brian & Simon know.
Still not working here, Glenn, after another DNS flush.
Simon did take a look at first but all follow up mails have been from Brian, I think he has now gone home, so it may have to wait until Monday.
He's been on earlies this week. Oddly, I would have expected it to be a job for Martin.
The strange thing is, inside their office network the site loads fine using the same nameservers.
That's weird, but I've known problems with the forum running like treacle and it's fine for them. I wonder if they connect differently to the network than us - though that really shouldn't affect DNS, of course.
Simon has cleared the nameserver cache, but I still can't reach the site, even after flushing my DNS cache, anyone else reach it from an IDNet DNS?
No. :(
Nope.
Server not found using my iPhone via wifi on IDNet dns.
Using 3G it loads fine (and fast).
Thanks for trying
Could they be blocking Idnet ip addresses?
That was my first thought Lance but it appears they can access it from IDNet towers :dunno:
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
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.
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. :)
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.
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.
Testing from 50 locations worldwide and their respective DNS servers have no issues resolving the address.
(http://img.photobucket.com/albums/v427/griff_90/76d30067.jpg)
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.
Thanks Rik, I reverted to OpenDNS to help with looking for my Grandfathers WW1 history.
It's still resolving at this point, Glenn. :fingers: It looks a useful site.
It looks like they have fixed the DNS problem today as this site has been resolving fine for me all day so far.
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. :)
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.
Thanks for the background, Simon. :)
Thanks Simon.
Oo nerdy info. Me like ;D