On 25/01/13 17:38, Per Jessen wrote:
James Knott wrote:
Per Jessen wrote:
Too long ago to investigate, but that sounds pretty dodgy. If your system was attempting DNS lookup via IPv6, it would mean it had an IPv6 address listed in /etc/resolv.conf.
[snip]
So, IPv6 addresses may be present on a DNS request, whether via IPv4 or IPv6. The problem is why is the IPv6 address being tried, when there's no IPv6 route.
So back to what I said - if the system was attempting DNS lookup _via_ IPv6, it would mean it had an IPv6 address listed in /etc/resolv.conf.
Any reasonably up-to-date application would today be doing a DNS lookup looking for both IPv4 and IPv6 addresses, but the only reason for attempting a lookup via IPv6, would be if the resolver(s) were IPv6-only. I don't know how the resolver handles the situation where the resolver addresses has no valid route.
I've now found a problem following disabling of IPv6. I have a script that sends a report to root on completion. It now says sendmail: fatal: config variable inet_interfaces: host not found: localhost In YaST, my Host Configuration has one entry for localhost ::1 localhost ipv6-localhost ipv6-loopback Should I replace this with 127.0.0.1 localhost localhost or can I add that line to the file? Bob -- Bob Williams System: Linux 3.4.11-2.16-desktop Distro: openSUSE 12.2 (x86_64) with KDE Development Platform: 4.9.5 "release 3" Uptime: 06:00am up 1 day 12:21, 3 users, load average: 0.02, 0.10, 0.56 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org