On 09/08/2019 21.28, Per Jessen wrote:
Carlos E. R. wrote:
On 09/08/2019 19.13, James Knott wrote:
On 2019-08-09 01:02 PM, Carlos E.R. wrote:
Not saying you said "that" :-)
I'm grasping at straws here. Hopping that some old bug of behaviour
in some software worked differently based on those addresses. So I
tried, just in case...
Those addresses are not the issue. With DNS, there's no difference
between them and any other routeable address. Don't forget, the DNS
only returns addresses, that is strings of digits. It makes no
difference what those digits are. What you are implying is that on
IPv4, a DNS server would choke on RFC1918 addresses.
As I said, I'm grasping on straws.
The program that fails is "ping -6 Isengard", claims no name found. If
I stop nscd it works. But "ping -6 google.com" works (at least it
finds the name).
So something is wrong with your DNS setup. IIRC, you're also
using /etc/hosts - clear out anything to do with Isengard, if anything.
That was it!
But this has a new problem: the localhost. This machine is called
"Telcontar", so obviously hosts has an entry for it:
192.168.1.14 Telcontar.valinor Telcontar
fc00::14 Telcontar6.valinor Telcontar6
I have to remove both for ping -6 to work, but if I do, other things
will stop working - I don't remember which, perhaps postfix.
On the other hand, on Isengard /etc/hosts has those entries, and they
work - with dnsmasq, which reads that file precisely.
Cheers / Saludos,
Carlos E. R.
(from 15.0 x86_64 at Telcontar)