Continuous DNS queries to 1.0.0.127.in-addr.arpa

Question

Continuous DNS queries to 1.0.0.127.in-addr.arpa

There are conflicting documents and discussions regarding the continual queries for this. Some say Bonjour. Some say mDNS is causing the issue. My Macbook Pro is generating hundreds of queries...where I see responses...to this address. Seems to me to be needless. I would hate to be a DNS provider for this.

At any rate, has anyone found a legitimate fix for this? I have been unable to find the legitimate fix that puts this issue to bed. It really is wasted traffic.

MacBook Pro (15-inch Early 2011), OS X Mountain Lion (10.8.2)

Posted on Oct 18, 2012 9:27 AM

Reply

Answer 1

Oct 18, 2012 4:56 PM in response to AnthonyKellar

1.0.0.127 is the reverse of 127.0.0.1 which is your local mac, so its querying itself

Reply

Answer 2

Oct 21, 2012 6:06 AM in response to Kevin Neal

Thank you for responding. I understand that 1.0.0.127 is the PTR record for 127.0.0.1. The question is, WHY is it trying to do this. Many support forums state that it is mDNS...some say Bonjour...I am interested in what is causing it and how to mitigate it.

Reply

Answer 3

wanker47

Level 1

0 points

Oct 24, 2012 7:08 PM in response to AnthonyKellar

I am having exactly the same issue. We have three Macs (Mac Pro, two MacBook Pros) and only the Mac Pro is doing it. It is hitting the DNS constantly with that same error. What is causing it and how do we make it stop?

I tried to Google the 1.0.0.127.in-addr-arpa line and all the responses are so packed with code I can't make heads or tails of them.

We are using Simple DNS Plus on Parallels on a Mac mini as our server. I would just like a simple explanation as to why the Mac Pro is behaving this way, and I would love simple instructions about how to fix it.

Reply

Answer 4

Oct 26, 2012 1:38 PM in response to wanker47

Mine quit doing it. I am on the same router...I haven't had my computer on for a few days. Did yours quit as well?

Reply

Answer 5

wanker47

Level 1

0 points

Oct 26, 2012 2:56 PM in response to AnthonyKellar

Nope, still banging away at that same query. No matter how I restart or shut the machine down.

Reply

Answer 6

Dec 27, 2012 9:09 AM in response to AnthonyKellar

In my particular case...for whatever reason...I ended up learning it was LogMeIn. How I found it was through a installable program known as "Private Eye" which is equivalent to a graphical DOS netstat -b command. I was able to see in real time what program was generating the traffic. In my case...it was LogMeIn. Removed it...program was gone. Recommend taking the same course of action on your system. It worked for me.