Patience my boy - patience .... $ dig www.sit.sg @ns1.jsyctech.com
; <<>> DiG 9.5.0-P1 <<>> www.sit.sg @ns1.jsyctech.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22380 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.sit.sg. IN A ;; ANSWER SECTION: www.sit.sg. 14400 IN A 203.211.140.170 ;; AUTHORITY SECTION: sit.sg. 14400 IN NS ns2.jsyctech.com. sit.sg. 14400 IN NS ns1.jsyctech.com. ;; Query time: 14 msec ;; SERVER: 203.211.140.170#53(203.211.140.170) ;; WHEN: Thu Aug 28 09:11:00 2008 ;; MSG SIZE rcvd: 92 $ dig www.sit.sg @165.21.83.88 ; <<>> DiG 9.5.0-P1 <<>> www.sit.sg @165.21.83.88 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45771 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.sit.sg. IN A ;; ANSWER SECTION: www.sit.sg. 14400 IN A 203.211.140.170 ;; Query time: 39 msec ;; SERVER: 165.21.83.88#53(165.21.83.88) ;; WHEN: Thu Aug 28 09:11:16 2008 ;; MSG SIZE rcvd: 44 On Wed, 2008-08-27 at 23:41 +0800, Yong Han wrote: > but i am the "admin" of the server > > On Wed, Aug 27, 2008 at 11:35 PM, Rui Boon <[EMAIL PROTECTED]> wrote: > Yong Han wrote: > > hi, > > > > i have some problem where all the new domain that i have > registered > > does not work yet all the existing domain is still working. > > > > > see a domain : sit.sg <http://sit.sg> (you can check the > domain info: > > www.sgnic.com.sg <http://www.sgnic.com.sg/>) > > > > but the existing one is still working. > > > > any idea? > > > > some try out: > > > > Hi Yong Han, > > > It seems that jsyctech.com could not able to resolve as well. > > Since sit.sg's record points to ns1/ns2.jsyctech.com as the > dns server, > it is likely that the dns server is not functioning correctly. > The > servers are currently acting as relay servers, but not as an > authoritative servers (which is what you want). If the dns > server is > running on Red Hat/CentOS or related OS, it is likely that the > administrator has updated bind recently. This may cause the > server to go > into default non-authoritative mode. To resolve this, you will > have to > contact the dns server administrator. > > > Cheers > > Rui Boon > > > _______________________________________________ > Slugnet mailing list > [email protected] > http://wiki.lugs.org.sg/LugsMailingListFaq > http://www.lugs.org.sg/mailman/listinfo/slugnet _______________________________________________ Slugnet mailing list [email protected] http://wiki.lugs.org.sg/LugsMailingListFaq http://www.lugs.org.sg/mailman/listinfo/slugnet
