[users] DNS problems

Kanwar Ranbir Sandhu m3freak at thesandhufamily.ca
Tue Sep 11 23:41:28 CEST 2007


Hi,

I'm having problems resolving apt.sw.be.  Something is wrong with the
name servers.
(sorry for the messed up formatting - copied from a pidgin session with
a co-worker
that was helping me debug the problem):

DNS Lookup: apt.sw.be A record 
Email link to resultsGenerated by www.DNSstuff.com at 21:22:46 GMT on 11
Sep 2007. 

How I am searching: 

Searching for apt.sw.be A record at h.root-servers.net [128.63.2.53]:
Got referral to amsterdam.ns.dns.be. (zone: be.) [took 38 ms] 
Searching for apt.sw.be A record at amsterdam.ns.dns.be.
[193.194.136.30]: Got referral to ns1.3ti.be. (zone: sw.be.) [took 134
ms

Searching for apt.sw.be A record at ns1.3ti.be. [212.204.216.221]:
Reports that dag.freshrpms.net. does not exist. [took 121 ms] Response:
apt.sw.be. exists, and is a CNAME pointing to dag.freshrpms.net., which
does not exist Details: apt.sw.be. exists, and is a CNAME pointing to
dag.freshrpms.net., which does not exist. This is a very unusual
response, and indicates that the DNS server is authoritative for both
apt.sw.be. and dag.freshrpms.net. and that while apt.sw.be. exists, it
knows that dag.freshrpms.net. does not exist. See RFC2308 2.1 for
details.

(05:36:39 PM) Afzan: amsterdam.ns.dns.be refers you to ns1.3ti.be which
is broken
(05:37:03 PM) Afzan: prague.ns.dns.be refers you to ns1.borderfield.be
which is working
(05:37:29 PM) Afzan: so depending which one you get pointed to by the
root servers, you will either get a good ip or not

Hope that helps resolve the problem.

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 2.6.22.2-42.fc6 i686 GNU/Linux 
17:23:59 up 11 days, 15:49, 2 users, load average: 1.24, 1.19, 1.11 




More information about the users mailing list