Knowledge Partner
Knowledge Partner
1213 views

dns failing

OES 11 / SLES 11 SP1 server running DNS. Twice now during the last
couple of weeks, DNS has failed. rcnovell-named status reports
unused. So I start it and it runs again for a while. Is there a log
file somewhere that would tell me what is happening? If not, any
suggestions?

I know the server isn't current...started to update my OES servers
only to run into an NCP/kernel issue. So I'm waiting on that fix
before continuing with the patching.

Ken
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
Labels (2)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: dns failing

On Tue, 26 Feb 2013 21:27:10 GMT, KeN Etter
<ketter@no-mx.forums.novell.com> wrote:

>OES 11 / SLES 11 SP1 server running DNS. Twice now during the last
>couple of weeks, DNS has failed. rcnovell-named status reports
>unused. So I start it and it runs again for a while. Is there a log
>file somewhere that would tell me what is happening? If not, any
>suggestions?
>
>I know the server isn't current...started to update my OES servers
>only to run into an NCP/kernel issue. So I'm waiting on that fix
>before continuing with the patching.
>
>Ken


Sorry for the double post...still having problems with my news reader.
Waiting on news reader support to get back to me.
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
Knowledge Partner
Knowledge Partner

Re: dns failing

ketter;2249053 wrote:
OES 11 / SLES 11 SP1 server running DNS. Twice now during the last
couple of weeks, DNS has failed. rcnovell-named status reports
unused. So I start it and it runs again for a while. Is there a log
file somewhere that would tell me what is happening? If not, any
suggestions?

I know the server isn't current...started to update my OES servers
only to run into an NCP/kernel issue. So I'm waiting on that fix
before continuing with the patching.

Ken


Hey Ken,

Define "isn't current"? 😉

If it's really not current, see: Support | DNS is not responsive or cores which might help until you get things patched up.

Cheers,
Willem
0 Likes
Knowledge Partner
Knowledge Partner

Re: dns failing

On Wed, 27 Feb 2013 19:06:02 GMT, magic31
<magic31@no-mx.forums.novell.com> wrote:

>
>ketter;2249053 Wrote:
>> OES 11 / SLES 11 SP1 server running DNS. Twice now during the last
>> couple of weeks, DNS has failed. rcnovell-named status reports
>> unused. So I start it and it runs again for a while. Is there a log
>> file somewhere that would tell me what is happening? If not, any
>> suggestions?
>>
>> I know the server isn't current...started to update my OES servers
>> only to run into an NCP/kernel issue. So I'm waiting on that fix
>> before continuing with the patching.
>>
>> Ken

>
>Hey Ken,
>
>Define "isn't current"? 😉


OES 11 on SLES 11 SP1

>If it's really not current, see: 'Support | DNS is not responsive or
>cores' (http://www.novell.com/support/kb/doc.php?id=7006015) which might
>help until you get things patched up.


Doesn't seem to apply...however I do have lots of these showing up in
named.run

general: socket: error: socket: too many open file descriptors

client: query: warning: client 192.168.1.125#1038: no more recursive
clients: quota reached

How do I resolve those?

Ken
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
Knowledge Partner
Knowledge Partner

Re: dns failing

ketter;2249330 wrote:
......however I do have lots of these showing up in
named.run

general: socket: error: socket: too many open file descriptors

client: query: warning: client 192.168.1.125#1038: no more recursive
clients: quota reached

How do I resolve those?

Ken


Haven't seen those error before... patching would be the first thing to do imo.

Curious, what is this server generally doing, and how many users is it doing this for?

-Willem
0 Likes
Knowledge Partner
Knowledge Partner

Re: dns failing

On Thu, 28 Feb 2013 08:56:01 GMT, magic31
<magic31@no-mx.forums.novell.com> wrote:

>
>ketter;2249330 Wrote:
>> ......however I do have lots of these showing up in
>> named.run
>>
>> general: socket: error: socket: too many open file descriptors
>>
>> client: query: warning: client 192.168.1.125#1038: no more recursive
>> clients: quota reached
>>
>> How do I resolve those?
>>
>> Ken

>
>Haven't seen those error before... patching would be the first thing to
>do imo.


On the list to do...hopefully soon.

>Curious, what is this server generally doing, and how many users is it
>doing this for?


About 60 users. File server, iPrint, NetStorage, DNS, DHCP.
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
W_Prindl Absent Member.
Absent Member.

Re: dns failing

Have you looked into memory consumption of novell-named? I have an
OES11SP1 server, which is running novell-named for just a few users and
machines and memory consumption is steadily growing (see attached
screebshot) till a reboot or a restart of novell-named. I would assume
that this could also kill novell-named, if memory used gets to big.

--
W. Prindl


KeN Etter wrote:

>OES 11 / SLES 11 SP1 server running DNS. Twice now during the last
>couple of weeks, DNS has failed. rcnovell-named status reports
>unused. So I start it and it runs again for a while. Is there a log
>file somewhere that would tell me what is happening? If not, any
>suggestions?
>
>I know the server isn't current...started to update my OES servers
>only to run into an NCP/kernel issue. So I'm waiting on that fix
>before continuing with the patching.
>
>Ken




W. Prindl
0 Likes
joharmon Absent Member.
Absent Member.

Re: dns failing

Sounds like you might be hitting a hard limit on the number of recursion lookups you are allowing on the server. You can either disable recursion and let the clients look things up, or bump up the hard limit of recursions.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.