Heres the main problem and I'm speaking with authority on the situation. The Host for this sites DNS servers SUCK. I've been having issues with all sorts of DNS updates they are CONSTANTLY sending out for all different domains.

The ONLY way to consistently have this site come up is to static in 69.93.171.244 , 69.93.171.245 or 69.93.171.246 for a DNS setting .

My DNS server at home received 4 updates for this site alone in the last 24hrs.

The problem is NOT just dns, but the hostfile on windows based machines keeping old records.

I'm about to call Eu and have him look into it. Someone is clueless.

 

This is gonna make you laugh.. On Windows based systems.. ( I'm gonna take a guess at this ) .

Win98.. open network in your control panel.. open the tcp/ip for your nic card.. there should be something in regards to DNS.. Designate it to enable or ' use these servers ' and put in the IP addy of one of the DNS servers from my post.

Those are the DNS servers of the Host/Server farm of this site. The rest of the sites you browse may seem slow, but they SHOULD come up. You will no longe be traversing to a local dns server, but one that located a great distance where your located.

Actually, on a Windows based system.. 9 times out of 10, its the ' hostfile ' located in the \\windows\system folder ( I think thats where its located ) . Its keeps an entry of all recent dns transactions and forwarding tables. It also kees a record of the DNS servers you have used. If theres a DNS uipdate and your running ' security ' software like Norton Inet Securety, Mccafees and even that rotten little wench called ' Zone Alarm ' ( IE: Make my machine a zombie please! ) odds are it will NOT update correctly and your connection will die.

Whats killing me at the moment is I'm trying to force a recurssive and a non-authoratative update to my bind box ( dns server in my house ) by record request and its lousing really bad.

Heres whats really pissing me off...

Default Server: eclipse.fibreconnections.net
Address: 69.93.171.244
> server 4.2.2.2
Default Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
> www.rangerforums.com
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
DNS request timed out.
timeout was 2 seconds.
*** Request to vnsc-bak.sys.gtei.net timed-out
> server 24.48.33.2
Default Server: alpha.buf.adelphia.net
Address: 24.48.33.2
> www.ranger-forums.com
Server: alpha.buf.adelphia.net
Address: 24.48.33.2
DNS request timed out.
timeout was 2 seconds.
*** Request to alpha.buf.adelphia.net timed-out
>

Its GREAT that fibreconnections servers finds an IP for this site, what about the rest of the bloody planet. My Alpha ( its a real DEC Alpha BTW ) has no records yet it runs an A-root update EVERY 6 HOURS.

Default Server: eclipse.fibreconnections.net
Address: 69.93.171.244
> server 4.2.2.2
Default Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
> www.rangerforums.com
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
DNS request timed out.
timeout was 2 seconds.
*** Request to vnsc-bak.sys.gtei.net timed-out
> server 24.48.33.2
Default Server: alpha.buf.adelphia.net
Address: 24.48.33.2
> www.ranger-forums.com
Server: alpha.buf.adelphia.net
Address: 24.48.33.2
DNS request timed out.
timeout was 2 seconds.
*** Request to alpha.buf.adelphia.net timed-out
> root
Default Server: A.ROOT-SERVERS.NET
Address: 198.41.0.4
>

Pulling normal Virginia based

http://www.opennic.unrated.net/public_servers.html

ns1.opennic.glue (.oss; San Jose, CA, US) - 208.185.249.250
ns4.opennic.glue (.oss; San Jose, CA, US) - 208.185.249.251
ns8.opennic.glue (.parody; US) - 65.243.92.254
ns10.opennic.glue (.indy; Dallas, TX, US ) - 66.227.42.140
ns11.opennic.glue (.indy; Dallas, TX, US ) - 66.227.42.149
ns12.opennic.glue (.fur, .geek; Garden Grove, CA, US ) - 64.81.44.251

All are loused, droped/wrong/insufficient A-record.

ns1.de.opennic.glue (Cologne, DE) - 217.115.138.24
ns1.jp.opennic.glue (Tokyo, JP) - 219.127.89.34
ns2.jp.opennic.glue (Tokyo, JP) - 219.127.89.37
ns1.nz.opennic.glue (Auckland, NZ) - 202.89.131.4
ns1.uk.opennic.glue (London, UK) - 194.164.6.112
ns1.phx.us.opennic.glue (Phoenix, AZ, US) - 63.226.12.96
ns1.sfo.us.opennic.glue (San Francisco, CA, US) - 64.151.103.120
ns1.co.us.opennic.glue (Longmont, CO, US) - 216.87.84.209
ns1.ca.us.opennic.glue (Los Angeles, CA, US) - 67.102.133.222

To the contrare, if you leave the continent and use DNS with the same bloody Root records...

ns1.de.opennic.glue (Cologne, DE) - 217.115.138.24
ns1.jp.opennic.glue (Tokyo, JP) - 219.127.89.34
ns2.jp.opennic.glue (Tokyo, JP) - 219.127.89.37
ns1.nz.opennic.glue (Auckland, NZ) - 202.89.131.4
ns1.uk.opennic.glue (London, UK) - 194.164.6.112
ns1.phx.us.opennic.glue (Phoenix, AZ, US) - 63.226.12.96
ns1.sfo.us.opennic.glue (San Francisco, CA, US) - 64.151.103.120
ns1.co.us.opennic.glue (Longmont, CO, US) - 216.87.84.209
ns1.ca.us.opennic.glue (Los Angeles, CA, US) - 67.102.133.222

> root
Default Server: A.ROOT-SERVERS.NET
Address: 198.41.0.4
> server 67.102.133.222
67.in-addr.arpa nameserver = chia.ARIN.NET
67.in-addr.arpa nameserver = dill.ARIN.NET
67.in-addr.arpa nameserver = BASIL.ARIN.NET
67.in-addr.arpa nameserver = henna.ARIN.NET
67.in-addr.arpa nameserver = indigo.ARIN.NET
67.in-addr.arpa nameserver = epazote.ARIN.NET
67.in-addr.arpa nameserver = figwort.ARIN.NET
Default Server: [67.102.133.222]
Address: 67.102.133.222
> www.ranger-forums.com
Server: [67.102.133.222]
Address: 67.102.133.222
Non-authoritative answer:
Name: ranger-forums.com
Address: 69.93.171.242
Aliases: www.ranger-forums.com
>

LA seems to work fine!

> server 194.164.6.112
Default Server: [194.164.6.112]
Address: 194.164.6.112
> www.ranger-forums.com
Server: [194.164.6.112]
Address: 194.164.6.112
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to [194.164.6.112] timed-out
>

My Bretheren ***** back on the island have no updated records.

Fiberconnections needs to re-issue an authoratative update to the root servers OR have the root servers send the record back out to all the non-authoratative servers on the rock ( earth ) .

Christian or sK0t, say the word and I'll force an update from work tomorrow.n This is maddening.

2 weeks ago, ShadyLuke couldn;t hit this place, Then I couldn't, now apparently tehres a bunch of people whom can't.. I'm about to load BIND on my SParc 80 and replicate ns3.fibreconnections.net 69.93.171.246 with a root record/ip and see what its tables say. Granted, it would take a LONG time, but on a oc48, it won't be that bad.

Either that or ask Eu.

 

Force it D. I don't know what the hell is going on any more.

 

Mate, I think everyone on here whom dosen't even know what ' DNS ' is just had a laugh. I don't even own a ' Windows ' based machine.

What I would like to know is why there are several public, private and open DNS servers out there of which some resolve, and some don't.

I have a tendency to trust my bind box here at the house or the 3500 I tend to oversee daily.

Server Used: [ whois.schlund.info ]

www.ranger-forums.com = [ 69.93.171.242 ]
domain: ranger-forums.com
created: 21-May-2004
last-changed: 22-Oct-2005
registration-expiration: 21-May-2006
nserver: ns1.fibreconnections.net 69.93.171.244
nserver: ns2.fibreconnections.net 69.93.171.245
nserver: ns3.fibreconnections.net 69.93.171.246
status: CLIENT-TRANSFER-PROHIBITED
registrant-firstname: Christian
registrant-lastname: Dorton
registrant-street1: 1302 W DAVIS ST
registrant-pcode: 77304
registrant-state: TX
registrant-city: Conroe
registrant-ccode: US
registrant-phone: 1.9792559131
registrant-email: trevelyn1015@hotmail.com

Yep.

If you wish to allow public forward/reverse lookups to your servers, people will use them, especially when local dns records have had a bad propegation/won't work. People want to get to a website YOUR COMPANY HOSTS, but apparently something isn't right. If YOU can't fix the issue at hand , don't complain about peoples methods.

I mentioned in my prior message the traversing times causing slower connections as well.

You mean to tell me that ALL those dns servers posted above are having issues?

I think its funny as there are users from Colorado, Buffalo, Erie PA , Somewhere in the lost lands of Alaska, all on different providers having the same issue.

The ONLY thing that could have caused ANYTHING related to what you speak of was the recent battle between Cognent and Level3. I can assure you from having first hand in pulling a rack of UBR's durring the fiasco that any issues from said event have long been resolved. ( hint )

There shouldn't be a ' we ' in the equasion. Its a DNS record that none of the users here have any control over, nor do their providers. If you wish to treat this as a comodity of individuals, thats your choice.

My Question to you is how will those that can't get to the site ( for reasons as being stated ) going to post their info to help out? Do you/we/I know exactly how many people are truly being effected by whatever is going on? Nobody can truthfully state a real number.

I don't mean to sound rude, but I am being blunt. Why not force an update and see if that resolves the problem instead of troubleshooting a bunch of peoples connections with different providers on different equipment with different operating systems from all over the country. The common problem is a DNS issue, why not go for that first ? Would seem the most logical thing to do as well as possibly the most expedient.

Christian NEVER HAD AN ISSUE when he was on a dedicated server elsewhere.

Christian is a paying customer. The folks on this site contributed to it. Those revenues are in your companies hands, thus the issue is in your hands and you need to resolve it, not the user base here.

 

Brian, can you force an update and see what happens, if you haven't already? Lets try it.

Honestly, I'm not convinced on anything at the moment.

 

Once again, tonight, people can't get to this site. If anyone static's in a DNS entry of 69.93.171.244 PRESTO! Up comes this site !

Its strange that I just had luke put in the DNS entries and the site came up.. this is after 2 days of downtime for him. This worked for no fewer then 3 people.

I'm willing to bet that ANYONE having problems connecting to this site whom uses the above IP for a DNS server will have no problems reaching this place here.

Its been expressed that the sites host does NOT wish people to use their dns servers. Thus I won't. I'm NOT encouraging others to do so either, even though its a proven ' fix '. I did request for people to remove teh DNS entry after they connected and viewed several of the forums here.

Christian, at this time, I would like make a request. I'm ' nobody ' here as well as many others whom can't *consistantly* connect here.

My request is to move to Clay's service.
D.

 

There will be no moving of the site at the moment. I want to know exactly what's going on before that even becomes an option. We know it's DNS related, and we know that connecting directly to FibreConnections DNS servers causes the resolution to happen just fine.

What I want to know though is why when the Internet's root DNS servers say to go look at ns1, ns2, and ns3.fibreconnections.net to find out where ranger-forums.com is, some DNS servers aren't doing it. Leads me to believe that an authoritative update needs to be performed, either for the first time, or again.

More to come...

 

Locking this thread. Refer to my post in the announcements section.