Re: Problem looking up domain dryfire.com

2016-08-18 Thread Mark Andrews
In message <9f949ee6-6386-c986-698e-e4a46e6cf...@thelounge.net>, Reindl Harald writes: > Am 16.08.2016 um 11:04 schrieb Eivind Olsen: > > I'm seeing some odd problems where BIND (9.10.4-P2) has issues resolving > > getsurfed.com. This is when using the "510 Software Group" BIND 9.10 for > > RHEL/

Re: Problem looking up domain dryfire.com

2016-08-18 Thread Reindl Harald
Am 16.08.2016 um 11:04 schrieb Eivind Olsen: I'm seeing some odd problems where BIND (9.10.4-P2) has issues resolving getsurfed.com. This is when using the "510 Software Group" BIND 9.10 for RHEL/CentOS/Fedora. why do you use a 3rd party package? no problem here with bind-9.10.4-1.P2.fc24.x8

Re: Problem looking up domain dryfire.com

2016-08-16 Thread Mark Andrews
The nameservers are broken. They send back rcode 17 (which is yet to be assigned) when they see a query with a EDNS option present rather than ignore the option as required by RFC 6891. They also send back RCODE 17 rather than BADVERS (16) when send a EDNS(1) query. The servers also don't answ

Re: Problem looking up domain dryfire.com

2016-08-16 Thread Mukund Sivaraman
On Tue, Aug 16, 2016 at 11:04:14AM +0200, Eivind Olsen wrote: > Hello. > > I'm seeing some odd problems where BIND (9.10.4-P2) has issues resolving > getsurfed.com. This is when using the "510 Software Group" BIND 9.10 for > RHEL/CentOS/Fedora. > > I can do manual lookups of the domain with "dig"

Problem looking up domain dryfire.com

2016-08-16 Thread Eivind Olsen
Hello. I'm seeing some odd problems where BIND (9.10.4-P2) has issues resolving getsurfed.com. This is when using the "510 Software Group" BIND 9.10 for RHEL/CentOS/Fedora. I can do manual lookups of the domain with "dig" and point it to their servers (dns0.getsurfed.com, dns1.getsurfed.com)