pn] I'm preparing to upgrade to Bering, and was trying to refresh my memory of my existing E2B configuration which I haven't touched in quite a while. I recently noticed that my name server was no longer functioning (my domains are quite inactive). I thought I just found the problem when I performed the Maytag test; the little green indicator light on the 3C905B-TX NIC for the DMZ on my router is not lit like it is for the internal network. So I figured I have a bad NIC or cable. But I can ping the name server from the router using the private address. I CANNOT ping the router's DMZ gateway from the name server. The name server has no firewall rules (well, everything is open by default).
pn] Brief overview: I have four static IPs, 66.92.161.9-12. The router is on .9, and the name server on .10. The other two are unused, but aliased to .9. My private network is 10.4.1.xxx and the DMZ is 10.4.2.xxx.
pn] One other note: when I ping the name server using the externally mapped address (66.92.161.10), I get the following for each packet sent. I don't know if this is related.
ping: sendto: invalid argument ping: wrote 66.92.161.10 64 chars, ret=-1
pn] Any ideas?
Looks like you have a low-level networking (or firewall) problem. I can ping your firewall, but *NOT* your DNS system:
[EMAIL PROTECTED] charles]$ ping 66.92.161.9 PING 66.92.161.9 (66.92.161.9) from 10.34.1.21 : 56(84) bytes of data. 64 bytes from 66.92.161.9: icmp_seq=1 ttl=240 time=87.0 ms 64 bytes from 66.92.161.9: icmp_seq=2 ttl=240 time=85.9 ms 64 bytes from 66.92.161.9: icmp_seq=3 ttl=240 time=85.1 ms 64 bytes from 66.92.161.9: icmp_seq=4 ttl=240 time=86.6 ms
--- 66.92.161.9 ping statistics --- 4 packets transmitted, 4 received, 0% loss, time 3033ms rtt min/avg/max/mdev = 85.111/86.180/87.001/0.799 ms [EMAIL PROTECTED] charles]$ ping 66.92.161.10 PING 66.92.161.10 (66.92.161.10) from 10.34.1.21 : 56(84) bytes of data. From 66.92.161.9 icmp_seq=3 Destination Host Unreachable From 66.92.161.9 icmp_seq=2 Destination Host Unreachable From 66.92.161.9 icmp_seq=1 Destination Host Unreachable
...Thinking maybe you firewall pings, but DNS would go through, I tried a quick dig:
[EMAIL PROTECTED] charles]$ dig www.google.com @66.92.161.10
; <<>> DiG 9.2.1 <<>> www.google.com @66.92.161.10 ;; global options: printcmd ;; connection timed out; no servers could be reached
While I realize you won't be hosting Google.com :), your name server should at least return an error of some sort (or correctly resolve the FQDN under most default bind configurations).
More troubleshooting could be done with the output of your firewall setup ("net ipfilter list", "ip addr", and "ip route"), and a couple of FQDN's that your DNS server should be authoratitive for...
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
