Skip to main content
NetApp Knowledge Base

After upgrading BIND DNS server, BIND returns NXDOMAIN to clients

  1. Last updated
  2. Save as PDF
Views:
80
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP onbox DNS load balancing
  • BIND 

Issue

  • After upgrading BIND DNS server, BIND returns NXDOMAIN to clients querying for LIF hostnames that are in a DNS zone that is load-balanced by ONTAP 
  • BIND error log contains 
    • 29-Jul-2024 09:55:08.854 resolver: info: loop detected resolving 'FQDN/A'
  • Clients are unable to resolve ONTAP LIFs 
    • > host hostname
Host hostname not found: 3(NXDOMAIN)
    • > nslookup hostname.zone.domain
Server:         dns_server_name
Address:        dns_server_ip
** server can't find hostname.zone.domain: NXDOMAIN

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.