David C. Rankin wrote:
I don't handle ipv6 at all. In my named.conf I have:
listen-on-v6 { none; };
But regardless, I end up with a slew of messages, e.g.
error (network unreachable) resolving 'gateway.discord.gg/A/IN': 2001:630:0:9::14#53
If your name server has IPv6, it will still use it for resolving, your config above will only stop it accepting queries over IPv6. I see gateway.discord.gg: janeway:~ # host gateway.discord.gg gateway.discord.gg has address 162.159.134.234 gateway.discord.gg has address 162.159.135.234 gateway.discord.gg has address 162.159.136.234 gateway.discord.gg has address 162.159.130.234 gateway.discord.gg has address 162.159.133.234 janeway:~ # host 2001:630:0:9::14 4.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.0.0.0.0.0.0.0.0.3.6.0.1.0.0.2.ip6.arpa domain name pointer ns0.ja.net.
success resolving 'gateway.discord.gg/A' (in 'discord.gg'?) after reducing the advertised EDNS UDP packet size to 512 octets
Possibly a firewall issue - firewall only accepting DNS packets sise 512? If you google that, there is plenty of hits, e.g. https://kb.isc.org/docs/aa-00708 (I don't know if that article is useful).
I don't understand why I'm seeing the attempts to resolve the ipv6 address to begin with?
If the domain you're doing a lookup on has nameservers with IPv6 addresses, and your name server too, they will be used. That is perfectly normal.
I don't recall seeing much of this before a month or two ago -- so I don't know if it is at all related to the DNS over http growing pains or what...
fwiw, I'm running bind 9.7.4-P1, and I'm not seeing those messages. I guess a newer version might show them. AFAIU, EDNS is about increasing the max bind packet size - are you implementing DNSSEC ? That is the only place I have come across EDNS. -- Per Jessen, Zürich (-0.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org