-
Notifications
You must be signed in to change notification settings - Fork 25
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
Incorrect Name #50
Comments
I'm a little confused. Are you saying that |
Well its possible its not a bug the rfc says
However the authority section can contain more then just name server records e.g. dig mnasd.google.com will have an soa in the auth section. So, yes, nscount is actually the count of authority sections and is very badly named, double check with anand to make sure im not misinterpreting things but thats my understanding |
Alright. I'll have a chat with Philip and Anand once the RIPE meeting is over and we'll see what can be done about this. |
Alright, I just had a talk with Philip and he can't reproduce the problem. Do you have an example result that we can poke at and reproduce? |
Its not an error that can be reproduced. I just think that nameserver_count would be better renamed as authority_count. however its a really minor thing so feel free to close this |
Alright, so I just talked with Philip on this one, and I think we're gonig to keep the name as-is, if for no other reason that it best reflects the original name I did however just add a docstring to the nameserver_count for someone who might be poking around the source, and a bit more explanation in the documentation, to hopefully make things a little more obvious. |
there is a property of nameserver_count for nscount at
https://github.com/RIPE-NCC/ripe.atlas.sagan/blob/master/ripe/atlas/sagan/dns.py#L57-L60
however this is actually the authoritative section count
The text was updated successfully, but these errors were encountered: