I have setup two PDNS servers running in the same host; pdns_server (the authoritative server) and pdns_recursor (a recursive server).
Here are the configurations for both PDNS servers settings:
launch=gpgsql loglevel=10 log-dns-queries=yes gpgsql-host=127.0.0.1 gpgsql-user=xxxxxx gpgsql-password=xxxxxxx gpgsql-dbname=xxxxxx recursor=127.0.0.1:5678
forward-zones=.=10.10.10.1;188.8.131.52 local-port=5678 trace=on
If you are abroad and missing your favourite TV programmes (BBC iPlayer or ITV Live Sport) which are only available free online at home, then you can configure browser to use SOCKS proxy with ssh tunnelling to stream video/audio data from your remote (anywhere in UK) to your browser (abroad) location.
See this on how to setup.
For me, I use VPN to gain ssh access.
Couple days ago, I was maintaining AppQoS appliances at customer site and noticed that one of our analysis tables from the HTTP module produced some strange results.
The table displays all the HTTP traffic in terms of media type (MIME) and transaction size in descending order. Read more
Again, I was diagnosing HTTP protocol traffic on my local network and I noticed something really strange that disturbed the HTTP protocol analyser module in AppQoS. A serious malformed response packet was found from www.assoc-amazon.com. The response headers were formed without probably ended with CR, only LF and the misspell of the ‘Connection’ header. Here shows an example of the response packet from the site using Wireshark/Ethereal. Read more
I noticed that my HTTP protocol analyser module of AppQoS reported some malformed HTTP packets. This was strange at first sight as the RFC for HTTP protocol is pretty well defined or this may be a bug in my module. So I inspected the captured packet with Wireshark/Ethereal. Thankfully, it wasn’t a bug in my module, it was actually the packet. Read more