Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 632
    • Issues 632
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #3407
Closed
Open
Issue created Jun 15, 2022 by Peter Much@PMc

dig/host do not fail over to other name servers in /etc/resolv.conf upon UDP timeout

Summary

When a query to the first nameserver in /etc/resolv.conf fails, /usr/local/bin/host terminates silently.

BIND version used

Only bind-tools of this version: package version is 9.18.3

Steps to reproduce

Connecting the first NS in resolv.conf returns EHOSTUNREACH or EPERM (ECONNREFUSED does not create the problem).

What is the current bug behavior?

no output from "host whatever"

What is the expected correct behavior?

The second nameserver from resolv.conf should be asked

Correct behaviour is present in 9.16.29, and also when invoking "host -T"

Edited Jun 15, 2022 by Michał Kępień
Assignee
Assign to
Time tracking