In my server hosted in the US, I'm having problems with looking up some
domains.  What I noticed is that those domains with problems are the one
which I entered dns entries in dot ph's system as opposed to putting them
in some other dns server.

The wierd thing is that when I tried to change /etc/resolv.conf and use my
dns server, it does not resolve.  Using DIG and forcing @nameserver on the
command line gives me timeouts or blank A entries.

>From my local setup:

$ dig anvilexecutiveclub.ph

; <<>> DiG 9.2.1 <<>> anvilexecutiveclub.ph
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26567
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0

;; QUESTION SECTION:
;anvilexecutiveclub.ph.         IN      A

;; ANSWER SECTION:
anvilexecutiveclub.ph.  264     IN      A       203.167.64.14

;; AUTHORITY SECTION:
ph.                     172616  IN      NS      SEC3.APNIC.NET.
ph.                     172616  IN      NS      AUTH50.NS.UU.NET.
ph.                     172616  IN      NS      NS-EXT.ISC.ORG.
ph.                     172616  IN      NS      NS.RIPE.NET.

;; Query time: 50 msec
;; SERVER: 203.172.11.21#53(203.172.11.21)
;; WHEN: Sun Aug 29 13:19:01 2004
;; MSG SIZE  rcvd: 160


But while logged on to the US server:

> dig anvilexecutiveclub.ph

;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33673
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;anvilexecutiveclub.ph.         IN      A

;; Query time: 26 msec
;; SERVER: 66.70.216.113#53(66.70.216.113)
;; WHEN: Sun Aug 29 13:18:53 2004
;; MSG SIZE  rcvd: 39


>  dig anvilexecutiveclub.ph @203.172.11.21

; <<>> DiG 9.2.1 <<>> anvilexecutiveclub.ph @203.172.11.21
;; global options:  printcmd
;; connection timed out; no servers could be reached


> dig anvilexecutiveclub.ph @ns2.domains.ph

; <<>> DiG 9.2.1 <<>> anvilexecutiveclub.ph @ns2.domains.ph
;; global options:  printcmd
;; connection timed out; no servers could be reached


>  dig www.infocom.ph

; <<>> DiG 9.2.1 <<>> www.infocom.ph
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49363
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;www.infocom.ph.                        IN      A

;; ANSWER SECTION:
www.infocom.ph.         86400   IN      A       203.172.25.24

;; AUTHORITY SECTION:
infocom.ph.             259200  IN      NS      ns2.infocom.ph.
infocom.ph.             259200  IN      NS      ns3.infocom.ph.
infocom.ph.             259200  IN      NS      ns1.infocom.ph.


I guess my DNS lookup has a problem.  Question is where is this thing
getting stuck?  Traceroutes from the server to nsfwd and ns2.domains.ph are
ok.

Appreciate any suggestions.

God bless you.
William

--
 William Villanueva
 http://www.purity.ph
 PGP key ID 0xDF608588  Registered linux user #179111
==================================================
  Do what you love and love what you're doing, and you'll never work
another day in your life.


--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie

Reply via email to