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

Network diversity: Ignore anycast? #29

Open
kasgel opened this issue Apr 23, 2020 · 1 comment
Open

Network diversity: Ignore anycast? #29

kasgel opened this issue Apr 23, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@kasgel
Copy link
Contributor

kasgel commented Apr 23, 2020

Apparently many big providers use anycast on their nameserver IP addresses. This means that even though the IPs are all in the same ASN block, they are broadcasted from hundreds of locations all around the world.

This is not urgent, but we'd need some way to pass the check if anycast is being used. This will require some BGP querying, most likely.

@kasgel
Copy link
Contributor Author

kasgel commented Apr 23, 2020

Example

/main.py --domain google.com --ns ns1.google.com ns2.google.com ns3.google.com ns4.google.com
[✓] PASS Unique Nameservers
[✓] PASS Valid hostnames
[✓] PASS Nameserver reachability TCP&UDP
[✓] PASS answer authoritatively
[X] FAIL Network diversity
[✓] PASS Consistency between glue and authoritative data
[✓] PASS Consistency between delegation and zone
[✓] PASS Consistency between authoritative nameservers
[✓] PASS PASS - Glue records found, non-EDNS0 UDP DNS packet support verified
[✓] PASS Prohibited Networks
[✓] PASS Check nameservers not recursive
[✓] PASS Same source address as destination address

As said, this is an edge case that we can fix later.

@kasgel kasgel added the enhancement New feature or request label Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant