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

Log Name Issues - FQDN Limitation #29

Open
jcdmacleod opened this issue Jan 4, 2019 · 4 comments
Open

Log Name Issues - FQDN Limitation #29

jcdmacleod opened this issue Jan 4, 2019 · 4 comments

Comments

@jcdmacleod
Copy link

DNSAuth doesn’t accept a file unless it is:

mon-01.pop.example.net_2018-12-29.05-59.dmp

This fails:

mon-01.pop.example.com_2018-12-29.05-59.dmp

I have not tried other tlds, but .com certainly fails. The files are just ignored, a rename causes them to be ingested instantly.

I will posted this under PDP too.

@mrjones-plip
Copy link
Contributor

@unix1 - when you're next in the DNSAuth code, can you confirm we actually only accept the .net TLD in the FQDN? We can triage this ticket accordingly after that.

@unix1
Copy link
Contributor

unix1 commented Jan 23, 2019

@Ths2-9Y-LqJt6 that is correct. The aggregate function has net_ hardcoded in file name parsing and it expects it there.

@mrjones-plip
Copy link
Contributor

@unix1 - great, thanks for the confirmation. If this is as easy of a fix as i think it is, please grab when you're next doing a cycle of work. No rush.

Conversely, if it's hard, or will have possible unknown reproductions, let's hold off until this can be the primary ticket you're working on.

@jcdmacleod - thanks for your patience while we work through this!

@unix1
Copy link
Contributor

unix1 commented Jan 25, 2019

@Ths2-9Y-LqJt6 this should be very simple indeed.

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

3 participants