Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #56343 > unrolled thread

Strange DNS Lookup Problem

Back to article view | Back to comp.sys.mac.system

Contents

  Strange DNS Lookup Problem Matthew Lybanon <lybanon@earthlink.net> - 2014-02-10 10:12 -0600
    Re: Strange DNS Lookup Problem Barry Margolin <barmar@alum.mit.edu> - 2014-02-10 11:57 -0500
      Re: Strange DNS Lookup Problem Matthew Lybanon <lybanon@earthlink.net> - 2014-02-10 11:48 -0600
        Re: Strange DNS Lookup Problem Sandman <mr@sandman.net> - 2014-02-10 17:54 +0000
        Re: Strange DNS Lookup Problem Warren Oates <warren.oates@gmail.com> - 2014-02-11 07:52 -0500
    Re: Strange DNS Lookup Problem Don Bruder <dakidd@sonic.net> - 2014-02-10 08:59 -0800
      Re: Strange DNS Lookup Problem Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-11 13:56 +0000
        Re: Strange DNS Lookup Problem nospam <nospam@nospam.invalid> - 2014-02-11 10:34 -0500
    Re: Strange DNS Lookup Problem Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-10 16:54 -0500

#56343 — Strange DNS Lookup Problem

My wife's MacBook Pro has been running nicely for a year or more.  
During setup it did whatever normally happens automatically to set up 
internet access.  And everything worked just fine (at least from a 
user's point of view).  But one day recently, Safari was unable to find 
web pages (some, not all).  Restarting Safari and restarting the 
computer didn't help.

Short version:  In the morning everything was fine, but in the evening, 
upon waking the computer from sleep, Safari couldn't find most of the 
web pages that had already been opened in tabs.  It could find a few, 
but not many.

I looked at Network in System Preferences.  In AdvancedŠ/DNS tab.  The 
only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).  
10.0.0.<something> describes all theIP addresses in our local network.  
The lock showing in the network pane was locked (and neither my wife nor 
our cats have the admin password).  Whatever was there (or had been 
there) worked just fine for a long time, but suddenly it didn't.

I (as administrator) entered two IP addresses that at some time in the 
dim past our internet provider had given me for DNS lookup, and that 
fixed the problem.

But what happened?  Any ideas, folks?

[toc] | [next] | [standalone]

#56348

In article 
<lybanon-8102FB.10124710022014@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> My wife's MacBook Pro has been running nicely for a year or more.  
> During setup it did whatever normally happens automatically to set up 
> internet access.  And everything worked just fine (at least from a 
> user's point of view).  But one day recently, Safari was unable to find 
> web pages (some, not all).  Restarting Safari and restarting the 
> computer didn't help.
> 
> Short version:  In the morning everything was fine, but in the evening, 
> upon waking the computer from sleep, Safari couldn't find most of the 
> web pages that had already been opened in tabs.  It could find a few, 
> but not many.
> 
> I looked at Network in System Preferences.  In Advanced.../DNS tab.  The 
> only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).  
> 10.0.0.<something> describes all theIP addresses in our local network.  
> The lock showing in the network pane was locked (and neither my wife nor 
> our cats have the admin password).  Whatever was there (or had been 
> there) worked just fine for a long time, but suddenly it didn't.
> 
> I (as administrator) entered two IP addresses that at some time in the 
> dim past our internet provider had given me for DNS lookup, and that 
> fixed the problem.
> 
> But what happened?  Any ideas, folks?

Was it the same 10.0.0.x as the router IP? Many routers provide a DNS 
proxy, and they configure their IP when they send out DHCP responses.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#56351

In article <barmar-63AD6F.11571110022014@news.eternal-september.org>,
 Barry Margolin <barmar@alum.mit.edu> wrote:

> In article 
> <lybanon-8102FB.10124710022014@70-3-168-216.pools.spcsdns.net>,
>  Matthew Lybanon <lybanon@earthlink.net> wrote:
> 
> > My wife's MacBook Pro has been running nicely for a year or more.  
> > During setup it did whatever normally happens automatically to set up 
> > internet access.  And everything worked just fine (at least from a 
> > user's point of view).  But one day recently, Safari was unable to find 
> > web pages (some, not all).  Restarting Safari and restarting the 
> > computer didn't help.
> > 
> > Short version:  In the morning everything was fine, but in the evening, 
> > upon waking the computer from sleep, Safari couldn't find most of the 
> > web pages that had already been opened in tabs.  It could find a few, 
> > but not many.
> > 
> > I looked at Network in System Preferences.  In Advanced.../DNS tab.  The 
> > only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).  
> > 10.0.0.<something> describes all theIP addresses in our local network.  
> > The lock showing in the network pane was locked (and neither my wife nor 
> > our cats have the admin password).  Whatever was there (or had been 
> > there) worked just fine for a long time, but suddenly it didn't.
> > 
> > I (as administrator) entered two IP addresses that at some time in the 
> > dim past our internet provider had given me for DNS lookup, and that 
> > fixed the problem.
> > 
> > But what happened?  Any ideas, folks?
> 
> Was it the same 10.0.0.x as the router IP? Many routers provide a DNS 
> proxy, and they configure their IP when they send out DHCP responses.

