Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some hosts seem to get 'blackholed' #1

Open
qbit opened this issue Jul 29, 2013 · 3 comments
Open

Some hosts seem to get 'blackholed' #1

qbit opened this issue Jul 29, 2013 · 3 comments

Comments

@qbit
Copy link

qbit commented Jul 29, 2013

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 ).

@marcopeereboom
Copy link

Are you by any chance using IPv6?

@qbit
Copy link
Author

qbit commented Aug 7, 2013

IPv4 only

@mgi
Copy link

mgi commented Jun 13, 2014

This issue still stand. FWIW, it seems that adsuck has trouble with CNAME but not with A.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants