[MacPorts] #39868: DNS warning updating outdated

MacPorts noreply at macports.org
Sat Aug 3 07:07:30 PDT 2013


#39868: DNS warning updating outdated
--------------------------------+--------------------------------
  Reporter:  graziosi.angelo@…  |      Owner:  macports-tickets@…
      Type:  defect             |     Status:  closed
  Priority:  Normal             |  Milestone:
 Component:  base               |    Version:  2.2.0
Resolution:  wontfix            |   Keywords:
      Port:                     |
--------------------------------+--------------------------------

Comment (by graziosi.angelo@…):

 Replying to [comment:7 graziosi.angelo@…]:
 > Replying to [comment:6 cal@…]:
 > > Replying to [comment:5 graziosi.angelo@…]:
 > > > With MacPorts 2.2.0 has been introduced a test which tries to load a
 not valid host (invalid-host.macports.org), so that the test HAS success
 if it PRODUCES an error.
 > >
 > > Correct so far. If the lookup of `invalid-host.macports.org` does NOT
 fail, there is a potential problem with your setup.
 > >
 > > > (indeed when I put invalid-host.macports.org in the address bar of
 Chrome, I got an error). And this is flagged to the user with that
 warning.
 > >
 > > It depends what kind of error you get. If it's the error message
 usually printed by Chrome (http://files.neverpanic.de/chrome-dns-
 error.jpg) then your connection is fine and you should not see this
 warning. If you see a different page (usually with your ISP's logo and a
 search form) your DNS servers do not correctly indicate that this domain
 does not exist, which might lead to problems when automatically
 downloading files.
 > >
 > > > So, in short, the warning really means "OK, you have a good
 connection etc.."
 > >
 > > No. If you see the warning, there probably is something wrong with
 your connection.
 > >
 > > Just to make sure, let's verify this is actually the case. Please run
 the following command in a terminal and paste its output:
 > > {{{
 > > /usr/bin/host invalid-host.macports.org
 > > }}}
 >
 >
 > It prints:
 >
 >
 > {{{
 > $ /usr/bin/host invalid-host.macports.org
 > invalid-host.macports.org has address 212.48.8.140
 > Host invalid-host.macports.org not found: 3(NXDOMAIN)
 > Host invalid-host.macports.org not found: 3(NXDOMAIN)
 > }}}
 >
 > Sincerely, I don't understand what is wrong with my connection. I work
 with it since 2004 without big problems..

 OK, I have tried also this:


 {{{
 $ host ____.org
 ____.org has address 212.48.8.140
 Host ____.org not found: 3(NXDOMAIN)
 Host ____.org not found: 3(NXDOMAIN)

 $ host axbc.com
 axbc.com has address 81.169.145.157
 axbc.com has IPv6 address 2a01:238:20a:202:1090::144
 axbc.com mail is handled by 5 smtpin.rzone.de.
 axbc.com mail is handled by 10 mailin.rzone.de.

 $ host axbcdefg.com
 axbcdefg.com has address 212.48.8.140
 Host axbcdefg.com not found: 3(NXDOMAIN)
 Host axbcdefg.com not found: 3(NXDOMAIN)
 }}}

 and searched for 212.48....

 For what I have understood (http://punto-informatico.it/2348608/PI/News
 /dns-promozionali-alice-irritano-utenti.aspx), it seems the result of a
 promotional policy of the provider. In short, the user typing a not
 existent site is redirected to a page (212.48....) proposing some
 alternative suggestions.

 Some year ago (the cited article, I am afraid it is in italian.. :( ) the
 situation was worse because the user was redirected to a page with games,
 pubblicity etc..

 it seems that I have to live with the MacPorts warning... :-(

 > Ciao,
 >  Angelo.

-- 
Ticket URL: <https://trac.macports.org/ticket/39868#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list