Skip to content
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

Unexpected errors may appear when using hostnames without a DNS domain #4272

Closed
TheWitness opened this issue May 19, 2021 · 3 comments
Closed
Labels
bug Undesired behaviour resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

If you are using a hostname and not a Fully Qualified Domain Name for one of your Cacti data collections, when you save the data collection the dns_get_record() exception is thrown.

To Reproduce

See the note above.

Expected behavior

Cacti should not throw these errors.

@TheWitness TheWitness added the bug Undesired behaviour label May 19, 2021
@TheWitness TheWitness added this to the 1.2.18 milestone May 19, 2021
TheWitness added a commit that referenced this issue May 19, 2021
 dns_get_record(): A temporary server error occurred
@TheWitness TheWitness added the resolved A fixed issue label May 19, 2021
@netniV
Copy link
Member

netniV commented May 19, 2021

We should see if we use the function elsewhere and update as appropriate

@TheWitness
Copy link
Member Author

I remember the settings plugin has a DNS resolver, but if memory serves me right, it's using RAW socket communication, which likely won't work with secure DNS. We should convert that function/library.

@TheWitness
Copy link
Member Author

@cigamit Should comment.

@netniV netniV closed this as completed Jun 9, 2021
@netniV netniV changed the title Cacti throws dns_get_record() errors in pollers.php under select circumstances Unexpected errors may appear when using hostnames without a DNS domain Jul 4, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants