Wpad.localdomain

hi
I’m continually having this conection in my log dns and he can disable wpad.localdomain I don’t use the proxy.
ty

In the past did you follow the wpad wiki documentation for using DNS for distributing the wpad info?

If yes then you would have file/directory entries such as

/etc/httpd/conf/vhosts.d/wpad.conf
/srv/web/ipfire/wpad

If those exist then you need to remove the files and links that would have been created by the following wiki directions
https://www.ipfire.org/docs/configuration/network/proxy/extend/wpad#vhost-for-apache

If those files/directories don’t exist then I don’t know where wpad.localdomain will have been created but it is not done by IPFire itself as that string is not found in the IPFire git repo.

1 Like

You cannot disable this dns resolve because it is done by the browsers on your clients to autodetect a proxy.

3 Likes

hi
That’s what I’ve seen, but why is it only happening with ipfire?
with other router and other I’m not see wpad.localdomain

Are you sure that the other router log dns failures?

2 Likes

I used to see it in ClearOS and, to get round it, just added an empty wpad.dat file.