re[2]: [SLE] getting named to run w/Suse 8.1
I guess I'll have to go read that HowTo, but I suspect it won't help. My problem is almost definitely SuSE specific and the HowTOs are Linux generic from what I have seen. I have installed and configure named (bind) a dozen times at least on various UNIX and RH servers. Doing what I believe is correct on SuSE gives me a functioning UDP name server. That is actually all that I critically need because Windows uses UDP requests. nslookup uses TCP, so it does not function. I have not tried dig on that machine, so I don't know if it works or not. Again the issue is that named complains that the tcp ports it wants to bind to are already in use, so it is only binding to the udp ports. When I do a "fuser -n tcp 53" it does not show any other users. Greg -- Greg Freemyer
The 03.03.05 at 15:49, Greg Freemyer wrote:
I have a new suse 8.1 install that I want to be a dns server.
I have enabled named via the runlevel editor.
It is now starting, but it is not working and I'm getting an entry in /var/log/warn from named about port already in use.
What am I doing wrong?
You should configure it first...
Also, once I get it working, is there a config tool for editing named.conf, or do I just use vi like I'm used to.
I think I saw something on the CDs, but never tried it... something for kde or gnome, I might be mistaken.
There is a howto, read it first :-)
-- Cheers, Carlos Robinson
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
The 03.03.14 at 15:39, Greg Freemyer wrote:
I guess I'll have to go read that HowTo, but I suspect it won't help.
My problem is almost definitely SuSE specific and the HowTOs are Linux generic from what I have seen.
Well... probably it will be something specific to your configuration, because I have bind running here, and it works.
Again the issue is that named complains that the tcp ports it wants to bind to are already in use, so it is only binding to the udp ports.
When I do a "fuser -n tcp 53" it does not show any other users.
Are you doing that as root? I suppose so, but just in case. Ah, I have just looked on the sdb, and your error message is reported there. I'll copy it here for your convenience: Symptom: Every time you log in, the following error message is displayed: earth login: bind: address already in use Cause: A start script triggers an attempt to start a network service for a second time. Solution: Remove this double entry automatically by entering the command: rctab -r After a reboot, the message is no longer displayed. -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R.
-
Greg Freemyer