The router IP is 10.0.0.1.  That MAY be what I found as the only entry 
in the DNS Servers list; I simply don't remember.  All I can say for 
sure is that we had been going with whatever got put there automatically 
when the computer was first setup, and it worked until suddenly it 
didn't.

[toc] | [prev] | [next] | [standalone]

#56352

In article <lybanon-1C5AF2.11483510022014@70-3-168-216.pools.spcsdns.net>, Matthew Lybanon <lybanon@earthlink.net> wrote:

>> > I (as administrator) entered two IP addresses that at some time in the
>> > dim past our internet provider had given me for DNS lookup, and that
>> > fixed the problem.
>> >
>> > But what happened?  Any ideas, folks?
>>
>> Was it the same 10.0.0.x as the router IP? Many routers provide a DNS
>> proxy, and they configure their IP when they send out DHCP responses.
>
> The router IP is 10.0.0.1.  That MAY be what I found as the only entry
> in the DNS Servers list; I simply don't remember.  All I can say for
> sure is that we had been going with whatever got put there automatically
> when the computer was first setup, and it worked until suddenly it
> didn't.

Sounds like the DNS bridge function in your router gave up. Try entering 
8.8.8.8 - that's the Google DNS, in the prefs, and see if that helps. 

-- 
Sandman[.net]

[toc] | [prev] | [next] | [standalone]

#56393

In article 
<lybanon-1C5AF2.11483510022014@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> 
> The router IP is 10.0.0.1.  That MAY be what I found as the only entry 
> in the DNS Servers list; I simply don't remember.  All I can say for 
> sure is that we had been going with whatever got put there automatically 
> when the computer was first setup, and it worked until suddenly it 
> didn't.

I had a similar problem like that recently on our iMac, but not on the 
older Mac Pro or the older MacBook Pro; all three were configured the 
same way - DNS pointed to the router (in our 192.168.0.1) which pointed 
to Google and OpenDNS via "DNS Relay," which is a setting on the router. 

The iMac (only) suddenly stopped finding its way -- with Firefox. I 
fixed it by setting the DNS in the iMac's Network prefs to the 
Google/OpenDNS and told the router NOT to enable "DNS Relay." Then I 
went and set up the other Macs the same way, of course.
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#56349

In article 
<lybanon-8102FB.10124710022014@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> My wife's MacBook Pro has been running nicely for a year or more.  
> During setup it did whatever normally happens automatically to set up 
> internet access.  And everything worked just fine (at least from a 
> user's point of view).  But one day recently, Safari was unable to find 
> web pages (some, not all).  Restarting Safari and restarting the 
> computer didn't help.
> 
> Short version:  In the morning everything was fine, but in the evening, 
> upon waking the computer from sleep, Safari couldn't find most of the 
> web pages that had already been opened in tabs.  It could find a few, 
> but not many.
> 
> I looked at Network in System Preferences.  In Advanced.../DNS tab.  The 
> only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).  
> 10.0.0.<something> describes all theIP addresses in our local network.  
> The lock showing in the network pane was locked (and neither my wife nor 
> our cats have the admin password).  Whatever was there (or had been 
> there) worked just fine for a long time, but suddenly it didn't.
> 
> I (as administrator) entered two IP addresses that at some time in the 
> dim past our internet provider had given me for DNS lookup, and that 
> fixed the problem.
> 
> But what happened?  Any ideas, folks?

For some reason (not enough information to say exactly what - I've got 
an idea or two, but they're not anything I can support with absolute 
certainty) her rig forgot who it was supposed to ask to do DNS lookups. 
The "10.0.0.x" address *SOUNDS LIKE* something may have gone wrong with 
a wireless connection, and the rig fell back to a default "I've got no 
network conneciton" setup that doesn't know anything about what DNS 
server should be used. SOMETIMES this works well enough due to locally 
cached DNS info, other times, not so much. Usually, when network access 
becomes possible again (for whatever reason...) the settings will revert 
to the ones that work. Other times, it may be necessary to manually put 
them back before everything is right with the world again.

-- 
Security provided by Mssrs Smith and/or Wesson. Brought to you by the letter Q

[toc] | [prev] | [next] | [standalone]

#56396

In message <ldb0hb$9tl$1@dont-email.me> 
  Don Bruder <dakidd@sonic.net> wrote:
> In article 
> <lybanon-8102FB.10124710022014@70-3-168-216.pools.spcsdns.net>,
>  Matthew Lybanon <lybanon@earthlink.net> wrote:

