When you can ping other machines via internal IP addresses (on the same 
switched network), you're not really using dns.  You're actually using 
arp tables that uses the layer two addressing within your client 
operating system. (MAC addresses)  Internally, you are just using the 
router's switching side and not routing traffic out to other networks. 
ie. internet perhaps in your case.

It's hard to provide a solid answer or recommendation with the 
information provided but in a nutshell, it would be very handy to post 
your network information on the troubled devices. In windows, ipconfig 
/all or in linux, refer to the network sections here: 
http://www.cyberciti.biz/tips/linux-command-to-gathers-up-information-about-a-linux-system.html
   
If you have other device types, just google on how to obtain a complete 
network view on it.

What do the devices that have trouble connecting to external networks 
have in common?  Example: Are they all on wireless and the others are 
not?  Are these clients configured correctly for your network?  Are they 
all located upstairs/downstairs; static or dynamic ip?

I read a bit in the thread below about possible dhcp service pains - you 
can certainly bypass that by manually specifying a static IP on any 
device within your network.   If you post the network information for 
one of your working clients, I can tell you a safe IP configuration for 
you to use. (outside of the DHCP typical address scope)

Cheers,
Jeff



On 1/6/2012 12:00 PM, [email protected] wrote:
> Send Linux mailing list submissions to
>       [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://oclug.on.ca/mailman/listinfo/linux
> or, via email, send a message with subject or body 'help' to
>       [email protected]
>
> You can reach the person managing the list at
>       [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux digest..."
>
>
> Today's Topics:
>
>     1. Re: need help solving an issue with my network (Gr?goire)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 5 Jan 2012 14:26:05 -0500
> From: Gr?goire, Andr?<[email protected]>
> Subject: Re: [OCLUG-Tech] need help solving an issue with my network
> To: linux<[email protected]>
> Message-ID:
>       
> <b395d5e85b4251478260ff80668add54016869a78...@exchngclsmb1.corp.crtc.gc.ca>
>       
> Content-Type: text/plain; charset="iso-8859-1"
>
> Have you found the problem yet?
>
> My Linksys router had a problem where if it was running for a few days 
> without a power cycle the DHCP service would crash so any new machine or 
> phone trying to lease an IP wouldn't be able to but those already issued IP's 
> worked fine. Power cycle the router and it would work, annoying as hell but 
> finally they issued new firmware that fixed this.
>
>
> ________________________________
> Andre Gregoire
> Senior Enforcement Officer
> Electronic Commerce Enforcement
> Canadian Radio-television and Telecommunications Commission (CRTC)
> [email protected]
> Telephone 819-953-6972
> Government of Canada
>
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Brenda J. Butler
> Sent: January-01-12 12:09 PM
> To: linux
> Subject: Re: [OCLUG-Tech] need help solving an issue with my network
>
>
>
> Do the machines with DNS problems get their IP addresses via
> DHCP?  Do they get their nameserver info from DHCP as well?
>
> If so, is DHCP still working?  DHCP-assigned addesses have
> to be renewed via leases.
>
> Maybe the kids machines/phones DHCP leases expired before
> the other leases ...
>
> Have you done an upgrade lately?  Changes to the firewall?
>
> You can use the dig command to direct DNS queries to a particular
> DNS server:
>
>      dig @server.to.query domain.to.ask.about
>      dig @server.to.query domain.to.ask.about NS
>
> Hope this helps - do send more questions if you have them.
>
> bjb
>
>
> On Sun, Jan 01, 2012 at 11:55:53AM -0500, ed stuckems wrote:
>> Folks:
>>
>> This may be slightly off-topic, so I hope you'll consider this request
>> for help appropriate for this list.
>>
>> My home network is suddenly misbehaving and after poking around a bit
>> I'm at a loss to explain why things aren't working and I can't seem to
>> fix the problem.  Any help/advice would be greatly appreciated.
>>
>> Here's the problem ... My kids' computers recently stopped serving web
>> pages.  After poking around a bit, it appears that dns requests from
>> their machines aren't being resolved.  Poking around more, I've
>> discovered that the game consoles and the android based phone aren't
>> working either and I suspect it's for the same reasons.  The phone
>> worked on the wifi network as recently as last week.  However, there
>> are machines on the network that are working!   My linux box, mac book
>> pro (running Mac OSX), iPad, and Windows Vista computers are all
>> working.
>>
>> All the machines are able to access internal machines/servers/services
>> via ip address (I'm not using dns for internal servers) and everything
>> internal can be pinged and is able to ping (most) everything else.  On
>> those machines that aren't working, nslookup is not able to resolve
>> host names and nslookup returns stating that the dns server(s) timed
>> out.
>>
>> There are 2 dns servers provided to clients on the network: the
>> caching server on the router, and the dns server provided by my
>> service provider.  nslookup reports time outs for both servers.
>>
>> I'm at a loss to explain what's happening and any advice or guidance
>> for correcting the issue would be greatly appreciated.
>>
>> regards
>> eds.
>> _______________________________________________
>> Linux mailing list
>> [email protected]
>> http://oclug.on.ca/mailman/listinfo/linux
> ---end quoted text---
> _______________________________________________
> Linux mailing list
> [email protected]
> http://oclug.on.ca/mailman/listinfo/linux
>
>
> ------------------------------
>
> _______________________________________________
> Linux mailing list
> [email protected]
> http://oclug.on.ca/mailman/listinfo/linux
>
>
> End of Linux Digest, Vol 85, Issue 4
> ************************************
>
>

_______________________________________________
Linux mailing list
[email protected]
http://oclug.on.ca/mailman/listinfo/linux

Reply via email to