|
Size: 846
Comment:
|
Size: 895
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| This text describes the way gnode request for MX in adna. | This text describes how the MX DNS query are resolved by ANDNA. |
| Line 12: | Line 12: |
| When you need to know the MX of a domain you contact the domain main node via dsn query, the node. using the dns_wrapper, give you it's MX. | When you need to know the MX of a domain, you resolve the domain itself via a normal hostname resolution, then you contact the gained ip, which is the host itself and you ask its MX. |
| Line 14: | Line 14: |
| This requires small changes in the code: it is just necessary that the dsn_wrapper contact the domain main node instead the adna server and the node will reply with the MX field. | This requires small changes in the code: it is just necessary that the dsn_wrapper, after having resolved the main domain, contacts the host with and the node will reply with the MX field. |
| Line 16: | Line 16: |
| Easy and straight, that permit the ADNA server to be free from all the request but the name resolving | Easy and straight, that permits the hash_gnodes to understand only name resolving requests. |
NTK_RFC 0004
Subject: Mail Exchange request
This text describes how the MX DNS query are resolved by ANDNA. It will be included in the final documentation, so feel free to correct it. But if you want to change the system here described, please contact us first.
In DNS server the MX field is provided by the DNS itself, to leave ADNA more flexible the MX in Ntk is provided by the host itself. When you need to know the MX of a domain, you resolve the domain itself via a normal hostname resolution, then you contact the gained ip, which is the host itself and you ask its MX.
This requires small changes in the code: it is just necessary that the dsn_wrapper, after having resolved the main domain, contacts the host with and the node will reply with the MX field.
Easy and straight, that permits the hash_gnodes to understand only name resolving requests.