[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] Re: SOLVED (was: fetchmail, fetchnews can't get thru router)



* Matthias Andree on Sunday, August 10, 2008 at 14:22:13 +0200
> Christian Ebert schrieb am 2008-08-10:
>> It would be good if someone running Linux connected via Speedport
>> 701 -> SpeedPortHS 300 could confirm/deny the t-online support
>> claim that there are no issues with Linux and DHCP on the client
>> machine.
> 
> While not running that combination, the resulting configuration I saw
> doesn't hint to DHCP issues.  I cannot vouch for the DHCP server handing
> out the addresses of two properly working DNS servers, and if one is
> down, that might indeed cause timeouts observed, depending on how
> exactly the 700V (701V?) forwards. I usually configure my Linux boxen
> (no laptops though, but PCs) with a local resolver (BIND9 or djbdns) and
> dnsmasq.

I believe MacOS runs BIND as well; there was a big huha about a
late security upgrade by Apple recently. -- Yes, I've done the
necessary update. Although, from what I've heard it's still not
the most recent BIND version.

>> Probably not. _Probably_ they are not queried automatically (by
>> fetchmail, fetchnews?).
> 
> Your computer queries the SpeedPort router, which likely forwards the
> requests to the two DNS servers it obtained via PPPoE via modem.
> 
> MacOS --> 192.168.2.1 Speedport EXTADDR ---> one-out-of-two-DNS

Yup. But surely other apps beside fechmail, fetchnews have to do
that too. Very strange.

>> After digging the right nameservers out of the Speedport config
>> interface (STATUS::Details/Netzwerk) I entered those DNS servers
>> in the Network Preferences pane, and they work.
> 
> All that you're reporting hint to the Speedport's DNS client being
> b0rked. I only briefly worked with a W900V, and didn't see any issues
> there.  Is the firmware the most current one?

Yep.

>> In my experiments before I tried some DNS server addresses from
>> http://www.atelier89.de/users/dirk/t-o/010.html
>> but not the right ones, or not in the right order -- my first one
>> is not even mentioned there, see below; although, as I've found
>> by now it /is/ included in the output of:
>> 
>> $ nslookup www-proxy.t-online.de
>> or better
>> $ nslookup www-proxy.t-ipnet.de
> 
> nslookup often causes misleading output. Use dig for debugging.

This is the output with DHCP and no manually configged nameservers:
$ dig www-proxy.t-ipnet.de

; <<>> DiG 9.3.5-P1 <<>> www-proxy.t-ipnet.de
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13663
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www-proxy.t-ipnet.de.          IN      A

;; ANSWER SECTION:
www-proxy.t-ipnet.de.   22353   IN      A       217.237.150.115
www-proxy.t-ipnet.de.   22353   IN      A       217.237.150.188
www-proxy.t-ipnet.de.   22353   IN      A       217.237.150.205
www-proxy.t-ipnet.de.   22353   IN      A       217.237.151.51
www-proxy.t-ipnet.de.   22353   IN      A       217.237.151.115
www-proxy.t-ipnet.de.   22353   IN      A       217.237.151.142
www-proxy.t-ipnet.de.   22353   IN      A       217.237.151.205
www-proxy.t-ipnet.de.   22353   IN      A       217.237.148.22
www-proxy.t-ipnet.de.   22353   IN      A       217.237.148.70
www-proxy.t-ipnet.de.   22353   IN      A       217.237.148.102
www-proxy.t-ipnet.de.   22353   IN      A       217.237.149.142
www-proxy.t-ipnet.de.   22353   IN      A       217.237.149.205
www-proxy.t-ipnet.de.   22353   IN      A       217.237.150.51

;; Query time: 54 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sun Aug 10 15:22:32 2008
;; MSG SIZE  rcvd: 246

This the one with manually set DNS servers:

~/.vim/after/ftplugin$ dig www-proxy.t-ipnet.de

; <<>> DiG 9.3.5-P1 <<>> www-proxy.t-ipnet.de
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54324
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www-proxy.t-ipnet.de.          IN      A

;; ANSWER SECTION:
www-proxy.t-ipnet.de.   12366   IN      A       217.237.151.142
www-proxy.t-ipnet.de.   12366   IN      A       217.237.151.205
www-proxy.t-ipnet.de.   12366   IN      A       217.237.148.22
www-proxy.t-ipnet.de.   12366   IN      A       217.237.148.70
www-proxy.t-ipnet.de.   12366   IN      A       217.237.148.102
www-proxy.t-ipnet.de.   12366   IN      A       217.237.149.142
www-proxy.t-ipnet.de.   12366   IN      A       217.237.149.205
www-proxy.t-ipnet.de.   12366   IN      A       217.237.150.51
www-proxy.t-ipnet.de.   12366   IN      A       217.237.150.115
www-proxy.t-ipnet.de.   12366   IN      A       217.237.150.188
www-proxy.t-ipnet.de.   12366   IN      A       217.237.150.205
www-proxy.t-ipnet.de.   12366   IN      A       217.237.151.51
www-proxy.t-ipnet.de.   12366   IN      A       217.237.151.115

;; Query time: 54 msec
;; SERVER: 217.237.151.205#53(217.237.151.205)
;; WHEN: Sun Aug 10 15:21:33 2008
;; MSG SIZE  rcvd: 246


c
-- 
  Was heißt hier Dogma, ich bin Underdogma!
[ What the hell do you mean dogma, I am underdogma. ]

_F R E E_  _V I D E O S_  -->>  http://www.blacktrash.org/underdogma/
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/