- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Here's an example. I have a recurring test hitting Google DNS (https://dns.google/resolve?name=plesk.magicalproductions.net&type=A) and when the IP is incorrect I log it. This has happened consistently over the last hour at least 20 times. Here is one of the responses that failed, which I don't begin to understand:
{"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"plesk.magicalproductions.net.","type":1}],"Answer":[{"name":"plesk.magicalproductions.net.","type":1,"TTL":60,"data":"50.116.16.111"}],"Comment":"Response from ns2.magical.ws.(50.116.16.111)."}
You can see the response is the same as the name server IP that it pulled from. That IP is not related to us in any way. It's not ns2.magical.ws and it's not plesk.magicalproductions.net. So, where did Google choose to query that name server from? Even if a root server was giving back bad info about the authoritative owner of the domain, why would the response be incorrect? (and the same IP as the A record response, for that matter)
Here is a valid response: {"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"plesk.magicalproductions.net.","type":1}],"Answer":[{"name":"plesk.magicalproductions.net.","type":1,"TTL":3600,"data":"149.28.66.164"}],"Comment":"Response from ns3.magcal.ws.(205.251.198.208)."}
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa