rndc flush

[Ladislav Vobr]

 >
 > The folllowing site could not resolve by our dns server.
 > 
www.ahwanepal.org,www.nepalkitchen.com,www.globalsimply.com,www.nsrd.com,por
 > talnepal.com,etc.
 > Not only these sites, even all the sites which are hoisted at 
69.50.215.33 .
 > After flush, it works for few hours and then stops, really irritating.
 >
 > Thank you for your swift help ,
 > Kind regards
 > eswari
 >
 >

Eswari, think about it a little. dns is distributed system. Argumenting 
by the fact that others can resolve it does not mean anything. Around 
the world each nameserver has cached the data at different times, and 
it's cached expired at different times, and gets updated again at 
different times. Seeing different answers from different caching servers 
is something you have to get use to it. In 99% of the cases there is 
nothing wrong with your caching server, only the particular domains has 
been updated/misconfigured/removed and distribution  of this fact is 
around the world is taking place.

I have checked nepalkitchen.com and what i see is that there is a 
delegation problem. .COM parent servers, delegates nepalkitchen.com to 
ns1.a1hosts.net. and ns2.a1hosts.net. nameserves, but the someone who 
defines and administers a1hosts.net domain forgets to mention them in 
the zone. This will lead exactly to this kind of problems, temporarily 
up/down.

nepalkitchen.com.       172800  IN      NS      ns1.a1hosts.net.
nepalkitchen.com.       172800  IN      NS      ns2.a1hosts.net.
;; Received 113 bytes from 192.5.6.30#53(a.gtld-servers.net) in 224 ms

dig a1hosts.net @l.gtld-servers.net.

; <<>> DiG 9.2.2 <<>> a1hosts.net @l.gtld-servers.net.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49845
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;a1hosts.net.                   IN      A

;; AUTHORITY SECTION:
a1hosts.net.            172800  IN      NS      ns1.a1hosts.net.
a1hosts.net.            172800  IN      NS      ns2.a1hosts.net.

;; ADDITIONAL SECTION:
ns1.a1hosts.net.        172800  IN      A       69.50.215.130
ns2.a1hosts.net.        172800  IN      A       69.50.215.131

;; Query time: 229 msec
;; SERVER: 192.41.162.30#53(l.gtld-servers.net.)
;; WHEN: Tue Dec 21 07:05:19 2004
;; MSG SIZE  rcvd: 97

$ dig ns1.a1hosts.net. @69.50.215.130

; <<>> DiG 9.2.2 <<>> ns1.a1hosts.net. @69.50.215.130
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60442
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.a1hosts.net.               IN      A

;; AUTHORITY SECTION:
a1hosts.net.            14400   IN      SOA     ns1.dnsrouter.com. 
root.tortuga.dnsrouter.com. 2004071906 14400 7200 3600000 86400

;; Query time: 298 msec
;; SERVER: 69.50.215.130#53(69.50.215.130)
;; WHEN: Tue Dec 21 07:05:49 2004
;; MSG SIZE  rcvd: 99

dig axfr a1hosts.net. @69.50.215.130

; <<>> DiG 9.2.2 <<>> axfr a1hosts.net. @69.50.215.130
;; global options:  printcmd
a1hosts.net.            14400   IN      SOA     ns1.dnsrouter.com. 
root.tortuga.dnsrouter.com. 2004071906 14400 7200 3600000 86400
a1hosts.net.            14400   IN      MX      0 a1hosts.net.
a1hosts.net.            14400   IN      NS      ns1.dnsrouter.com.
a1hosts.net.            14400   IN      A       69.50.215.130
ftp.a1hosts.net.        14400   IN      A       69.50.215.130
host.a1hosts.net.       14400   IN      A       69.50.215.130
www.host.a1hosts.net.   14400   IN      A       69.50.215.130
itti.a1hosts.net.       14400   IN      A       69.50.215.130
www.itti.a1hosts.net.   14400   IN      A       69.50.215.130
localhost.a1hosts.net.  14400   IN      A       127.0.0.1
mail.a1hosts.net.       14400   IN      CNAME   a1hosts.net.
www.a1hosts.net.        14400   IN      CNAME   a1hosts.net.
a1hosts.net.            14400   IN      SOA     ns1.dnsrouter.com. 
root.tortuga.dnsrouter.com. 2004071906 14400 7200 3600000 86400



this is the authoritative server for a1hosts.net. and as you can see it 
has no idea about ns1.a1hosts.net. and ns2.a1hosts.net. You have to add 
their A records here, another point you have single NS record here, it 
means everything stands and falls with this single nameserver....


Ladislav