Hi Robert, thanks for your reply once again. I did a lookup both using the host commando (both with -t A and -t AAAA options) and you can see that my host (wich is running bind recursively for my network using root nameservers) returns the lack of the A record for my probe. I then used dig (@localhost) with same result. Right now trying from on-line services DNS returns error both fro AAAA and A records. Once I will go back home I will check again against different nameservers. Any particular one recommanded? Also I would seggest updating the news reflecting that now the probes have both A and AAAA records, it still shows as future implementation there. Cheers Fabio Sent from my iPad On 14/feb/2012, at 12:56, Robert Kisteleki <robert@ripe.net> wrote:
Hi,
On 2012.02.14. 12:52, Software Registrations wrote:
Hello Robert,
thanks for your reply but I do not understand your point about changing the UI and having A and AAAA records.
I do not have A and AAAA records for my probe only AAAA.
You do. At least, we generate them and I can see them from two different networks using simple DNS queries.
Are you saying that the probe now supports both? What firmware release are you referring to?
There's not probe firmware change needed, this is happening purely on our side.
Regards, Robert
Regards
Fabio
Sent from my iPad