I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself. /Simon 14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.734 client 192.168.1.48#40389: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.737 client 192.168.1.48#44142: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.740 client 192.168.1.48#59254: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.742 client 192.168.1.48#56991: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.745 client 192.168.1.48#59319: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:36.769 client 192.168.1.48#55435: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 08:55:56.001 client 192.168.1.48#49742: query: caldwell.atlas.ripe.net IN AAAA + (192.168.1.47) 14-Mar-2012 08:55:56.146 client 192.168.1.48#34211: query: caldwell.atlas.ripe.net IN A + (192.168.1.47) 14-Mar-2012 08:58:38.199 client 192.168.1.48#42327: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.202 client 192.168.1.48#53097: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.204 client 192.168.1.48#54101: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.207 client 192.168.1.48#52439: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.210 client 192.168.1.48#37104: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.212 client 192.168.1.48#59275: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 08:58:38.216 client 192.168.1.48#49299: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 09:01:28.778 client 192.168.1.48#58887: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.781 client 192.168.1.48#52689: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.784 client 192.168.1.48#40593: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.787 client 192.168.1.48#51568: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.790 client 192.168.1.48#36493: query: ghostgraz.com IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.792 client 192.168.1.48#33057: query: ghostgraz.com.lan IN AAAA + (192.168.1.47) 14-Mar-2012 09:01:28.796 client 192.168.1.48#49588: query: ghostgraz.com IN A + (192.168.1.47) 14-Mar-2012 09:01:34.977 client 192.168.1.48#35392: query: www.ripe.net IN A + (192.168.1.47)
On 3/14/12 10:05 , Simon Josefsson wrote:
I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself.
/Simon
14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47)
That seems to be a UDM that scheduled on your probe. Unfortunately, at the moment probes host don't have a means to find out what measurements are running on their probes.
On 2012.03.14. 10:32, Philip Homburg wrote:
On 3/14/12 10:05 , Simon Josefsson wrote:
I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself.
/Simon
14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47)
That seems to be a UDM that scheduled on your probe. Unfortunately, at the moment probes host don't have a means to find out what measurements are running on their probes.
On a positive note: since this is interesting and useful information, we'll show the list of the ongoing measurements on for each probe on the "probe status" page. This is most likely going to happen when we go live with UDMs. Regards, Robert
Robert Kisteleki <robert@ripe.net> writes:
On 2012.03.14. 10:32, Philip Homburg wrote:
On 3/14/12 10:05 , Simon Josefsson wrote:
I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself.
/Simon
14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47)
That seems to be a UDM that scheduled on your probe. Unfortunately, at the moment probes host don't have a means to find out what measurements are running on their probes.
On a positive note: since this is interesting and useful information, we'll show the list of the ongoing measurements on for each probe on the "probe status" page. This is most likely going to happen when we go live with UDMs.
Thanks for feedback -- I was mostly concerned that the probe might had been hijacked. /Simon
Hi Philipp, could I - and maybe others, too - be enlighted what "UDM" stands for, please? The usual acronym finders don't help me here. Thanks, -C. On 14.03.2012 10:32, Philip Homburg wrote:
On 3/14/12 10:05 , Simon Josefsson wrote:
I was debugging my local DNS resolver when I noticed peculiar lookups from the Atlas probe for 'ghostgraz.com'. It seems to happen once in a while. Does anyone have any idea what this is? I don't see it in the list of built-in measurements, and I don't recall configuring anything related to that site myself.
/Simon
14-Mar-2012 08:55:36.732 client 192.168.1.48#58740: query: ghostgraz.com IN AAAA + (192.168.1.47)
That seems to be a UDM that scheduled on your probe. Unfortunately, at the moment probes host don't have a means to find out what measurements are running on their probes.
On 3/14/12 10:46 , Carsten Schiefner wrote:
could I - and maybe others, too - be enlighted what "UDM" stands for, please? The usual acronym finders don't help me here.
Google 'atlas udm' :-) It stands for User Defined Measurements
Thanks, Philipp. On 14.03.2012 11:25, Philip Homburg wrote:
On 3/14/12 10:46 , Carsten Schiefner wrote:
could I - and maybe others, too - be enlighted what "UDM" stands for, please? The usual acronym finders don't help me here.
Google 'atlas udm' :-)
It stands for User Defined Measurements
participants (4)
-
Carsten Schiefner -
Philip Homburg -
Robert Kisteleki -
Simon Josefsson