system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers

3 posts / 0 new
Topic locked
Last post
#1 Fri, 08/31/2018 - 22:01
adamjedgar

system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers

I am quite frankly sick of this problem and it keeps popping up whenever i least expect it when setting up a new machine. I cannot for the life of me remember how to fix it when i wish to run bind dns and use the system as a nameserver.

My Microsoft Azure Virtual Machine is running a static ip address

google drive image of the problem spot here...https://drive.google.com/open?id=1VTJbOFIX6ynNAaiRbvY8VH8zEVyQgI2i

Is the following solution good enough...

  1. login to ssh command prompt via putty (or through virtualmin interface directly)
  2. sudo su
  3. now as root user edit nano /etc/rc.local
  4. add the following line into rc.local just before the line "exit 0" echo nameserver 127.0.0.1 >> /etc/resolv.conf

is this an ok solution?

Fri, 08/31/2018 - 22:58
Freddy63
Freddy63's picture

+1 for this question. I would like to know that too.

I provide FREE Server Management Services in exchange of money

Thu, 09/06/2018 - 05:43
unborn
unborn's picture

hi, I had same problem on my debian box which turned to be simple - I had no static ip setup on that server, basically I setup static ip on router but not on server. As I configured static ip to be asked from router on box rather then assign static ip to the box from router this problem went away. also you can add this into your system..

Configuring/troubleshooting Debian servers is always great fun

Topic locked