Forum hard to get to

[sub]

If someone can tell me what exactly is wrong with the DNS entry, I'll try to get it fixed. As I mentioned above, I cant remember ever having problems connecting to the site.

[mvallevand]

I think your DNS is fine, and suggest the problem rests with the few people complaining. I've posted from many ISP's across Canada and the only problem was the major outage a while back. Right now this linux laptop is using OpenDNS and I suggest that anyone having trouble use it instead of a hosts file which I suggested earlier or their own DNS.

Martin

[donschjr]

I would agree it was a problem with Comcast's DNS server but this is the only site I have this problem with. I've used open dns before but never found it as reliable as my isp's server.

[martint123]

I've never had a problem with either gbpvr or opendns in many years.

I know plenty of people who have very obscure and apparently inexplicable problems and they usually involve using their router to be their dns server. If this is the case then I found that setting each PC to opendns as their dns source or if they have many devices, setting the router to use opendns rather than their ISP seems to help.
Linksys routers seem to crop up a lot for me, but that may be due to their popularity over here and/or their price.

[fla]

On Dec 23rd I opened a ticket with EveryDNS (ticket #5429). With the holidays, I'm not expecting a quick "gbpvr support like" reply

Code:

Reverse lookup "funny" for NS1.EVERYDNS.NET:

I'm investigating some DNS issues with a site that uses EveryDNS name servers.
Running the DNS Sleuth perl script, I found that NS1 is breaking a rule in
RFC 1912 Section 2.1 by having a reverse lookup record to NS2 only.

Name Server          IP                 Reverse Lookup

NS1.EVERYDNS.NET --> 208.76.62.100  --> PTR ns2.everydns.net    Expected ns1.everydns.net
NS2.EVERYDNS.NET --> 78.129.207.168 --> PTR ns2.everydns.net    As Expected
NS3.EVERYDNS.NET --> 208.76.63.100  --> PTR ns3.everydns.net    As Expected
NS4.EVERYDNS.NET --> 208.76.60.100  --> PTR ns4.everydns.net    As Expected

Is this an error?

For the record, for 8 years my router is a Linux machine and have been using the same ISP's DNS servers also for 8 years. This gbpvr forums problem is the only DNS issue I've ever had.

[fla]

EveryDNS was acquired by Dyn Inc as explained here. I'm pretty sure all of our DNS issues will disappear once Dyn starts running things at the technical level.

I've always avoided openDNS and the like assuming they must be slower and also because they hijack errors to show adds. I ran a DNS benchmark utility and my Linux machine's and my ISP's DNS blow everyone away. OpenDNS came in sixth in my case.

[donschjr]

Fresh windows 7 install and the problems getting here started again, just made the entry in my host file that fixed it before.

[fla]

The configuration error regarding the everydns.net nameservers that I reported earlier in this thread has been fixed. As I expected Dyn.com knows their stuff. Not sure if this will fix the errors accessing the forums that people have been having though. In early February, Dyn mentioned a 90-120 transition from everydns infrastructure to their own so things should gradually improve over that time period.