>> My wife's MacBook Pro has been running nicely for a year or more.  
>> During setup it did whatever normally happens automatically to set up 
>> internet access.  And everything worked just fine (at least from a 
>> user's point of view).  But one day recently, Safari was unable to find 
>> web pages (some, not all).  Restarting Safari and restarting the 
>> computer didn't help.
>> 
>> Short version:  In the morning everything was fine, but in the evening, 
>> upon waking the computer from sleep, Safari couldn't find most of the 
>> web pages that had already been opened in tabs.  It could find a few, 
>> but not many.
>> 
>> I looked at Network in System Preferences.  In Advanced.../DNS tab.  The 
>> only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).  
>> 10.0.0.<something> describes all theIP addresses in our local network.  
>> The lock showing in the network pane was locked (and neither my wife nor 
>> our cats have the admin password).  Whatever was there (or had been 
>> there) worked just fine for a long time, but suddenly it didn't.
>> 
>> I (as administrator) entered two IP addresses that at some time in the 
>> dim past our internet provider had given me for DNS lookup, and that 
>> fixed the problem.
>> 
>> But what happened?  Any ideas, folks?

> For some reason (not enough information to say exactly what - I've got 
> an idea or two, but they're not anything I can support with absolute 
> certainty) her rig forgot who it was supposed to ask to do DNS lookups. 
> The "10.0.0.x" address *SOUNDS LIKE* something may have gone wrong with 
> a wireless connection, and the rig fell back to a default "I've got no 
> network conneciton" setup that doesn't know anything about what DNS 
> server should be used. SOMETIMES this works well enough due to locally 
> cached DNS info, other times, not so much. Usually, when network access 
> becomes possible again (for whatever reason...) the settings will revert 
> to the ones that work. Other times, it may be necessary to manually put 
> them back before everything is right with the world again.

No, none of this is at all likely.

Routers are little computers, and they get hot, tired, and wonky. They
should be restarted every month or three.

Normally a router will act as a DNS proxy and normally this a good idea
as it speeds up accessing sites that are accessed with any regularity.
However, routers don't have a lot of memory, so rebooting them is a good
idea.

I have a monthly reminder to reboot my router and cable modem setup on
my phone.

-- 
I WAS NOT TOUCHED "THERE" BY AN ANGEL Bart chalkboard Ep. BABF14

[toc] | [prev] | [next] | [standalone]

#56398

In article <slrnlfkb06.4jp.g.kreme@oswin.local>, Lewis
<g.kreme@gmail.com.dontsendmecopies> wrote:

> Routers are little computers, and they get hot, tired, and wonky. They
> should be restarted every month or three.

crappy ones maybe, but good ones do not need periodic reboots.

[toc] | [prev] | [next] | [standalone]

#56372

On 2014.02.10, 11:12 , Matthew Lybanon wrote:
> My wife's MacBook Pro has been running nicely for a year or more.
> During setup it did whatever normally happens automatically to set up
> internet access.  And everything worked just fine (at least from a
> user's point of view).  But one day recently, Safari was unable to find
> web pages (some, not all).  Restarting Safari and restarting the
> computer didn't help.
>
> Short version:  In the morning everything was fine, but in the evening,
> upon waking the computer from sleep, Safari couldn't find most of the
> web pages that had already been opened in tabs.  It could find a few,
> but not many.
>
> I looked at Network in System Preferences.  In AdvancedŠ/DNS tab.  The
> only entry under DNS Servers was 10.0.0.x (I forget exactly what x was).
> 10.0.0.<something> describes all theIP addresses in our local network.
> The lock showing in the network pane was locked (and neither my wife nor
> our cats have the admin password).  Whatever was there (or had been
> there) worked just fine for a long time, but suddenly it didn't.

The x is likely your router.

It means it's depending on the router's DNS settings to go look for DNS.

Better (IMO) to have the three addresses on the Mac's DNS table[1]:

First:      OpenDNS		208.67.222.222
2nd:        ISP's DNS		(at your ISP's help pages)
3rd:        Router address	10.0.0.x   (x is likely 1)

Router:
1st DNS:    OPENDNS2		208.67.220.220
2nd DNS:    8.8.8.8   (Google)

If the router supports a 3rd DNS (such as Tomato routers)
3rd DNS:    8.8.4.4   (Google) or ISP's alternate DNS address.

The above seems complicated - indeed just setting the first address on 
the Mac will likely work 99.99% of the time.  The rest is additional 
fluff.  On a portable machine, the DNS addresses are best set to 
OpenDNS' addresses (IMO).  On a desktop you can fool around to get a 
feel for which are quickest.

[1] Note that you can enter more than 3 DNS' in the Mac's DNS table - 
however - Unix only looks at the first three, the rest are ignored.

> I (as administrator) entered two IP addresses that at some time in the
> dim past our internet provider had given me for DNS lookup, and that
> fixed the problem.

I suspect they changed or were OOS for a bit.

> But what happened?  Any ideas, folks?

I suspect the DNS addresses on the router are no longer valid (or were 
never set).

-- 
   Privacy has become an essential personal chore that most
   people are not trained to perform.
                  - Jaron Lanier, Scientific American, 2013.11.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web