Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: Andy H on 09 March 2013, 19:17:55
-
My home internet ground to halt earlier this afternoon. I have had letters through from TalkTalk telling me that they were going to migrate me from Nildram/Tiscali/Opal (delete as appropriate) to TalkTalk so not a massive surprise.
A quick trawl through the logs on the mini-server that I use as a gateway revealed a total failure of DNS. I switched off the broadband router for a minute, switched it back on and DNS and internet was restored.
Now that things are working again my logs have stopped showing errors connecting to root DNS servers but I am still getting the following errors. I am guessing that the problem is with the image server & not my end :-\
Mar 9 18:42:52 zaphod named[1532]: error (FORMERR) resolving 'images.omegaowners.com/AAAA/IN': 208.
96.10.221#53
Mar 9 18:42:52 zaphod named[1532]: DNS format error from 66.33.206.206#53 resolving images.omegaown
ers.com/AAAA for client 192.168.39.121#36336: invalid response
Mar 9 18:42:52 zaphod named[1532]: error (FORMERR) resolving 'images.omegaowners.com/AAAA/IN': 66.3
3.206.206#53
Mar 9 18:42:52 zaphod named[1532]: DNS format error from 66.33.216.216#53 resolving images.omegaown
ers.com/AAAA for client 192.168.39.121#36336: invalid response
Mar 9 18:42:52 zaphod named[1532]: error (FORMERR) resolving 'images.omegaowners.com/AAAA/IN': 66.3
3.216.216#53
Mar 9 18:42:54 zaphod named[1532]: DNS format error from 66.33.206.206#53 resolving shop.omegaowner
s.com/AAAA for client 192.168.39.121#46135: invalid response
Mar 9 18:42:54 zaphod named[1532]: error (FORMERR) resolving 'shop.omegaowners.com/AAAA/IN': 66.33.
206.206#53
Mar 9 18:42:54 zaphod named[1532]: DNS format error from 208.96.10.221#53 resolving shop.omegaowner
s.com/AAAA for client 192.168.39.121#46135: invalid response
Mar 9 18:42:54 zaphod named[1532]: error (FORMERR) resolving 'shop.omegaowners.com/AAAA/IN': 208.96
.10.221#53
Mar 9 18:42:54 zaphod named[1532]: DNS format error from 66.33.216.216#53 resolving shop.omegaowner
s.com/AAAA for client 192.168.39.121#46135: invalid response
Mar 9 18:42:54 zaphod named[1532]: error (FORMERR) resolving 'shop.omegaowners.com/AAAA/IN': 66.33.
216.216#53
Mar 9 18:43:05 zaphod named[1532]: DNS format error from 66.33.206.206#53 resolving theboy.omegaown
ers.com/AAAA for client 192.168.39.121#48140: invalid response
Mar 9 18:43:05 zaphod named[1532]: error (FORMERR) resolving 'theboy.omegaowners.com/AAAA/IN': 66.33.206.206#53
Mar 9 18:43:06 zaphod named[1532]: DNS format error from 208.96.10.221#53 resolving theboy.omegaowners.com/AAAA for client 192.168.39.121#48140: invalid response
Mar 9 18:43:06 zaphod named[1532]: error (FORMERR) resolving 'theboy.omegaowners.com/AAAA/IN': 208.96.10.221#53
Mar 9 18:43:06 zaphod named[1532]: DNS format error from 66.33.216.216#53 resolving theboy.omegaowners.com/AAAA for client 192.168.39.121#48140: invalid response
Mar 9 18:43:06 zaphod named[1532]: error (FORMERR) resolving 'theboy.omegaowners.com/AAAA/IN': 66.33.216.216#53
-
Turn off IPV6 ;)
-
Turn off IPV6 ;)
Ahh. IPV6.
I know that I need to make an effort to learn about it and I know that it isn't going to go away.
If it isn't causing problems for the image server I think I will leave it be.............
-
What's a DNS? ???
-
>:( >:( your not the only one breaked off with talktalk ive had problems for months wich they cant sort out
-
Turn off IPV6 ;)
Ahh. IPV6.
I know that I need to make an effort to learn about it and I know that it isn't going to go away.
If it isn't causing problems for the image server I think I will leave it be.............
IPV6 isn't coming this way any time soon, dispite the hype.
No mainstream UK ISP has announced support, beyond a wishy washy "we're looking into it", and I know for a fact that most haven't even started any testing.
Bizarrely, BT's new platform, 21CN, was not designed to accomodate IPV6.
So, disable it. It's pissing off the DNS servers you are using (consumers really, really should be sticking to their own ISP's DNS, or some other caching DNS servers, to reduce traffic on the authoritive name servers - you can't generate enough queries to make a useful caching server (not to say you can't have a caching server of your own, but don't point it at roots, point it to another caching)).
Keep on top of BIND updates. It has as many holes as Chrome.
-
What's a DNS? ???
Converts names to IP.
eg, DNS converts www.omegaowners.com to its real address on the internet - 217.155.56.220