Howto: Setup a DNS server with bind

[Nokao]

Internal dns service seems to work, however:

I didn't understand how to define a certain IP for an EXTERNAL whatever website... and WHERE to do it.

[dmfrey]

I followed this tutorial for my Feisty server. My clients can all ping/nslookup/dig the dns server, however, they cannot perform any of those commands on other clients on the network. My network consists of three machines: the dns server, one static ip client, and one dynamic ip client. Each has the resolve.conf setup to point back to the dns server. How do i get the name resolutions established for all of the clients on the network automatically?

Thanks for any help.

[mark27]

Hy i have problem when i am restarting the bind9
i am having this ouput
Stopping domain name service... rndc: connect failed: connection refused
[ ok ]
* Starting domain name service... .

i would like to know how can i solve the problem, what happen it.

[CopaceticOpus]

I typed "rndc" into Google and the first result describes your error message and a suggested remedy for it:

http://www.redhat.com/docs/manuals/l...bind-rndc.html

[bignose]

I typed "rndc" into Google and the first result describes your error message and a suggested remedy for it:

http://www.redhat.com/docs/manuals/l...bind-rndc.html

I'm having the exact same error. Except :

I have a defult LTS install where rndc works just fine and there is not a 'control statement in named.conf...

Then I have another machine that a colo facility installed for me, and rndc just won't go... and the named.conf files do not differ [i ran a diff on them]

CORRECTION : the working machine is LTS, the non working one is Edgy, however teh files still do not differ.

Jeff.

[sgla1]

One more step to get it to work:
You must rename the named.conf.local to named.conf

If you read all the way to the bottom of named.conf you will see the following line:

include "/etc/bind/named.conf.local";

You absolutely need named.conf -- if you are foolish enough to rename it (thereby overwriting named.conf--see man mv) you will never have a working dns server. The only way to eliminate named.conf.local is to paste all of it's contents into named.conf.

I'm sorry if this sounds harsh but unfortunately there is a lot of bad advice in these forums. People, please test your advice carefully before you post.

[sgla1]

Please ignore--does not reference OP

[stubba]

My clients can all ping/nslookup/dig the dns server, however, they cannot perform any of those commands on other clients on the network

I'm having the same issue. Any help greatly appreciated...

[lkstamenov]

Nice! Works! But if you add the following :

1. Remove any comments from the zones files (those in zones directory)
2. Test the domain with
sudo named-checkzone exampledomain.com

And it works like a dream

[iLLiCiTgr]

Interesting Guide