You are not logged in.
I have been using squid for the last couple of days because of a poor connection at the dsl. I also decided that possibly pdnsd would be a good measure to also speed things up a little. But when using pdnsd as a DNS server, squid doesn't always use the DNS records that pdnsd provides and results in messages from squid
ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL: http://www.weather.com/news/weather-tornado/tornado-torcon-index
Unable to determine IP address from host name www.weather.com
The DNS server returned:
No DNS records
This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
Your cache administrator is webmaster.
Doing a dig will sometimes return that the DNS server was pdnsd and other times it pulls it from the primary DNS server in the configuration file.
Last edited by nomorewindows (2013-12-17 20:58:48)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Just to clarify, I am using pdnsd and squid on the same machine. It looks like adding
nameserver localhost
to /etc/resolv.conf may have allowed it to use the entries from pdnsd. It looks like I am getting more responses on squid that involve the IP address of the site, but the internet connection was down instead of it having to say that it couldn't look up the DNS even though it was available in the pdnsd cache.
Last edited by nomorewindows (2013-12-15 13:30:11)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I've got the same setup as you by the sound of it. My /etc/resolv.conf contains:
nameserver 127.0.0.1
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
There is an option in there to use 127.0.0.1, but if you want to make it available to the rest of the network then it tells you to put eth0. Maybe I need 127.0.0.1, eth0 to make it work?
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I haven't tried this but I'm guessing the format will be:
server_ip = 127.0.0.1;
server_ip = eth0;
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I haven't tried this but I'm guessing the format will be:
server_ip = 127.0.0.1; server_ip = eth0;
I'm thinking it would be
server_ip= 127.0.0.1,eth0;
but the documentation makes it seem like you are replacing 127.0.0.1 with eth0.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Here's what the man page for pdnsd.conf says about "server_ip=":
Presently you can only specify one address here; if you want pdnsd to listen on multiple interfaces but not all you will have to specify server_ip=any and use firewall rules to restrict access
Last edited by loafer (2013-12-17 20:37:31)
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Here's what the man page for pdnsd.conf says about "server_ip=":
man pdnsd.conf wrote:Presently you can only specify one address here; if you want pdnsd to listen on multiple interfaces but not all you will have to specify server_ip=any and use firewall rules to restrict access
Doing a nmap localhost shows the port 53 to be closed, so maybe it doesn't use it at all. But doing a nmap from a proxy client shows it to be open. But there's another trick. We need to change the ip address in /etc/resolv.conf to be the ip addr of our proxy server. Then when we do that, it shows open. So nameserver localhost won't work. It has to be the ip address of the proxy server, although this seems redundant. Real confusion would result if you had multiple dns servers and were trying to configure it for redundancy. But the squid part of it can be configured on a heirarchy structure and for certain domains. I suspicioned about the nameserver localhost not working, so now I think with a little smarts, we have it solved.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline