search

dns-violations / dnsflagday

DNS flag day
https://dnsflagday.net/
146 stars 40 forks source link

Client TCP checker #123

Closed jelu closed 5 years ago

jelu commented 5 years ago
jelu commented 5 years ago

@pspacek @Habbie @oerdnj and anyone else, need help with text for this now

jelu commented 5 years ago

Don't merge this until September, dev.dns-oarc.net will be reinstalled next week.

pspacek commented 5 years ago

I just realized one more thing: We probably need a mechanism to detect that test server is down, because it will inevitably happen (we have seen unintentional DDoS caused by major media picking up DNS flag day story etc.).

I think it would be useful to try this approach:

  1. download one web object from unique name which: a) is hosted on the same DNS server as checker b) can be resolved over UDP
  2. run test as coded now
  3. repeat the test and download another web object from same server as in step (1), but this time name of the object can contain information about pass/fail status

If steps 1 or 3 fail we can assume a problem with test infrastructure - in that case we should display "please come back later" message.

Does it sound reasonable to you?

jelu commented 5 years ago

@pspacek I've added a network check that must success in order for the test to start. Don't really see the point to do two network checks.

jelu commented 5 years ago

Thanks for the suggestion.

It's quite a difficult area because no tool can with certainty say who is your ISP or DNS operator because it will only see the last resolver and it may be someone else.

For example, plenty of ISP forwards their clients DNS to public resolvers.

And some ISP gives out public resolvers over DHCP.

We can point to other tools for the user to try and identify the problem but I think it shouldn't say that they will show you who runs your DNS.

jelu commented 5 years ago

@pspacek @Habbie can you briefly look over this change again so I can merge?

jelu commented 5 years ago

@ncartron @huguei @kidmin @songlinjian Hi all,

When this PR is merged we now have the client TCP checker in place. I added it to all other languages also but with English text so your translation wizardry is needed again, cheers!

huguei commented 5 years ago

@ncartron @huguei @kidmin @songlinjian Hi all,

When this PR is merged we now have the client TCP checker in place. I added it to all other languages also but with English text so your translation wizardry is needed again, cheers!

Sure! I'll wait for its approval on master branch.