<snip>
>
> not certain if you intend it to be, but your 64.135.16.15 machine is
> not reachable from "outside". an attempt to telnet to port 53 (or 25)
> gets me "no route to host" and a traceroute ends with:
>
> 8 ge2-0.cr1.bct.fl.host.net (64.135.1.9) 34.779ms 35.102ms 35.413ms
> 9 ge6-1.er8.bct.fl.host.net (64.135.1.58) 34.934ms 34.219ms 35.044ms
> 10 sunspot.swhi.net (64.135.16.15) 34.653 ms !<10> 34.619 ms !<10>
>
> 35.739 ms !<10>
>
> so, from the outside, it appears that you have a firewall block (or
> network configuration problem).
>
> my read is that the block is at the machine, not an edge router, so
> this may be the source of your problem.
>
> try doing a telnet to port 53 on 64.135.16.15 (based on past messages i
> think that that's the correct ipnumber) from some local machine and see
> what you get. if it's listening you should get a connect message (even
> if there are access restrictions in named.conf). if you get something
> else, that should give a hint on where to look.
>
>
> - Rick
>
>
Hi Rick,
Telnetting on port 53 from a machine in the same /24 gives this:
[ray@wh1 ray]$ telnet 64.135.16.15 53
Trying 64.135.16.15...
telnet: connect to address 64.135.16.15: No route to host
Thanks for your input. I welcome any suggestions.
Kind regards,
~Ray
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
