Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Tellemurius]

there was no resolve, says couldn't connect



ok the problem seems to be fixed but im waiting till tomorrow, this is a weird case for me.

[Blank Expression]

Qwest et al. have no rational reason to block Wikipedia.

More likely is that your DNS servers are a box of fail.

[Virex]

A failing DNS server should affect more people then him alone though, yet I canīt find many complaining about problems. What does Tracert say? If you end up in a dead end then maybe there's something wrong with the network architecture at that point and the internet hasn't been able to reconfigure yet.


edit: Scratch that, not being able to resolve it means a failing DNS somewhere. To fix it you'd somehow need to tell your PC to request the IP from a different DNS, though how that would work I don't know.

[Sergius]

You could try setting the DNS servers by hand.

8.8.8.8 is google's main, I think. THere's also OpenDNS.

[G-Flex]

there was no resolve, says couldn't connect



ok the problem seems to be fixed but im waiting till tomorrow, this is a weird case for me.

The domain name wasn't resolved at all? Why didn't you say that before?

Honestly, when you're looking for help with these things, you ought to paste/copy exactly what the results of the commands are, that way there aren't communication breakdowns like these. It's been several posts just to get this little bit of information, which is crucial to actually figuring out the problem, whereas if you had supplied this information to begin with, preferably by saying the exact results of what you tried to do, it would have been done by now. "I can't resolve the domain name" says a whole lot more than "I can't get to Wikipedia".


Have you messed with the DNS settings on your router, or no? If so, then whatever you set them to is probably the problem, and if not, try to. I use 8.8.8.8 and 8.8.4.4. Preferably set these on your router, not your computer's TCP/IP configuration.

[Tellemurius]

i dunno alright, i mostly handle the computer stuff and barely ask online. i bitched at qwest and they said something about some security bullshit >.>

[G-Flex]

What security bullshit? At their end or yours?

[Tellemurius]

their end apparently, if it was my end i would expected a notice or something.

[G-Flex]

Why would they send you a notice if you had a problem on your network?

[Captain Mayday]

Can you ping 208.80.152.2?
If you can, it's a DNS issue.

[Tellemurius]

Why would they send you a notice if you had a problem on your network?

im on a dedicated line, im paying for the extra shit and they called me last time when they were going to shut down for maintenence.

[Tellemurius]

again? ok what is wrong with their DNS servers now?

[G-Flex]

Why would they send you a notice if you had a problem on your network?

im on a dedicated line, im paying for the extra shit and they called me last time when they were going to shut down for maintenence.

I said on your network, not your connection to them. They wouldn't know or even particularly care about a problem with your router or computer unless it's violating terms of service or otherwise screwing things up. For instance, I could set my router to use some bullshit IP address for DNS services, or mess up my Windows TCP/IP configuration in any number of ways, and my ISP wouldn't magically know this, and even if they did, they wouldn't care because it's not their problem.


Listen to Captain Mayday. Try to ping that IP address. Tell us what happens.

[Tellemurius]

ok i pinged it and got 86ms so i guess the DNS server is the bitch of the week. i'll try to map out to what my DNS servers are and see wtf is their problem.




this is my traceroute report from my gateway:

Spoiler (click to show/hide)

Traceroute Results
1 30ms 30ms 30ms           hlrn-dsl-gw84-149.hlrn.qwest.net [207.225.112.149]
2 20ms 30ms 20ms           hlrn-agw1.inet.qwest.net [71.217.190.153]
3 30ms 30ms 20ms           dvr-core-01.inet.qwest.net [67.14.24.21]
4 50ms 40ms 20ms           dvr-brdr-01.inet.qwest.net [205.171.10.6]
5 20ms 30ms 20ms           63.146.26.130
6 30ms 20ms 20ms           vb2000d1.rar3.denver-co.us.xo.net [207.88.13.182]
7 50ms 50ms 40ms           te-4-2-0.rar3.dallas-tx.us.xo.net [207.88.12.41]
8 80ms 100ms 70ms         207.88.14.42.ptr.us.xo.net [207.88.14.42]
9 90ms 80ms 80ms           w006.z207088246.xo.cnc.net [207.88.246.6]
10 90ms 80ms 80ms         rr.pmtpa.wikimedia.org [208.80.152.2]

[G-Flex]

Okay, so your ISP is having DNS issues, probably. Just change the DNS servers your router is using, as was suggested earlier, and you should be fine.