Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    DNS fails to respond to type "ANY" queries for local names

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 608 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      tenortim
      last edited by

      Hi,
      I was trying to upgrade VMware VCSA6 to 6.5 and it kept failing saying the hostname (vcsa6.internal.splhi.com) wasn't resolvable.
      After digging down through the scripts, the bottom level Python code is calling "dig" as follows:

      dig @10.0.0.1 vcsa6.internal.splhi.com +short ANY
      

      That's failing on pfSense with no answer and noerror.
      This seems to be related to unbound and the "System Domain Local Zone Type".

      If I instead query

      dig @10.0.0.1 vcsa6.internal.splhi.com +short
      

      I get the correct response (10.0.0.188).

      Is this a bug/limitation in unbound? It seems it ought to handle queries of type "ANY" even for the local domain definition.
      I'm going to work around it by hacking the vcsa Python code to not add the "ANY" argument in the interim.

      1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator
        last edited by

        https://forum.pfsense.org/index.php?topic=102900.0

        Went over this quite some time ago.  Funny that is like 1 year exactly…

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

        1 Reply Last reply Reply Quote 0
        • T Offline
          tenortim
          last edited by

          Thank you, John!

          So, yes, this will break anybody trying to upgrade VMware VCSA if pfSense/unbound is their DNS server.
          Hacking dns_utils.py on the 6.5 VM and removing that addition of 'ANY' to the dig arguments allowed me to complete the upgrade.
          That's really pretty bad coding - they don't want or need 'ANY' (imagine if there were MX records!), they only want 'A' or 'AAAA', so I'll look log a bug with VMware.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.