dev.home

Comments

4 comments

  • Avatar
    rotblitz

    This dev.home is an internal network name of your network, and some networking application within your network tries to resolve this name, again and again.  The bad thing is that these DNS queries are sent out to OpenDNS which is in no way able to resolve your internal names, and therefore your application doesn't stop the trials.  The solution is to prevent the application from raising these queries, maybe by changing its configuration, or to stop sending these queries from going out to OpenDNS.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    This dev.home is clearly an internal network name expected to exist within your network.  The bad thing is that your router or another device sends out these internal name resolution attempts to an external DNS service, i.e. to OpenDNS.  Such internal queries should not be sent out, because external DNS services are unable to resolve internal network names.

    There is a networking application within your network which queries this network name again and again, because it doesn't get a result beside NXDOMAIN.  Try to identify this network application and make it stop raising these DNS queries.  You could also try to configure your router to not send out queries for the home TLD. 

    You probably have configured the OpenDNS resolver addresses on the LAN/DHCP side which impacts or breaks local name resolution.  If you can, you better configure on the WAN side of the router.

    0
    Comment actions Permalink
  • Avatar
    beaton3344

    I've blocked it at router I can't pin point where it's coming from. Maybe Asus router itself.

    I have

    dev
    dev.home
    dev is blocked 80,000 times. A day. dev.home is around 60,000 times....
    Are killing it not sure what's causing it have to start unplugging and waiting to see what it is. Only have 2 device connected most the time. Maybe chromecast.

    Strange thing is opendns allows me to block dev.. But not dev.home. Which I have both blocked router side now... I run a network of about 30 computers and don't even come close to 10000 requests. But my little home network is insane. Strange.

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    "Strange thing is opendns allows me to block dev.. But not dev.home."

    Well, dev is interpreted as a TLD, like com or org.  This is why you can add it to the blacklist or whitelist.  Whereas home as TLD may be exempted from being able to be added.  This is a TLD used in private environments only.

    Also, it does not make sense to block or allow such internal network names at OpenDNS.  As long as the queries are sent to OpenDNS, they will appear in your stats.  OpenDNS reports everything about your DNS traffic, no matter if blocked or not.  To stop it from appearing in your stats you eliminate it at the source or do not send it to OpenDNS, as I said already.

    Also, blocking domains at OpenDNS does not mean that such DNS queries are not processed and responded to, rather to the contrary.  They are very well responded to with an OpenDNS own IPv4 and/or IPv6 address.  And therefore they appear in the stats, of course.

    0
    Comment actions Permalink

Please sign in to leave a comment.