-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dns_query "E! Error in plugin" with IPv6. #3021
Comments
Any idea why we are getting connection refused to the ipv6 address when its working via ping6? I think you should be able to configure your system to prefer ipv4: https://serverfault.com/questions/93717/setting-ipv4-as-preferred-protocol-over-ipv6 |
I guess an ICMP packet is allowed, but port 53 for DNS is closed for the IPv6 protocol. As IPv6 enabled systems become more widespread, wouldnt an option within the plugin to choose a preferred transport be better than forcing users to globally prefer a legacy protocol? |
I agree it would be nice to be able to select it, but don't think github.com/miekg/dns currently supports it, can you open an issue with them? |
It looks as though https://github.com/miekg/exdns/blob/master/q/q.go it's already possible to choose IPv4 or IPv6 queries with the library you mentioned above :
|
Thanks, lets add an option called network like so: [[inputs.dns_query]]
domains = ["mjasion.pl"]
servers = ["8.8.8.8", "8.8.4.4"]
record_type = "A"
network = "udp4" |
Lovely, thanks Daniel! |
Directions
dns_query plugin needs a way of forcing IPv4 usage only.
Bug report
Relevant telegraf.conf:
dns_query plugin enabled :
System info:
Telegraf version from github as of today (15July2017).
Ubuntu 17.04
Steps to reproduce:
Expected behavior:
IPv6 link local address not used for DNS query.
Actual behavior:
DNS query is performed to local 'gateway' (systemd uses this name to refer to the local configured gateway) using IPv4, and not using IPv6 link local addresses.
Additional info:
IPv6 enabled on interface :
xxx
The text was updated successfully, but these errors were encountered: