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.x86_64 from the Fedora repos
I can do manual lookups of the domain with "dig" and point it to their servers (dns0.getsurfed.com, dns1.getsurfed.com) but it fails for me if I go through my BIND installation. The named.run log contains lines like this: 16-Aug-2016 10:48:40.693 lame-servers: info: 17 unexpected RCODE resolving 'dryfire.com/NS/IN': 213.162.97.178#53 16-Aug-2016 10:48:40.749 lame-servers: info: 17 unexpected RCODE resolving 'dryfire.com/NS/IN': 213.162.97.177#53 A search for "17 unexpected RCODE" seems to indicate this might be caused by incompatibility between SIT/DNS cookies and older versions of NSD. Is this also what's happening in my case here?
;; ANSWER SECTION: dryfire.com. 21600 IN A 109.109.232.98 ;; ANSWER SECTION: dryfire.com. 21595 IN NS dns0.getsurfed.com. dryfire.com. 21595 IN NS dns1.getsurfed.com.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users