I have Verizon FIOS - which doesn't do IPv6 :( So I've turned off
IPv6 on my Win10 machine ('ipconfig /all' now doesn't say anything
about IPv6) but I still get a *lot* of network unreachable msgs in the
log - eg:
01-Sep-2017 17:23:13.721 lame-servers: info: error (network
unreachable) resolving 'ns1.p16.dynect.net/A/IN': 2001:502:7094::30#53
01-Sep-2017 17:23:13.721 lame-servers: info: error (network
unreachable) resolving 'ns1.p16.dynect.net/A/IN': 2001:500:d937::30#53
ftp://ftp.isc.org/isc/bind9/9.9.11/doc/arm/man.named.html
Says to use the "-4" option to have named only use IPv4, but how to
specify that option?
If I run services.msc & double click on "ISC BIND" it opens up a
window that has 'start parameters' greyed out, so I can't add it
there.
I tried using regedit to add " -4" to the program name
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\named\ImagePath)
so the path to the executable for ISC BIND was 'c:\program
files\bind9\named.exe -4'
but I still got all those log messages.
How to tell named not to use ipv6?
& failing that, how to not log all those 'error (network unreachable)
resolving [ipv6 address]' messages while still logging everything
else?
Thanks,
Lee
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
