You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much of our code uses the word "domain". This has multiple meanings, which are mixed up, and this is causing repeated ambiguity, confusion, and wasted time. We should fix this. The first step is figure out new names, and start using them in new or modified code or the database.
Is the domain field the domain entered by the user? What is maildomain? And why does maildomain (through DomainServersModel) have a domain field as well, which is not an FK? Is that the same as the other domains? etc.
There are a few different things referred to as "domain" (and sometimes, "hostname"):
A. The test target entered by the user or in the API request. Often a domain, but far from always. Any DNS name will do.
B. A name of a specific server for/against which we run a test. For example, the list of NS or MX records derived from A.
C. An IP of A or B.
There is some hierarchy: for NS RPKI we take A, find all NS (B), then find each IP (C), then check RPKI status. It's not perfectly uniform - for web we take A, find all IPs on that label (C), then run TLS against it. For mail TLS we take A, find all MX records (B), resolve those to IPs and run against one v4 and one v6 IP (C).
The word "domain" fits nowhere, so we can recognise old code by it still using that term. I still haven't come up with great terms especially for A and B though.
Any changes here would be reflected in our docs or labels, but probably not in the user frontend.
The text was updated successfully, but these errors were encountered:
Much of our code uses the word "domain". This has multiple meanings, which are mixed up, and this is causing repeated ambiguity, confusion, and wasted time. We should fix this. The first step is figure out new names, and start using them in new or modified code or the database.
See for example:
Internet.nl/checks/models.py
Lines 437 to 445 in a6870db
Is the domain field the domain entered by the user? What is maildomain? And why does maildomain (through DomainServersModel) have a domain field as well, which is not an FK? Is that the same as the other domains? etc.
There are a few different things referred to as "domain" (and sometimes, "hostname"):
There is some hierarchy: for NS RPKI we take A, find all NS (B), then find each IP (C), then check RPKI status. It's not perfectly uniform - for web we take A, find all IPs on that label (C), then run TLS against it. For mail TLS we take A, find all MX records (B), resolve those to IPs and run against one v4 and one v6 IP (C).
The word "domain" fits nowhere, so we can recognise old code by it still using that term. I still haven't come up with great terms especially for A and B though.
Any changes here would be reflected in our docs or labels, but probably not in the user frontend.
The text was updated successfully, but these errors were encountered: