Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 566
    • Issues 566
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #692
Closed
Open
Issue created Nov 14, 2018 by Michael McNally@McNally

"dig @localhost -b 127.0.0.1 ANY" hangs and triggers a crash

Summary

ISC Support Customer reports a minor problem (via support ticket #13746) with dig.

Steps to reproduce

He writes: If I run dig as follows (while not having anything listen on port 53 on "localhost"):

% dig @localhost -b 127.0.0.1 ANY
;; Connection to 127.0.0.1#53(127.0.0.1) for . failed: connection refused.

it hangs here, and if I then tries to terminate it, it crashes as follows:

^Cdighost.c:4161: INSIST(current_lookup == ((void*)0)) failed, back trace

According to his report

  • "@localhost"
  • "-b 127.0.0.1", and
  • (qtype is) "ANY"

are all required in order to trigger the behavior

What is the current bug behavior?

Hangs and then crashes with an INSIST assertion if sent an interrupt signal.

Edited Dec 04, 2018 by Ondřej Surý
Assignee
Assign to
Time tracking