Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 627
    • Issues 627
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 116
    • Merge Requests 116
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #433

Closed
Open
Created Jul 24, 2018 by Vladimír Čunát@vcunat

`dig -4` just hangs if ::1 is default resolver

Summary

dig -4 just hangs if ::1 is default resolver

  • Bad: DiG 9.12.2 & 9.13.2 – hangs indefinitely.
  • Reasonable: DiG 9.10.3-P4 – it asks 127.0.0.1 instead.

Steps to reproduce

  • put nameserver ::1 (only) into /etc/resolv.conf.
  • run dig -4 isc.org

What is the expected correct behavior?

Behavior of 9.10 sounds okay to me. Failing with some understandable error is another option I see.

Edited Jul 24, 2018 by Vladimír Čunát
Assignee
Assign to
BIND 9.13.x
Milestone
BIND 9.13.x
Assign milestone
Time tracking
None
Due date
None