Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • linuxmce linuxmce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 255
    • Issues 255
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linuxmcelinuxmce
  • linuxmcelinuxmce
  • Issues
  • #1606
Closed
Open
Issue created Nov 10, 2012 by anonymous@anonymous

dhcp uses 127.0.0.1 as a nameserver on external nic and passes it to clients

When I enable dhcp on the external interface (eth0 in my case) I get 127.0.0.1 as the first nameserver and my client pc also get that as the nameserver. The lease entry in /var/lib/dhcp3/dhclient.eth0.leases on the core gets an entry like:

option domain-name-servers 127.0.0.1,193.8.10.10,193.8.1.1;

maybe it needs to filter out the invalid 127.0.0.1 address? When I manually remove the 127.0.0.1 entry from resolv.conf it works properly.

Assignee
Assign to
Time tracking