DNS Fails on good internet connection

P

plamoreux

Registered
Hi there,

Basically, the upshot is that at home, running OS X 10.1.2 on a PowerBook G4 Titanium, DNS just doesn't work. My Internet connection is fine. I can ping IP addresses and go to IP addresses in my browser, but it can't look up names and resolve them.

I have a PacBell DSL modem. In network prefs, I set up my built-in ethernet manually with all the information necessary - IP address, Gateway, DNS servers, subnet mask. I can do this exact thing on a Windows machine and it works fine. Actually it works fine in OS 9.2, too! No proxie are set and AppleTalk is turned off.

DNS just seems clogged for some reason. If I check out resolv.conf, the DNS servers are listed there. If I check out system logs, there is dns failure all over the place even though the correct server addresses are in there and even though I can successfully ping the dns servers from the Terminal window.

I have tried many times to create new locations. I have tried disabling the internal modem and moving the built-in ethernet to the top of the list in Network Prefs. I've tried rebooting. Creating a new user to log in as.

Does anyone know of any config files, system files or something that can be wiped out so I can start over? Like clear all my locations or something? Do I need to re-install OS X?

Man, in general I've been having a great time with OS X, but this is just driving me crazy. Any help would be so appreciated.

Thanks a bunch.

Paul.
 
I assume that it's not a misconfigured firewall - if you have not changed the firewall settings at all, then it won't be that, but if you have, that's something to check...

Could it be that the problem is with your ISP's DNS servers? (ie. do you have the problem in OS 9 as well) You could just go to some other ISP's website, look for setup instructions, and add the other ISP's DNS servers after your own.

Anyway, good luck getting it figured out
 
Hi,

I did change the Router/Firewall last night, but that was an attempt to fix the problem... and this new one is working fine for Windows and OS9. AND... as a matter of fact, to narrow down the problem, I have cut the firewall out of the equation and I'm now just connecting the Mac to the DSL modem (which also works fine in OS 9, etc.).

The actual DNS servers are up and working. From OS X, I can actually ping the servers from a Terminal window and they reply normally, but I cannot get any names resolved (it just can't turn www.apple.com into its IP address, for example).

Paul.
 
well, i also use pachell in the bay area. first try entering the minimum amount of info required. let it seek anything that it can. i haven't used a dns program since switching to osx so i'm not going to be much help but i know pachell works better with less constaints.
 
A few things to try (in Terminal):

Code: 
$ nslookup
Default Server:  some.server.com
Address:  256.256.256.256

>

does running nslookup result in something similar to the above? That's telling me what nslookup (and hence, /etc/resolv.conf) think should be used. If you receive an error, post it, otherwise /etc/resolv.conf should be good (type exit to quit nslookup).

If good, have you changed anything in NetInfo relating to locations/resolver?
 
Well everybody,

Thanks for all the input. I was at work today and, like alwasy, my OS X connection worked fine. I put the laptop to sleep, headed home to respond to the nslookup suggestion above and wham, it worked at home too. I didn't change locations and I don't have it set to automatic location ssensing. I just opened the lid and it worked. The setups at work and home are so similar now that the same location works in both places.

I have no idea why it works now and not yesterday. I just have to figure that something got unclogged or reset somehow. Now I can also change to my "home" location and that still works, too.

I am really happy that it's working now and I am so sorry to waste you're time. I appreciate the suggestions and the support.

BTW, output of nslookup:
Default Server: dns1-sf.snfc21.pacbell.net
Address: 206.13.28.12

Thanks again,

Paul.
 
well, this sounds like a typical pachell story. i know i sometimes lose service for 5 mins up to a few hours at times. also, you might want to try refreshing your dsl modem at first hint of non service . i typically have to do this about once every couple of weeks or so. just shut down your computer, turn off the modem for about 30 - 60 secs, turn modem back on and boot up. this has solved most of my problems with pachell working or not. sometimes you just have to pray.
 
You must log in or register to reply here.
Back
Top