I am setting up a new DNS server. It will be primary for my domain.
This server is in an active subnet with a real public address.
It is not setup yet properly in .com, but that is in the works.
In the var/named/chroot/etc
I added:
named.custom (which I 'included' in named.conf)
and my various zone files.
All the log entries look good.
Oh in /etc/resolv.conf, I added my system as one of the namewervers.
When I go into nslookup and type any host name I get the error:
** server can't find foo:NXDOMAIN
where foo is whatever I typed in.
so what else did I forget to change?
Restart named. ("#/etc/rc.d/init.d/named restart;") Then, test as follows, when logged into DNS system:
nslookup - localhost
mydomain.com.
Notice the dot at the end of the domain. It'll either work or tell you that it didn't. If it works, your DNS server is set up. If not, your DNS server isn't as properly configured as you think.
-Ben
On Thursday 29 December 2005 07:28, Robert Moskowitz wrote:
I am setting up a new DNS server. It will be primary for my domain.
This server is in an active subnet with a real public address.
It is not setup yet properly in .com, but that is in the works.
In the var/named/chroot/etc
I added:
named.custom (which I 'included' in named.conf)
and my various zone files.
All the log entries look good.
Oh in /etc/resolv.conf, I added my system as one of the namewervers.
When I go into nslookup and type any host name I get the error:
** server can't find foo:NXDOMAIN
where foo is whatever I typed in.
so what else did I forget to change?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At 02:46 PM 12/29/2005, Benjamin Smith wrote:
Restart named. ("#/etc/rc.d/init.d/named restart;") Then, test as follows, when logged into DNS system:
nslookup - localhost
mydomain.com.
I have been getting no where with this one. Going through various online BIND9 setup tutorials, I see a reference to nsswitch.conf. In this file I find the entry:
hosts: files dns
I have yet to find any explaination of this file. Is there something I need to add?
Also I found references to /etc/hostname and /etc/networks. Neither are on my system. Are they needed?
And this was pretty much a standard CentOS 4.2 install, but I went back using that 'broken' add/remove gui to add BIND that I forgot (before I knew about yum install bind)
Notice the dot at the end of the domain. It'll either work or tell you that it didn't. If it works, your DNS server is set up. If not, your DNS server isn't as properly configured as you think.
-Ben
On Thursday 29 December 2005 07:28, Robert Moskowitz wrote:
I am setting up a new DNS server. It will be primary for my domain.
This server is in an active subnet with a real public address.
It is not setup yet properly in .com, but that is in the works.
In the var/named/chroot/etc
I added:
named.custom (which I 'included' in named.conf)
and my various zone files.
All the log entries look good.
Oh in /etc/resolv.conf, I added my system as one of the namewervers.
When I go into nslookup and type any host name I get the error:
** server can't find foo:NXDOMAIN
where foo is whatever I typed in.
so what else did I forget to change?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- "The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hello Robert,
What is listed in /etc/resolv.conf? You should have something like: search my.domain nameserver 10.0.0.1
where my.domain is the domainname for your network and 10.0.0.1 is the IP of the DNS server you are setting up.
jer
Friday, December 30, 2005, 9:12:52 AM, you wrote:
At 02:46 PM 12/29/2005, Benjamin Smith wrote:
Restart named. ("#/etc/rc.d/init.d/named restart;") Then, test as follows, when logged into DNS system:
nslookup - localhost
mydomain.com.
I have been getting no where with this one. Going through various online BIND9 setup tutorials, I see a reference to nsswitch.conf. In this file I find the entry:
hosts: files dns
I have yet to find any explaination of this file. Is there something I need to add?
Also I found references to /etc/hostname and /etc/networks. Neither are on my system. Are they needed?
And this was pretty much a standard CentOS 4.2 install, but I went back using that 'broken' add/remove gui to add BIND that I forgot (before I knew about yum install bind)
Notice the dot at the end of the domain. It'll either work or tell you that it didn't. If it works, your DNS server is set up. If not, your DNS server isn't as properly configured as you think.
-Ben
On Thursday 29 December 2005 07:28, Robert Moskowitz wrote:
I am setting up a new DNS server. It will be primary for my domain.
This server is in an active subnet with a real public address.
It is not setup yet properly in .com, but that is in the works.
In the var/named/chroot/etc
I added:
named.custom (which I 'included' in named.conf)
and my various zone files.
All the log entries look good.
Oh in /etc/resolv.conf, I added my system as one of the namewervers.
When I go into nslookup and type any host name I get the error:
** server can't find foo:NXDOMAIN
where foo is whatever I typed in.
so what else did I forget to change?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- "The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At 11:30 AM 12/30/2005, Jerry57 (GMail) wrote:
Hello Robert,
What is listed in /etc/resolv.conf? You should have something like: search my.domain nameserver 10.0.0.1
I got that:
cat resolv.conf ; generated by /sbin/dhclient-script search htt-consult.com nameserver 65.84.78.211 nameserver 65.84.78.209
Oh, and originally I installed the system to use DHCP. Then I the gnome Network control apt to edit stuff to go to the static address.
where my.domain is the domainname for your network and 10.0.0.1 is the IP of the DNS server you are setting up.
jer
Friday, December 30, 2005, 9:12:52 AM, you wrote:
At 02:46 PM 12/29/2005, Benjamin Smith wrote:
Restart named. ("#/etc/rc.d/init.d/named restart;") Then, test as follows, when logged into DNS system:
nslookup - localhost
mydomain.com.
I have been getting no where with this one. Going through various online BIND9 setup tutorials, I see a reference to nsswitch.conf. In this file I find the entry:
hosts: files dns
I have yet to find any explaination of this file. Is there something I need to add?
Also I found references to /etc/hostname and /etc/networks. Neither are on my system. Are they needed?
And this was pretty much a standard CentOS 4.2 install, but I went back using that 'broken' add/remove gui to add BIND that I forgot (before I knew about yum install bind)
Notice the dot at the end of the domain. It'll either work or tell you that it didn't. If it works, your DNS server is set up. If not, your DNS
server isn't
as properly configured as you think.
-Ben
On Thursday 29 December 2005 07:28, Robert Moskowitz wrote:
I am setting up a new DNS server. It will be primary for my domain.
This server is in an active subnet with a real public address.
It is not setup yet properly in .com, but that is in the works.
In the var/named/chroot/etc
I added:
named.custom (which I 'included' in named.conf)
and my various zone files.
All the log entries look good.
Oh in /etc/resolv.conf, I added my system as one of the namewervers.
When I go into nslookup and type any host name I get the error:
** server can't find foo:NXDOMAIN
where foo is whatever I typed in.
so what else did I forget to change?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- "The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- USE THE BEST . . .
Linux for servers . . .
Macintosh for graphics . . . Palm for mobility . . . Windows for solitaire!
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, 2005-12-30 at 11:36 -0500, Robert Moskowitz wrote:
I got that: cat resolv.conf ; generated by /sbin/dhclient-script search htt-consult.com nameserver 65.84.78.211 nameserver 65.84.78.209 Oh, and originally I installed the system to use DHCP. Then I the gnome Network control apt to edit stuff to go to the static address.
Is this your DNS server?
Your DNS server should use itself, and then forward as appropriate in its named.conf file.
This is coming up so much that I think we need just a dedicated FAQ on "proper DNS server/network configuration."
At 12:19 PM 12/30/2005, Bryan J. Smith wrote:
On Fri, 2005-12-30 at 11:36 -0500, Robert Moskowitz wrote:
I got that: cat resolv.conf ; generated by /sbin/dhclient-script search htt-consult.com nameserver 65.84.78.211 nameserver 65.84.78.209 Oh, and originally I installed the system to use DHCP. Then I the gnome Network control apt to edit stuff to go to the static address.
Is this your DNS server?
Your DNS server should use itself, and then forward as appropriate in its named.conf file.
the .211 is the server's address. .209 is the firewall that acts as a DNS proxy for other systems (until .211 gets working).
So you are implying that I should remove the 2nd entry. OK, but somehow I don't think that is my problem...
This is coming up so much that I think we need just a dedicated FAQ on "proper DNS server/network configuration."
-- Bryan J. Smith mailto:b.j.smith@ieee.org http://thebs413.blogspot.com
Some things (or athletes) money can't buy. For everything else there's "ManningCard."
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I know the comments about top posting, but I think it is ok in this case....
I finally got DNS working. Dumb dumb dumb.
I was so fed up, and since there was nothing on this system and I installed BIND by using the 'broken' redhat GUI instead of installing intially or using yum install, I did a total rebuild (and brought the system memory up to 256Mb by stealing from another system for now).
Had a real rough time on that reinstall (another story and post).
Well, I again copied my named.custom and *.zone files into /var/named/chroot/etc and it still did not work.
So I again stared at the system logs. I finally noticed that named.custom was being processed, but none of the zone files were being found.
I looked at my mode to named.conf and I had:
include "'/etc/named.custom"
But in named.custom I had:
file "whatever.zone"
Dah.
changed that to be "/etc/whatever.zone" and things started working right!
Now how in the bleep did I have this in my old attempt (but Centos 3.4) and it worked?
On to getting mail working then telling all and sundry that my primary dns server is on a new address. Oh what fun that will be!
At 12:19 PM 12/30/2005, Bryan J. Smith wrote:
On Fri, 2005-12-30 at 11:36 -0500, Robert Moskowitz wrote:
I got that: cat resolv.conf ; generated by /sbin/dhclient-script search htt-consult.com nameserver 65.84.78.211 nameserver 65.84.78.209 Oh, and originally I installed the system to use DHCP. Then I the gnome Network control apt to edit stuff to go to the static address.
Is this your DNS server?
Your DNS server should use itself, and then forward as appropriate in its named.conf file.
This is coming up so much that I think we need just a dedicated FAQ on "proper DNS server/network configuration."
-- Bryan J. Smith mailto:b.j.smith@ieee.org http://thebs413.blogspot.com
Some things (or athletes) money can't buy. For everything else there's "ManningCard."
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tuesday 03 January 2006 08:10 am, Robert Moskowitz wrote:
Now how in the bleep did I have this in my old attempt (but Centos 3.4) and it worked?
Has to do with the default directory structure for 3.x vs 4.x.
My guess is that 3.x didn't have a chrooted BIND and that 4.x did.
But it's only a guess based on recollection; I'm not looking at a system now.
Jeff
On Tue, 2006-01-03 at 11:27 -0800, Jeff Lasman wrote:
On Tuesday 03 January 2006 08:10 am, Robert Moskowitz wrote:
Now how in the bleep did I have this in my old attempt (but Centos 3.4) and it worked?
Has to do with the default directory structure for 3.x vs 4.x.
My guess is that 3.x didn't have a chrooted BIND and that 4.x did.
But it's only a guess based on recollection; I'm not looking at a system now.
You can install bind in either a chroot or the regular way on C4.
Johnny Hughes wrote:
On Tue, 2006-01-03 at 11:27 -0800, Jeff Lasman wrote:
Has to do with the default directory structure for 3.x vs 4.x.
My guess is that 3.x didn't have a chrooted BIND and that 4.x did.
But it's only a guess based on recollection; I'm not looking at a system now.
You can install bind in either a chroot or the regular way on C4.
Same goes for CentOS3.x
Ralph
On Wednesday 04 January 2006 07:45 am, Ralph Angenendt wrote:
You can install bind in either a chroot or the regular way on C4.
Same goes for CentOS3.x
We do default installs, and on CentOS3, we always ended up with a non-chainrooted BIND; on CentOS4 we always end up with a chainrooted BIND.
Jeff
Jeff Lasman wrote:
On Wednesday 04 January 2006 07:45 am, Ralph Angenendt wrote:
You can install bind in either a chroot or the regular way on C4.
Same goes for CentOS3.x
We do default installs, and on CentOS3, we always ended up with a non-chainrooted BIND; on CentOS4 we always end up with a chainrooted BIND.
Wondering what a "default install" might be:
On both systems you need the bind-chroot package, if you want to have a chrooted bind.
bind-chroot-9.2.4-7_EL3 on CentOS 3 and bind-chroot-9.2.4-2 on CentOS 4.
Ralph
On Tuesday 10 January 2006 02:25 am, Ralph Angenendt wrote:
Wondering what a "default install" might be:
We install from standard installation media.
Server install ONLY.
We install only these options: text-based internet dns name server postgresql database network servers
Later we uninstall caching-nameserver because updating it has caused us to lose our customized named.conf file.
Jeff
At 11:24 AM 1/10/2006, Jeff Lasman wrote:
On Tuesday 10 January 2006 02:25 am, Ralph Angenendt wrote:
Wondering what a "default install" might be:
We install from standard installation media.
Server install ONLY.
We install only these options: text-based internet dns name server postgresql database network servers
Later we uninstall caching-nameserver because updating it has caused us to lose our customized named.conf file.
Which is why you are suppose to use named.custom
I think.
On Tuesday 10 January 2006 02:12 pm, Robert Moskowitz wrote:
Which is why you are suppose to use named.custom
I think.
That may be true. However I'm stuck with what my hosting control panel recognizes. I've never seen a named.custom anywhere. Has anyone implemented it?
When caching-nameserver updates named.conf it doesn't add back any of our includes. Perhaps it does an include for named.custom.
Anyone tried it?
Jeff
On Tue, 2006-01-10 at 16:44, Jeff Lasman wrote:
When caching-nameserver updates named.conf it doesn't add back any of our includes. Perhaps it does an include for named.custom.
Anyone tried it?
No, I think you just aren't supposed to install the caching-nameserver unless all you want is a caching nameserver. The normal bind with or without bind-chroot will do caching too but they also let you keep your custom changes.
On Tuesday 10 January 2006 03:07 pm, Les Mikesell wrote:
No, I think you just aren't supposed to install the caching-nameserver unless all you want is a caching nameserver. The normal bind with or without bind-chroot will do caching too but they also let you keep your custom changes.
I agree with you, but caching-nameserver gets installed in our install when we install "dns name server", so the install perhaps isn't quite intuitive.
Jeff
-
Benjamin Smith -
Bryan J. Smith -
Jeff Lasman -
Jerry57 (GMail) -
Johnny Hughes -
Les Mikesell -
Ralph Angenendt -
Robert Moskowitz