On Mon, 26 Aug 2002, Andre John Cruz wrote:
>
> dig @ns1.pacific.net.ph intergate.com.ph mx
> and it just ends with a timeout. i tried @ns2.pacific.net.ph too and nothing
> happens either.
first, i thought it was policy, (you shouldnt allow non-customers to use
your nameservers for recursive queries on domains you dont host) but then
dig @ns2.pacific.net.ph intergate.com.ph ns
yielded the ff:
intergate.com.ph. 14h41m28s IN NS k.intergate.com.ph.
intergate.com.ph. 14h41m28s IN NS www.intergate.com.ph.
intergate.com.ph. 14h41m28s IN NS latte.intergate.com.ph.
intergate.com.ph. 14h41m28s IN NS arabica.intergate.com.ph.
all except k.intergate.com.ph resolves to an IP addr. so therefore 'k'
will be unreachable. and maybe, Pacific's nameserver got stuck at
k.intergate.com.ph (and is not cycling to the other NS) so it cant get at
your MX addresses.
pong
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
