Skip to content

DNS Check failed #46

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

Open
ETMARCOF opened this issue Feb 9, 2022 · 1 comment
Open

DNS Check failed #46

ETMARCOF opened this issue Feb 9, 2022 · 1 comment

Comments

@ETMARCOF
Copy link

ETMARCOF commented Feb 9, 2022

I have standard cluster 4.0.2f and i run last version available of hypercheck and DNS check is failing. But if i SSH to every CVM's I'm able to do execute dig for every node for example dig esxi01 @ 10.21.2.230 or dig scvm01 @10.21.1.230 and so on. Why is only executing @10.21.216.230 and only testing one DNS server?

2022-02-07 05:34:13 - HX_TOOL - INFO - Executing command: stcli services dns show
2022-02-07 05:34:15 - HX_TOOL - INFO - ************************ CMD OUTPUT ************************
2022-02-07 05:34:15 - HX_TOOL - INFO - ----------------------------------------
2022-02-07 05:34:15 - HX_TOOL - INFO - 10.21.1.230
2022-02-07 05:34:15 - HX_TOOL - INFO - ----------------------------------------
2022-02-07 05:34:15 - HX_TOOL - INFO - 10.21.2.230
2022-02-07 05:34:15 - HX_TOOL - INFO - ----------------------------------------
2022-02-07 05:34:15 - HX_TOOL - INFO - *************************************************************
2022-02-07 05:34:15 - HX_TOOL - INFO - DNS IP Address: 10.21.1.230
2022-02-07 05:34:15 - HX_TOOL - INFO - DNS IP Address: 10.21.2.230
2022-02-07 05:34:15 - HX_TOOL - INFO - #############################################################
2022-02-07 05:34:15 - HX_TOOL - INFO - Executing command: dig @10.21.216.230
2022-02-07 05:34:27 - HX_TOOL - INFO - ************************ CMD OUTPUT ************************
2022-02-07 05:34:27 - HX_TOOL - INFO -
2022-02-07 05:34:27 - HX_TOOL - INFO - ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.21.2.230
2022-02-07 05:34:27 - HX_TOOL - INFO - ; (1 server found)
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; global options: +cmd
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; Got answer:
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 64597
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
2022-02-07 05:34:27 - HX_TOOL - INFO -
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; OPT PSEUDOSECTION:
2022-02-07 05:34:27 - HX_TOOL - INFO - ; EDNS: version: 0, flags:; udp: 4000
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; QUESTION SECTION:
2022-02-07 05:34:27 - HX_TOOL - INFO - ;. IN NS
2022-02-07 05:34:27 - HX_TOOL - INFO -
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; Query time: 1534 msec
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; SERVER: 10.21.2.230#53(10.21.2.230)
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; WHEN: Mon Feb 07 17:34:27 WET 2022
2022-02-07 05:34:27 - HX_TOOL - INFO - ;; MSG SIZE rcvd: 28
2022-02-07 05:34:27 - HX_TOOL - INFO -

@doomi
Copy link

doomi commented Sep 22, 2022

I can confirm the issue.
the check does a simple
dig @"dns server"
which in our environment with hardened DNS servers will result in a "status: REFUSED"

the check should explicitly test for an A or PTR record, i.e.
dig @"dns server" -x "node-ip"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants