Anonymous_User Absent Member.
Absent Member.
1828 views

DNS error

Hello,

i have the following erro in de logger screen of one of my DNS servers, it wil not start:

<Press any key to close screen>
Starting eDirectory integrated Novell DNS Server...
error: socket: too many open file descriptors
error: could not listen on UDP socket: not enough free resources
error: creating IPv4 interface Loopback Interface 1 failed; interface ignored
error: Error occured while updating the IP list of the DNS server object
critical: loading configuration: failure
critical: exiting (due to fatal error)
DNS Server is unloaded successfully
DNS Server Exiting

Has someone else seen this before ??

Thanx Dave Simons
Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: DNS error

NetWare version? Service Pack? NAMED.NLM version?

> error: could not listen on UDP socket: not enough free resources
>

Is UDP port 53 in use before you run NAMED?

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Betr.: Re: DNS error

sorry,

NW6.5 SP5

version named:
eDirectory integrated Novell DNS Server
Version 6.04.15 5 December 2005

Who can i see if port 53 is already in use ?

Thanx Dave



>>> Brad Doster<bd@NSCSysOps.net> 13-07-2006 16:08 >>>

NetWare version? Service Pack? NAMED.NLM version?

> error: could not listen on UDP socket: not enough free resources
>

Is UDP port 53 in use before you run NAMED?

bd
NSC Volunteer SysOp
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Betr.: DNS error

In article <44B7581F.0C29.001C.0@pantein.nl>, D.J.H.T. Simons wrote:
> Who can i see if port 53 is already in use ?
>

On the server, TCPCON --> Protocol Information --> TCP --> TCP
Connections.... look for '53' or 'domain' in the first Port column.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Betr.: DNS error

mmmmmmmmm

i had an frozen server when i hit enter on the "TCP
Connections". After the reboot the server was running fine again

>>> Brad Doster<bd@NSCSysOps.net> 15-07-2006 16:38 >>>

In article <44B7581F.0C29.001C.0@pantein.nl>, D.J.H.T. Simons wrote:
> Who can i see if port 53 is already in use ?
>

On the server, TCPCON --> Protocol Information --> TCP --> TCP
Connections.... look for '53' or 'domain' in the first Port column.

bd
NSC Volunteer SysOp
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Betr.: DNS error

In article <44BB91A0.0C29.001C.0@pantein.nl>, D.J.H.T. Simons wrote:
> mmmmmmmmm
>
> i had an frozen server when i hit enter on the "TCP
> Connections". After the reboot the server was running fine again
>

Sounds like the DNS problem may have been a symptom of some other
problem then. In any event, glad it's working now...

bd
NSC Volunteer SysOp


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.