Cannot get ip address of mx record kienhwa.hk
Barry Margolin
barmar at alum.mit.edu
Wed Aug 9 04:23:16 UTC 2006
In article <eb9p3q$8oe$1 at sf1.isc.org>,
Peter Dambier <peter at peter-dambier.de> wrote:
> Asking my local nameserver did only find an SOA record.
That's because you did a query for type ANY. ANY does not mean "all"
unless you're querying the authoritative server (or if the server you're
querying doesn't have any records for the name cached, since it will
have to go to the authoritative server). It means "send me any records
you currently have cached".
Since kienhwa.hk's MX records have 0 TTL, they will never be cached.
>
>
> ; <<>> DiG 9.1.3 <<>> -t any kienhwa.hk.
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48737
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN ANY
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 600 IN SOA NS1.OGDNS.COM. NS1.OGDNS.COM.
> 1 10800 3600 86400 0
>
> ;; Query time: 1008 msec
> ;; SERVER: 192.168.48.227#53(192.168.48.227)
> ;; WHEN: Tue Aug 8 11:18:00 2006
> ;; MSG SIZE rcvd: 77
>
>
> Asking for HK. to find the nameservers got me
>
> ;; Truncated, retrying in TCP mode.
> ;; Connection to 192.168.48.2#53(192.168.48.2) for hk. failed: connection
> refused.
>
>
> I have 3 local resolvers using BIND 9.4.0, djbdns and as last resort the DNS
> server of my DSL-router who is querying my ISP. So I shall try again
>
>
> ;; Truncated, retrying in TCP mode.
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34537
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 15, ADDITIONAL: 7
>
> ;; QUESTION SECTION:
> ;hk. IN ANY
>
> ;; ANSWER SECTION:
> hk. 602829 IN NS NS2.CUHK.EDU.hk.
> hk. 602829 IN NS B.DNS.TW.
> hk. 602829 IN NS TLD3.ULTRADNS.ORG.
> hk. 602829 IN NS NS1.HKIRC.NET.hk.
> hk. 602829 IN NS ADNS2.BERKELEY.EDU.
> hk. 602829 IN NS TLD4.ULTRADNS.ORG.
> hk. 602829 IN NS NS3.CUHK.EDU.hk.
> hk. 602829 IN NS NS2.HKIRC.NET.hk.
> hk. 602829 IN NS TLD5.ULTRADNS.INFO.
> hk. 602829 IN NS TLD1.ULTRADNS.NET.
> hk. 602829 IN NS TLD2.ULTRADNS.NET.
> hk. 602829 IN NS SEC3.APNIC.NET.
> hk. 602829 IN NS ADNS1.BERKELEY.EDU.
> hk. 602829 IN NS TLD6.ULTRADNS.CO.UK.
> hk. 602829 IN NS NS-HK.RIPE.NET.
> hk. 26829 IN SOA NS1.HKIRC.NET.hk.
> HOSTMASTER.HKIRC.NET.hk. 2006080816 21600 1800 3600000 600
>
> ;; AUTHORITY SECTION:
> hk. 602829 IN NS TLD4.ULTRADNS.ORG.
> hk. 602829 IN NS TLD6.ULTRADNS.CO.UK.
> hk. 602829 IN NS TLD5.ULTRADNS.INFO.
> hk. 602829 IN NS ADNS1.BERKELEY.EDU.
> hk. 602829 IN NS NS-HK.RIPE.NET.
> hk. 602829 IN NS NS1.HKIRC.NET.hk.
> hk. 602829 IN NS TLD3.ULTRADNS.ORG.
> hk. 602829 IN NS TLD1.ULTRADNS.NET.
> hk. 602829 IN NS TLD2.ULTRADNS.NET.
> hk. 602829 IN NS NS2.HKIRC.NET.hk.
> hk. 602829 IN NS NS3.CUHK.EDU.hk.
> hk. 602829 IN NS SEC3.APNIC.NET.
> hk. 602829 IN NS B.DNS.TW.
> hk. 602829 IN NS ADNS2.BERKELEY.EDU.
> hk. 602829 IN NS NS2.CUHK.EDU.hk.
>
> ;; ADDITIONAL SECTION:
> ADNS1.BERKELEY.EDU. 171608 IN A 128.32.136.3
> NS2.CUHK.EDU.hk. 58082 IN A 137.189.6.21
> NS2.CUHK.EDU.hk. 58082 IN AAAA 2001:ce0:3:6::21
> NS2.HKIRC.NET.hk. 5903 IN A 203.119.2.19
> NS3.CUHK.EDU.hk. 58082 IN A 202.45.188.19
> SEC3.APNIC.NET. 160658 IN A 202.12.28.140
> SEC3.APNIC.NET. 160658 IN AAAA 2001:dc0:1:0:4777::140
>
> ;; Query time: 150 msec
> ;; SERVER: 192.168.48.227#53(192.168.48.227)
> ;; WHEN: Tue Aug 8 11:56:24 2006
> ;; MSG SIZE rcvd: 793
>
>
> People with broken routers or firewalls might have given up already.
>
> Now lets find about your email.
>
>
> ; <<>> DiG 9.1.3 <<>> -t any kienhwa.hk. @ADNS1.BERKELEY.EDU
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57212
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN ANY
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 28800 IN NS NS2.OGDNS.COM.
> kienhwa.hk. 28800 IN NS NS1.OGDNS.COM.
>
> ;; Query time: 216 msec
> ;; SERVER: 128.32.136.3#53(ADNS1.BERKELEY.EDU)
> ;; WHEN: Tue Aug 8 11:40:08 2006
> ;; MSG SIZE rcvd: 73
>
>
> Berkley has found you. Now your nameservers again
>
> ; <<>> DiG 9.1.3 <<>> -t any kienhwa.hk. @NS2.OGDNS.COM.
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59129
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN ANY
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 1800 IN SOA NS2.OGDNS.COM. NS2.OGDNS.COM.
> 1 10800 3600 86400 0
>
> ;; Query time: 360 msec
> ;; SERVER: 202.134.124.67#53(NS2.OGDNS.COM.)
> ;; WHEN: Tue Aug 8 11:41:25 2006
> ;; MSG SIZE rcvd: 90
>
>
> That is not good. No A record. No MX record. No way to send you emails.
>
>
> ; <<>> DiG 9.1.3 <<>> -t mx kienhwa.hk.
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37515
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN MX
>
> ;; ANSWER SECTION:
> kienhwa.hk. 0 IN MX 10 kienhwa.hk.
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 86400 IN NS NS2.OGDNS.COM.
>
> ;; ADDITIONAL SECTION:
> NS2.OGDNS.COM. 169843 IN A 202.134.124.67
>
> ;; Query time: 407 msec
> ;; SERVER: 192.168.48.227#53(192.168.48.227)
> ;; WHEN: Tue Aug 8 12:07:17 2006
> ;; MSG SIZE rcvd: 87
>
>
> Ok, I could find your MX record, but I am shure my mailer
> would not have found it.
>
> ; <<>> DiG 9.1.3 <<>> -t AAAA kienhwa.hk.
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9808
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN AAAA
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 600 IN SOA NS2.OGDNS.COM. NS2.OGDNS.COM.
> 1 10800 3600 86400 0
>
> ;; Query time: 390 msec
> ;; SERVER: 192.168.48.227#53(192.168.48.227)
> ;; WHEN: Tue Aug 8 12:08:03 2006
> ;; MSG SIZE rcvd: 77
>
>
> Even if my mailer had tried it, it would give up now.
>
> ; <<>> DiG 9.1.3 <<>> -t A kienhwa.hk.
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37398
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
>
> ;; QUESTION SECTION:
> ;kienhwa.hk. IN A
>
> ;; ANSWER SECTION:
> kienhwa.hk. 0 IN A 202.134.124.67
>
> ;; AUTHORITY SECTION:
> kienhwa.hk. 86349 IN NS NS2.OGDNS.COM.
>
> ;; ADDITIONAL SECTION:
> NS2.OGDNS.COM. 169792 IN A 202.134.124.67
>
> ;; Query time: 400 msec
> ;; SERVER: 192.168.48.227#53(192.168.48.227)
> ;; WHEN: Tue Aug 8 12:08:07 2006
> ;; MSG SIZE rcvd: 87
>
>
> Only by trying all steps manually could I find it.
>
> Dont grow gray hairs with bind 8 any longer.
> It is not worth the trouble.
>
> Try and get BIND 9.4.0b1
> It can be downloaded from
>
> ftp://ftp.isc.org/isc/bind9/9.4.0b1/bind-9.4.0b1.tar.gz
>
> I have tried bind-9.4.0 from the beginning. I did not see any
> problems. I think bind-9.4.0b1 is much easier to use than
> trying to fix Bind 8.
>
> Of course you can try 9.3.2 that is stable. But taking the
> lastest might save you some updates and other headaches.
>
> Kind regards
> Peter and Karin
>
>
>
> Alex Tang wrote:
> > Hi All
> >
> > Sometimes my user cannot send email to kienhwa.hk.
> > I find out that the dns server cannot get the ip
> > address of the mx record at the same time.
> >
> >
> >>set q=mx
> >>kienhwa.hk
> >
> > Server: dns
> > Address:
> >
> > kienhwa.hk mail exchanger = 10 kienhwa.hk.
> >
> > but I can get the ip address of the mx by enter the host name only
> >
> >
> >>set q=a
> >>kienhwa.hk
> >
> > Server: dns
> > Address:
> >
> > Name: kienhwa.hk
> > Address: 202.134.124.67
> >
> > also the ttl of the domain is 0
> >
> >
> >>set q=soa
> >
> > origin = NS1.OGDNS.COM
> > mail addr = NS1.OGDNS.COM
> > serial = 1
> > refresh = 10800
> > retry = 3600
> > expire = 86400
> > minimum = 0
> >
> > What cause the problem ?
> > My bind version is 8.3.7
> >
> > Help Help
> >
> > Thx
> >
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list