-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ben Halicki wrote:
| Walter Hofmann <(E-Mail Removed)> wrote in message
news:<(E-Mail Removed)>...
|
|>Jerry Smiley <(E-Mail Removed)> schrieb:
|>
|>>Walter Hofmann wrote:
|>>
|>>
|>>>Jerry Smiley <(E-Mail Removed)> schrieb:
|>>>
|>>>>Walter Hofmann wrote:
|>>>>
|>>>>>Hi,
|>>>>>
|>>>>>it seems that my Debain unstable computer queries for an AAAA
record
|>>>>>(ie. ipv6), waits for a timeout, and only then queries for the A
|>>>>>record (ie. ipv4) address whenever it needs to resolve a name
in DNS.
|>>>>>
|>>>>>Of course every network application is delayed by this. How
can I switch
|>>>>>this off?
|>>>>>
|>>>>>I read the man page for resolv.conf, and it says that this is
switched
|>>>>>_on_ by adding the line "options inet6" to /etc/resolv.conf. But I
|>>>>>checked and this line is not there. So why is it doing ipv6
queries?
|>>>>>
|>>>>>Walter
|>>>>
|>>>>Try adding in the /etc/modules.conf
|>>>>
|>>>> alias net-pf-10 off
|>>>> alias ipv6 off
|>>>
|>>>This didn't work. I added these lines and also rebooted to make sure
|>>>that the ipv6 module was not loaded, but nothing changed.
|>>>
|>>>Any other help?
|>>>
|>>>Walter
|>>
|>> If you want to disable ipv6 then you can put the following line
in either
|>>/etc/modules.conf for 2.4 kernel or /etc/modprobe.conf for 2.6
kernel.
|>>
|>> alias net-pf-10 off
|>
|>This didn't work. I added these lines and also rebooted to make sure
|>that the ipv6 module was not loaded, but nothing changed.
|>
|>Both telnet and ssh still look for an AAAA record first.
|>
|>Any other help?
|>
|>Walter
|
|
| Hi Walter,
|
| I'm stuck in a similar situation, where telnet and ssh are both
| resolving ipv6 addresses before ipv4.. very slow! Just wondering if
| you managed to find a solution?
Stupid question time, but why is it slow, and why is it waiting for
a timeout?
In any case where the IPv6 record exists, or doesn't exist, the
response should be no different than any other DNS lookup, and the
result should also be cached (if only briefly for NXDOMAIN).
Anything other than this suggests other configuration problems.
Typically if it is slow, it is because the first query caches the
relevant nameserver data, and the subsequent query is then very
quick because all the cached data is current.
The issue with SSH is I believe well documented, some versions are
built to try IPv6 addresses first. I vaguely recall it is a compile
time switch which can be overridden with a run time option, but it
is very well documented.
The confusion here seems to be between trying lookups for IPv6 data
(AAAA) and actually using IPv6 to perform lookups. In most cases the
resolvers (and DNS servers) will use IPv4 to perform the lookup for
AAAA, unless you have configured IPv6 as an available protocol (in
which case you probably want the AAAA lookup anyway).
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Debian -
http://enigmail.mozdev.org
iD8DBQFBo3vSGFXfHI9FVgYRAhv2AJ9MMEH80FYvchIaFl7rja RBIUc2LgCg1zmN
XZT/wFpUmSvIEqaQ04QiM+s=
=aeWA
-----END PGP SIGNATURE-----