Porblems with Lycos.com host lookup.

Hi all, We are seeing odd behaviour when attempting to look up the following url from a range of Redhat servers. bigmail1.lycosmail.lycos.com should resolve to 209.202.248.251 but we see the following. [...@ ~]$ host bigmail1.lycosmail.lycos.com Host bigmail1.lycosmail.lycos.com

9.7.0a2 - deny-answer-addresses

'uname -rms' Linux 2.6.30.4-spott-gecd13d4 i686 '/l/sbin/named -V' BIND 9.7.0a2 built with '--prefix=/opt/bind/9.7.0a2' '--with-openssl=yes' '--disable-linux-caps' '--sysconfdir=/usr/local/etc' '--localstatedir=/var' 'CFLAGS=-O' I want to disallow rebinding-attacks in a caching resolver. In the

Re: 9.7.0a2 - deny-answer-addresses

On Fri, 21 Aug 2009, clemens fischer wrote: BIND 9.7.0a2 built with '--prefix=/opt/bind/9.7.0a2' '--with-openssl=yes' '--disable-linux-caps' '--sysconfdir=/usr/local/etc' '--localstatedir=/var' 'CFLAGS=-O' Thank you very much for testing the alpha release. deny-answer-addresses {

Re: 9.7.0a2 - deny-answer-addresses

Jeremy C. Reed wrote: Thank you very much for testing the alpha release. My pleasure! I had a workaround resulting in dns-rebind protection in my pdnsd[1] resolver, but pdnsd doesn't support dnssec and a few other features. [1] http://www.phys.uu.nl/~rombouts/pdnsd.html

Re: Format of 'dig -k' TSIG key file?

After some experimenting, here is the whole answer, hinted at by one response on this mailing list. On Thu, Jul 30, 2009 at 05:40:54PM -0400, Joseph S D Yao wrote: ... In dig(1), the '-k' option is said to require a TSIG key file as an option. I have a TSIG file with a comment header and the

Re: Porblems with Lycos.com host lookup.

In message 65afb5970908210654s56231ce1g461a251fe9afa...@mail.gmail.com, Matt writes: Hi all, We are seeing odd behaviour when attempting to look up the following url from a range of Redhat servers. The lycos.com servers are returning malformed responses. The NS RRset should not be for