I've got an interesting DNS problem on Comcast cable...
The only computers on my LAN that can resolve domain names reliably are my OS X Macs (mark one up for Apple!). I'm behind a Linksys router, and it seems like no matter how I configure my OS 9 Macs or Windows boxes, none of them will resolve IPs. I can ping WAN IPs and I can load WAN sites if I know the IP, but I can't resolve any domain names!
This problem occurs on OS 9 whether I choose DHCP or manual configuration, and whether I manually specify the DNS server(s) or not. Same deal for Win XP. OS X just works (manually and via DHCP).
The only notable exception is a 9.2.2 Mac set up via DHCP. It doesn't seem to have any trouble with getting on the web at all.
Any thoughts? Could Comcast be doing something with their DNS servers that prevents my OS 9 and Windows machines behind my NAT/router from getting on the web? I've literally done nothing at all to my network. One day it worked, the next it didn't...
Peace,
Drew
When you manually specify the DNS address in OS 9, are you using your router's address or the addresses supplied by your ISP? Also, are you able to ping the ISP's DNS addresses from OS X and OS 9 machines?
The way I typically set things up is to plug the ISP-supplied DNS addresses into the router, and have the router act as the DHCP server, then have the clients get all their TCP/IP info via DHCP. That way the clients are getting the IP and DNS addresses from one source. It's always worked for me, regardless of what OS the client machine uses.
Seems like my ol' D-Link NAT router wasn't anymore passing the correct info along - used to work fine, then . . . ?
I semi-'resolved' the problem by manually entering Comcast's DNS addys directly into the TCP/IP info area on the client computers. Worked-for-me, though I guess it didn't work for you. Still takes longer than it ought to for names to resolve. Seems like Comcast did 'something' a few months ago and ever since DNS lookups have been problematic.
[grump]
bloody cablecos
[/grump]
dan k