BIND9 Linux UDP not responding

Hi,

I current have now got a primary (and secondary i think, depends if i've configured correctly) but using the dns crawler, I can only get a response from TCP but not UDP. I have opened the correct ports on the firewall so I have no idea why its not responding, all I get is a response from TCP and from UDP i get:

Response Timed out!
Waited 5 seconds for the UDP response

anyone know whats wrong ?
thanks

what's your domain or server IP?

domain is pspltd.homeip.net

oh, well, that's not going to show me what your server IP is. I guess you have to tell me that directly.

the server IP, do you mean local or external

internal 192.168.1.1
external 82.163.167.227

Now enter this command at the commandline:

C:\>netstat -an | find ":53"

Show me the response, then execute this command:

C:\path\to\binds\dns\bin>dig @127.0.0.1 pspltd.homeip.net

Show me the response to that as well.

btw, the server is linux, sorry, should have mentioned earlier but in windows netstat command returned nothing and the dig command I can't run because its a linux machine

Then execute these equivilent commands:

netstat -an | grep ":53"

dig @127.0.0.1 pspltd.homeip.net

netstat -an | grep ":53" produces:

[root@localhost root]# netstat -an | grep ":53"
tcp 0 0 192.168.1.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
udp 0 0 192.168.1.1:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 192.168.1.1:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
[root@localhost root]#

and dig @127.0.0.1 pspltd.homeip.net produces:

[root@localhost root]# dig @127.0.0.1 pspltd.homeip.net

; <<>> DiG 9.2.3 <<>> @127.0.0.1 pspltd.homeip.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10077
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;pspltd.homeip.net. IN A

;; ANSWER SECTION:
pspltd.homeip.net. 86400 IN A 82.163.167.227

;; AUTHORITY SECTION:
pspltd.homeip.net. 86400 IN NS pspltd.homeip.net.
pspltd.homeip.net. 86400 IN NS www.pspltd.homeip.net.

;; ADDITIONAL SECTION:
www.pspltd.homeip.net. 86400 IN A 82.163.167.227

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 15 18:49:05 2004
;; MSG SIZE rcvd: 99

[root@localhost root]#

Just to cover all our bases, now try this command:

dig @192.168.1.1 pspltd.homeip.net

Also, explain a bit about your box here. You've got the IP address of 192.168.1.1 so it looks like a gateway server or something. Explain your modem/router/switch/hub/computers setup.

Also try this command at the prompt and see if your UDP starts working.

service iptables stop

the response from dig @192.168.1.1 pspltd.homeip.net was:

[root@localhost root]# dig @192.168.1.1 pspltd.homeip.net

; <<>> DiG 9.2.3 <<>> @192.168.1.1 pspltd.homeip.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57569
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;pspltd.homeip.net. IN A

;; ANSWER SECTION:
pspltd.homeip.net. 86400 IN A 82.163.167.227

;; AUTHORITY SECTION:
pspltd.homeip.net. 86400 IN NS www.pspltd.homeip.net.
pspltd.homeip.net. 86400 IN NS pspltd.homeip.net.

;; ADDITIONAL SECTION:
www.pspltd.homeip.net. 86400 IN A 82.163.167.227

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jul 15 19:25:58 2004
;; MSG SIZE rcvd: 99

[root@localhost root]#

and I stopped IPtables but that made no difference, UDP still didn't work.

The setup I am running is an IPcop router with:
Green network: 192.168.0.*
Orange network: 192.168.1.*
Red network: dlink router(with all ports forwarded to ipcop)

the dlink router is then connected to the internet

theres a 24 port switch on the green network and a 5 port switch on the orange network

show me the response to the following command executed from another computer on the network:

dig @192.168.1.1 pspltd.homeip.net

thanks, I have now solved this as you made me think when you asked what the setup was. I thought, i bet I have only forwarded TCP on the dlink, and that was the problem. As soon as I forwarded the UDP ports to ipcop, everything started working

thanks