Strange DNS issue [SOLVED BY DEATH]

skottish · 2009-02-16 17:32:55

I'm having a very strange DNS issue with a wireless connection using either wicd or netcfg. I can connect to the router fine, I can ping any website successfully, but I can't connect to any web page with Firefox, nor can I connect with pacman. routes and resolv.conf shows identical information as the other computer which runs fine. Another strange thing is that Konqueror can connect to the first page of any webite, but can't go farther than that. Any ideas?

Mr Green · 2009-02-16 18:27:47

post your configs... wireless does not always out of the box... really depends on your system and set up

skottish · 2009-02-16 18:54:13

Mr Green wrote:

post your configs... wireless does not always out of the box... really depends on your system and set up

Actually, the wireless was working fine until I upgraded last night. I only see this machine about once every three months, so it was a lot. And, the netcfg profile is a copy and paste job from my desktop which works perfectly.

It turns out that there's something more strange going on. I dragged the laptop over to the router, plugged it in with ethernet, and it won't even connect through that. I've even tried dhclient instead of dhcpcd.

So, what configs does everyone want to see?

cactus · 2009-02-16 18:54:17

could also have something to do with the size of the response. If your window scaling factor is being munged upstream from you, it could result in the behavior you are experiencing.

You could try temporarily disabling tcp window scaling, and see if that changes the behavior at all.

skottish · 2009-02-16 18:55:36

cactus wrote:

could also have something to do with the size of the response. If your window scaling factor is being munged upstream from you, it could result in the behavior you are experiencing.
You could try temporarily disabling tcp window scaling, and see if that changes the behavior at all.

I'm a networking idiot. I'm trying this in /etc/sysctl.conf

net.ipv4.tcp_default_win_scale = 0

Doesn't work.

fukawi2 · 2009-02-16 21:51:19

skottish wrote:

So, what configs does everyone want to see?

Output of 'pacman -Sy --debug'

cactus · 2009-02-16 21:58:47

skottish wrote:

cactus wrote:
could also have something to do with the size of the response. If your window scaling factor is being munged upstream from you, it could result in the behavior you are experiencing.
You could try temporarily disabling tcp window scaling, and see if that changes the behavior at all.
I'm a networking idiot. I'm trying this in /etc/sysctl.conf
net.ipv4.tcp_default_win_scale = 0
Doesn't work.

Assuming you applied that with a reboot or a sysctl -p.
So that didn't work. Well shucks. That was my guess.
*head scratching*

Maybe you are on the right track with the wireless stuff.

skottish · 2009-02-16 22:10:45

It's weird because I can ping google or yahoo or anyone else by name. That tells me that DNS is working to some degree. The fact that it works for ping, or with the first address I type into Konqueror, and for nothing else is strange to me. I'm sure it's just some simple configuration issue, but I'm not sure where else to look.

--EDIT--

It is for sure not the wireless. ethernet has exactly the same problem.

skottish · 2009-02-16 22:50:48

fukawi2 wrote:

skottish wrote:
So, what configs does everyone want to see?
Output of 'pacman -Sy --debug'

The first actual error message is failed retrieving file... "No address record". Then all of the errors are "No address record".

fukawi2 · 2009-02-16 23:18:58

Contents of resolv.conf?

skottish · 2009-02-16 23:30:16

fukawi2 wrote:

Contents of resolv.conf?

resolv.conf:

search home
nameserver 192.168.1.1

That's identical to the functioning desktop.

I've also tried manually entering DNS servers, trying unsuccessfully to get resolv.conf not be overwritten, tried resolv.conf.head which is being ignored. Lots of stuff.

--EDIT--

It looks like resolv.conf.head is working now. I still can't get DNS resolution.

resolv.conf:

nameserver 4.2.2.1
nameserver 4.2.2.2

search home
nameserver 192.168.1.1

fukawi2 · 2009-02-17 01:29:23

dig google.com
dig google.com @192.168.1.1
dig google.com @208.67.222.222
dig google.com.au @75.127.96.189

Last edited by fukawi2 (2009-02-17 01:29:55)

skottish · 2009-02-17 04:35:04

Thanks fukawi2. It turns out there's an apparent disk failure on the machine. Whether or not that's what the problem was, I don't know. It seems reasonable though; None of the configs changed, as well none of the networking infrastructure is much different. This has led to yet another set of problems on the same machine, but that's s different thread all together...

fukawi2 · 2009-02-17 05:36:26

Ah yes, Error 666... Why didn't you quote that error code earlier?

Arch Linux

#1 2009-02-16 17:32:55

Strange DNS issue [SOLVED BY DEATH]

#2 2009-02-16 18:27:47

Re: Strange DNS issue [SOLVED BY DEATH]

#3 2009-02-16 18:54:13

Re: Strange DNS issue [SOLVED BY DEATH]

#4 2009-02-16 18:54:17

Re: Strange DNS issue [SOLVED BY DEATH]

#5 2009-02-16 18:55:36

Re: Strange DNS issue [SOLVED BY DEATH]

#6 2009-02-16 21:51:19

Re: Strange DNS issue [SOLVED BY DEATH]

#7 2009-02-16 21:58:47

Re: Strange DNS issue [SOLVED BY DEATH]

#8 2009-02-16 22:10:45

Re: Strange DNS issue [SOLVED BY DEATH]

#9 2009-02-16 22:50:48

Re: Strange DNS issue [SOLVED BY DEATH]

#10 2009-02-16 23:18:58

Re: Strange DNS issue [SOLVED BY DEATH]

#11 2009-02-16 23:30:16

Re: Strange DNS issue [SOLVED BY DEATH]

#12 2009-02-17 01:29:23

Re: Strange DNS issue [SOLVED BY DEATH]

#13 2009-02-17 04:35:04

Re: Strange DNS issue [SOLVED BY DEATH]

#14 2009-02-17 05:36:26

Re: Strange DNS issue [SOLVED BY DEATH]

Board footer