|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
DNS Win2000, could not listen on UDP Socket: Unexpected Error
Trying to set up BINDS on win2000
Cannot get named to start. Using "named -g" get "could not listen on UDP Post: Unexpected error", named conf seems ok, I have done following: - I changed setup to exact setup as from http://serialcoders.sytes.net/BIND/. - If I delete files (root.hint) get cannot find file error (as expected). - If I have garbage in named.conf (eg line with "aa") get error "unknown option 'aa'" (as expected) Am logged onto Windows as administrator Google doesn't show any entries for "could not listen on UDP Socket: unexpected Error" Full output from "named -g" is C:\Program Files\DNS\bin>named -g Nov 20 10:43:46.628 starting BIND 9.2.3 -g Nov 20 10:43:46.628 using 1 CPU Nov 20 10:43:46.638 loading configuration from 'c:\Program Files\DNS\etc\named.c onf' Nov 20 10:43:46.638 set maximum stack size to 0: not implemented Nov 20 10:43:46.638 set maximum data size to 0: not implemented Nov 20 10:43:46.638 set maximum core size to 0: not implemented Nov 20 10:43:46.638 set maximum open files to 0: not implemented Nov 20 10:43:46.638 listening on IPv4 interface Loopback Interface 1, 127.0.0.1# 53 Nov 20 10:43:46.638 could not listen on UDP socket: unexpected error Nov 20 10:43:46.638 creating IPv4 interface Loopback Interface 1 failed; interfa ce ignored Nov 20 10:43:46.638 listening on IPv4 interface TCP/IP Interface 2, 192.168.1.16 1#53 Nov 20 10:43:46.638 could not listen on UDP socket: unexpected error Nov 20 10:43:46.638 creating IPv4 interface TCP/IP Interface 2 failed; interface ignored Nov 20 10:43:46.638 not listening on any interfaces Nov 20 10:43:46.648 ..\resolver.c:4755: REQUIRE(dispatchv4 != ((void *)0) || dis patchv6 != ((void *)0)) failed Nov 20 10:43:46.648 exiting (due to assertion failure) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Any ideas please? |
|
#2
|
||||
|
||||
|
show us the response from a commandline command:
netstat -an I suspect something is already bound to port 53 for UDP. If so, you need to shut down that program. If you don't know what program is using that port then download TCPView from www.sysinternals.com. It is like netstat except it shows you the program responsible for each socket.
__________________
Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links: Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts |
|
#3
|
|||
|
|||
|
Should have mentioned in initial post.
- Nothing is bound to port 53 in Netstat - it is win2000 professional (not server) This is output from TCP view Apache.exe:440 TCP ath700:http ath700:0 LISTENING IEXPLORE.EXE:1724 UDP ath700:1030 *:* lsass.exe:224 UDP ath700:isakmp *:* MSTask.exe:1612 TCP ath700:1025 ath700:0 LISTENING services.exe:212 UDP ath700:1026 *:* svchost.exe:372 TCP ath700:epmap ath700:0 LISTENING svchost.exe:372 UDP ath700:epmap *:* System:8 TCP ath700:microsoft-ds ath700:0 LISTENING System:8 TCP ath700:1027 ath700:0 LISTENING System:8 TCP ath700:netbios-ssn ath700:0 LISTENING System:8 UDP ath700:microsoft-ds *:* System:8 UDP ath700:netbios-ns *:* System:8 UDP ath700:netbios-dgm *:* System:8 TCP ath700:1129 ath700:0 LISTENING System:8 TCP ath700:1129 pii400:netbios-ssn ESTABLISHED |
|
#4
|
||||
|
||||
|
This problem is really frustrating me, makes me wish I never asked. So I am going to ask you to give me a complete mapping of what you have and where. Tell me the paths of all of your BIND binaries and configuration files. In addition, I would like to see your named.conf. There is a chance there's a bug in the newest BIND (I use 9.2.2) that is caused by something unusual in your windows setup. I say this cause of the unusual error information you've shown me. And lastly I want you to take a look in the following location for more error information that may shed some light on the problem:
Control Panel -> Administrative Tools -> Event Viewer -> Application Log All red flagged "named" entries are BIND errors. |
|
#5
|
|||
|
|||
|
Not quite sure what you mean by mapping
Files in \Program Files\DNS\etc are - 1.0.0.127.IN-ADDR.ARPA.zone - dns.log (0 kb) - example.com.zone - named.conf - root.hint CONTENTS OF NAMED.CONF options { # Set the working directory from which all relative paths are based # directory "/Program Files/DNS/etc"; # this server performs as a caching server. Allow recursion # recursion yes; # For requests we aren't authoritative for, forward the request to # the forwarder servers first, then try resolving it ourself # forward first; # use these servers as forwarders when resolving requests # forwarders { 68.51.0.6; 68.51.0.5; }; # Do not notify servers of zone changes # notify no; }; # I'm a log fan logging { channel query_logging { file "/Program Files/DNS/etc/dns.log" versions 3 size 100M; print-time yes; // timestamp log entries }; category queries { query_logging; }; category lame-servers { null; }; }; # Specify the root name servers zone "." IN { type hint; file "root.hint"; }; # example zone used for testing of DNS software I develop zone "example.com" IN { type master; file "example.com.zone"; }; # and of course the reverse lookup for the zone zone "1.0.0.127.in-addr.arpa" { type master; file "1.0.0.127.IN-ADDR.ARPA.zone"; }; CONTENTS OF APPLICATION LOG (FOR LAST REBOOT) Type Date Time Source Category Event User Computer Error 21/11/2003 8:27:58 AM XMail None 0 N/A ATH700 Error 21/11/2003 8:27:58 AM XMail None 0 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Warning 21/11/2003 8:27:57 AM named None 2 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Information 21/11/2003 8:27:57 AM named None 3 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Error 21/11/2003 8:27:57 AM named None 1 N/A ATH700 Information 21/11/2003 8:27:57 AM named None 3 N/A ATH700 Warning 21/11/2003 8:27:57 AM named None 2 N/A ATH700 Warning 21/11/2003 8:27:57 AM named None 2 N/A ATH700 Warning 21/11/2003 8:27:57 AM named None 2 N/A ATH700 Warning 21/11/2003 8:27:57 AM named None 2 N/A ATH700 Information 21/11/2003 8:27:57 AM named None 3 N/A ATH700 Information 21/11/2003 8:27:57 AM named None 3 N/A ATH700 Information 21/11/2003 8:27:57 AM named None 3 N/A ATH700 |
|
#6
|
||||
|
||||
|
Ok, there are 3 information events at the very bottom, 4 warnings above that. All those should be normal. I want to know all the descriptions of each event above those.
|
|
#7
|
|||
|
|||
|
Log Descriptions - Latest First
XMAIL - Error The description for Event ID ( 0 ) in Source ( XMail ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: XMail error: 0, {Error in function {stat}}: The operation completed successfully. (0x0). XMAIL - Error The description for Event ID ( 0 ) in Source ( XMail ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Error in function {stat} Named - Error - exiting (due to assertion failure) Named - Error - ..\resolver.c:4755: REQUIRE(dispatchv4 != ((void *)0) || dispatchv6 != ((void *)0)) failed Named - Warning - not listening on any interfaces Named - Error - creating IPv4 interface TCP/IP Interface 2 failed; interface ignored Named - Error - could not listen on UDP socket: unexpected error Named - Information - listening on IPv4 interface TCP/IP Interface 2, 192.168.1.161#53 Named - Error - creating IPv4 interface Loopback Interface 1 failed; interface ignored Named- Error- could not listen on UDP socket: unexpected error Named - Information - listening on IPv4 interface Loopback Interface 1, 127.0.0.1#53 Which is basically the same log as I get running named -g Thankyou Glenn |
|
#8
|
||||
|
||||
|
That was actually helpful. Now I know that the server did not terminate cause it couldn't bind to your interfaces. Add this to your options block and show me the error log.
listen-on port 1053 { 127.0.0.1; 192.168/16; }; With the above I'm trying to avoid the UDP errors so that we can determine if the server still can't start. I've never seen the following error before. Nor could I find any information from google about it. ..\resolver.c:4755: REQUIRE(dispatchv4 != ((void *)0) || dispatchv6 != ((void *)0)) failed I will have to look at the BIND source code to figure out why that error occured. This error is what I think may be a bug in the BIND software. It is an error that includes code, which may indicate a "note" that the programmer left themself in case the theoretical bug actually proved to be a bug in fact. I myself am a programmer and that's kind of what I do. |
|
#9
|
|||
|
|||
|
Added that line to options then ran named -g.
listen-on port 1053 { 127.0.0.1; 192.168/16; }; The output looks the same. C:\Program Files\DNS\bin>named -g Nov 21 13:49:25.563 starting BIND 9.2.3 -g Nov 21 13:49:25.573 using 1 CPU Nov 21 13:49:25.583 loading configuration from 'c:\Program Files\DNS\etc\named.c onf' Nov 21 13:49:25.593 set maximum stack size to 0: not implemented Nov 21 13:49:25.593 set maximum data size to 0: not implemented Nov 21 13:49:25.593 set maximum core size to 0: not implemented Nov 21 13:49:25.603 set maximum open files to 0: not implemented Nov 21 13:49:25.603 listening on IPv4 interface Loopback Interface 1, 127.0.0.1# 1053 Nov 21 13:49:25.613 could not listen on UDP socket: unexpected error Nov 21 13:49:25.613 creating IPv4 interface Loopback Interface 1 failed; interfa ce ignored Nov 21 13:49:25.623 listening on IPv4 interface TCP/IP Interface 2, 192.168.1.16 1#1053 Nov 21 13:49:25.633 could not listen on UDP socket: unexpected error Nov 21 13:49:25.643 creating IPv4 interface TCP/IP Interface 2 failed; interface ignored Nov 21 13:49:25.653 not listening on any interfaces Nov 21 13:49:25.663 ..\resolver.c:4755: REQUIRE(dispatchv4 != ((void *)0) || dis patchv6 != ((void *)0)) failed Nov 21 13:49:25.663 exiting (due to assertion failure) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Glenn |
|
#10
|
|||
|
|||
|
Sorry, it is not the same, is now trying to listen on port 1053 rather than 53
Glenn |
|
#11
|
|||
|
|||
|
Downloaded and installed BIND 8.4.1 and it loads test files without errors. (Haven't done anything else but install, reboot, and run their BINDCTRL.exe program)
(Sorry, did not note previous version was BIND 9.2.3) Should i report it to ISC org as a bug? Again, thank you muchly for your help, silentRage |
|
#12
|
||||
|
||||
|
Yes, go ahead and report the bug. Even if it is not a bug, maybe they'll tell you what's up with the error.
|
|
#13
|
|||
|
|||
|
reported error to ISC
Problem is Service Packs not installed for win2000 Installed Service Pack 4 and all is OK Again, Thank you for your time, is really appreciated |
![]() |
| Viewing: Dev Shed Forums > System Administration > DNS > DNS Win2000, could not listen on UDP Socket: Unexpected Error |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|