Unsolved
This post is more than 5 years old
68 Posts
0
12005
October 10th, 2012 10:00
anyone else have a weird resolv.conf?
Here's my weird resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search whereiwork.com
#
# m
# mmmm m m mmmm mmmm mmm mm#mm
# #" "# # # #" "# #" "# #" # #
# # # # # # # # # #"""" #
# ##m#" "mm"# ##m#" ##m#" "#mm" "mm
# # # #
# " " "
# This file is managed by puppet. Do not make local changes.
domain buildd
nameserver 10.122.37.1
So, the first two command lines make sense, sort of. It's using some resloveconf daemon to do DNS lookups, but how do I get rid of this puppet code, why would it hardcode my domain to "buildd" and set a nameserver on a 10.x network that I obviously don't have access to?
I assume this is something left over from Dell's initial configuration?
No Events found!
cumptrnrd
3 Posts
0
December 1st, 2012 10:00
I noticed I had the same thing in my resolv.conf. I agree, this looks like something left over from some build process. The puppet agent was not running after a fresh install, so I don't think it was expected that we would be managing our machines with puppet.
Normally, NetworkManager manages these things, but I think it was explicitly disabled because NetworkManager does not support bridged networking. Without bridged networking, I don't know if all the cloud and virtualization tools meant to be used with the Sputnik project could be used out of the box.
cumptrnrd
3 Posts
0
December 2nd, 2012 22:00
I think this is where the fix is:
$ ls -l tail
lrwxrwxrwx 1 root root 8 Dec 1 01:55 tail -> original
$ cat original
#
# m
# mmmm m m mmmm mmmm mmm mm#mm
# #" "# # # #" "# #" "# #" # #
# # # # # # # # # #"""" #
# ##m#" "mm"# ##m#" ##m#" "#mm" "mm
# # # #
# " " "
# This file is managed by puppet. Do not make local changes.
domain buildd
nameserver 10.122.37.1