Skip to content

Some hosts seem to get 'blackholed' #1

@qbit

Description

@qbit

Version 2.5.0 and 2.4.2 seem to suffer from this.

Basically nslookup / dig / adsuck seem to resolve fine, but other utilities like ping seem to not be able to.

It only seems to do this for "www.youtube.com" and "talkgadget.google.com"

My config looks like this:
adsuck_flags="-c /var/adsuck -f /viles/resolv.conf /files/hosts.small"

Tho I have been debugging with ( if I add in -d, I can see what seems to be a correct response ):

adsuck -v -D -c /var/adusck -f /files/resolv.conf /files/hosts.small"

I added some debug to line 401 of adsuck.c - and it isn't falling into the spoofquery function, and I have no regex stuff defined.

My router ( openbsd 5.2 ) is the machine running adsuck, and its resolver looks like:
nameserver 8.8.8.8
nameserver 8.8.4.4

The clients that are unable to resolve are OpenBSD current, ChromeOS ( beta ).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions