Domain not resolve but resolve with other ISP domain
Mark Andrews
Mark_Andrews at isc.org
Mon Dec 18 09:25:39 UTC 2006
> Any ideas because problem still with only one domain plastics4arab.com
>
>
> Regards,
> Mohammed Nayeem
I suspect you need to look at the packet level.
Run "tcpdump -n -p -s 0 host 75.126.81.155" in one window
Then in another window run
"dig +norec +dnssec plastics4arab.com @75.126.81.155"
and send the list what tcpdump produces.
Mark
> -----Original Message-----
> From: Nayeem [mailto:nayeem at ksa.zajil.com]
> Sent: Sunday, December 17, 2006 6:57 PM
> To: 'Andy Shellam (Mailing Lists)'
> Cc: 'bind-users at isc.org'
> Subject: RE: Domain not resolve but resolve with other ISP domain
>
> Dear Sir,
>
> You can see detail below what you reauest.
>
> [root at cd1 ~]# cat /etc/resolv.conf
> domain cd1.zajil.net
> nameserver 212.24.224.45
> nameserver 212.24.224.35
> search localdomain
> [root at cd1 ~]# dig @212.24.224.45 plastics4arab.com
>
> ; <<>> DiG 9.2.4 <<>> @212.24.224.45 plastics4arab.com
> ; (1 server found)
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
> [root at cd1 ~]# dig @212.24.224.35 plastics4arab.com
>
> ; <<>> DiG 9.2.4 <<>> @212.24.224.35 plastics4arab.com
> ; (1 server found)
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
> [root at cd1 ~]# dig @212.24.224.35 dns3.ksasun.com
>
> ; <<>> DiG 9.2.4 <<>> @212.24.224.35 dns3.ksasun.com
> ; (1 server found)
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
> [root at cd1 ~]# dig @212.24.224.35 google.com
>
> ; <<>> DiG 9.2.4 <<>> @212.24.224.35 google.com
> ; (1 server found)
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20416
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
>
> ;; QUESTION SECTION:
;google.com. IN A
>
> ;; ANSWER SECTION:
> google.com. 90 IN A 72.14.207.99
> google.com. 90 IN A 64.233.187.99
> google.com. 90 IN A 64.233.167.99
>
> ;; AUTHORITY SECTION:
> google.com. 34703 IN NS ns1.google.com.
> google.com. 34703 IN NS ns2.google.com.
> google.com. 34703 IN NS ns3.google.com.
> google.com. 34703 IN NS ns4.google.com.
>
> ;; ADDITIONAL SECTION:
> ns1.google.com. 87673 IN A 216.239.32.10
> ns2.google.com. 87665 IN A 216.239.34.10
> ns3.google.com. 87669 IN A 216.239.36.10
> ns4.google.com. 87661 IN A 216.239.38.10
>
> ;; Query time: 0 msec
> ;; SERVER: 212.24.224.35#53(212.24.224.35)
> ;; WHEN: Sun Dec 17 18:45:29 2006
> ;; MSG SIZE rcvd: 212
>
> Regards,
> Mohammed Nayeem
>
>
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf
> Of Andy Shellam (Mailing Lists)
> Sent: Sunday, December 17, 2006 6:34 PM
> To: Nayeem
> Cc: bind-users at isc.org
> Subject: Re: Domain not resolve but resolve with other ISP domain
>
> Recursion is as follows:
>
> When you query a non-recursive DNS server, it returns the answer from
> it's cache (if it has it), it's zone files (for zones it is
> authoritative for), or the servers you can query to get the answer.
> When you query a recursive DNS server, the server runs all the queries
> needed to get you (the client) the final answer, rather than leaving you
> to run other queries yourself to get the answer.
>
> So, if I queried "google.com" on a non-recursive server, it'd tell me to
> query the root nameservers.
> However, if I queried "google.com" on a recursive server, the server
> would query the root nameservers, and any others it needed to get me the
> record for google.com.
>
> I think that your machine's resolvers (in /etc/resolv.conf) aren't
> working, or you cannot reach them.
> To query a specific server, use "dig @<server IP> <query>" - so to query
> my machine 80.175.29.73 for google.com, I'd do "dig @80.175.29.73
> google.com".
>
> Try doing that for all the IP addresses listed in /etc/resolv.conf and
> post your results.
>
> Nayeem wrote:
> >
> > Dear Sir,
> >
> > I used this web site to test and got timeout when "no recursion" not check
> >
> >
> > It show answer when I check "no recursion"
> >
> >
> > So what "no recursion" will do ?
> >
> > Mohammed Nayeem
> >
> > -----Original Message-----
> > From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> > Behalf Of Nayeem
> > Sent: Sunday, December 17, 2006 6:09 PM
> > To: 'Andy Shellam (Mailing Lists)'
> > Cc: bind-users at isc.org
> > Subject: RE: Domain not resolve but resolve with other ISP domain
> >
> > Dear Sir,
> >
> > Thanks for reply
> >
> > You mean our machine 212.24.224.45 got problem or their (ksasun.com)
> >
> > machine?
> >
> > Sorry to ask that can to tell me how can I check DNS query against them ?
> >
> > Actually I try to use our 3 DNS servers but we got same result when I use
> >
> > other ISP DNS then how it resolved.
> >
> > Thanks,
> >
> > Regards,
> >
> > Mohammed Nayeem
> >
> > -----Original Message-----
> >
> > From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> > Behalf
> >
> > Of Andy Shellam (Mailing Lists)
> >
> > Sent: Sunday, December 17, 2006 5:58 PM
> >
> > To: Nayeem
> >
> > Cc: bind-users at isc.org
> >
> > Subject: Re: Domain not resolve but resolve with other ISP domain
> >
> > You've got a problem with that machine seeing the ksasun.com domain then
> >
> > by the looks of things.
> >
> > Check what resolvers that machine is using (in /etc/resolv.conf) and
> >
> > that they're all working OK (eg. you can run a DNS query against them.)
> >
> > Nayeem wrote:
> >
> > > Dear Sir,
> >
> > >
> >
> > > Thanks for the reply and I tried dig command and results mention below.
> >
> > >
> >
> > > [root at cd1 ~]# dig @dns3.ksasun.com plastics4arab.com
> >
> > > dig: couldn't get address for 'dns3.ksasun.com': failure
> >
> > > [root at cd1 ~]# dig @dns4.ksasun.com plastics4arab.com
> >
> > > dig: couldn't get address for 'dns4.ksasun.com': failure
> >
> > >
> >
> > > Regards,
> >
> > > Mohammed Nayeem
> >
> > >
> >
> > > -----Original Message-----
> >
> > > From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> >
> > Behalf
> >
> > > Of Andy Shellam (Mailing Lists)
> >
> > > Sent: Sunday, December 17, 2006 5:12 PM
> >
> > > To: Nayeem
> >
> > > Cc: bind-users at isc.org
> >
> > > Subject: Re: Domain not resolve but resolve with other ISP domain
> >
> > >
> >
> > > dig @dns3.ksasun.com plastics4arab.com
> >
> > > dig @dns4.ksasun.com plastics4arab.com
> >
> > >
> >
> > > According to the root nameservers (I queried g.gtld-servers.net),
> >
> > > dns3.ksasun.com and dns4.ksasun.com are authoritative for the domain
> >
> > > plastics4arab.com.
> >
> > > Running the above 2 queries from the console of your DNS server will
> >
> > > show if you have connectivity problems to those 2 servers - if you do,
> >
> > > then that's the problem.
> >
> > >
> >
> > > Andy.
> >
> > >
> >
> > > Nayeem wrote:
> >
> > >
> >
> > >> When I try other domains then it is resolved.
> >
> > >>
> >
> > >> ~]# nslookup
> >
> > >>
> >
> > >>
> >
> > >>> yahoo.com
> >
> > >>>
> >
> > >>>
> >
> > >> Server: 212.24.224.45
> >
> > >> Address: 212.24.224.45#53
> >
> > >>
> >
> > >> Non-authoritative answer:
> >
> > >> Name: yahoo.com
> >
> > >> Address: 216.109.112.135
> >
> > >> Name: yahoo.com
> >
> > >> Address: 66.94.234.13
> >
> > >>
> >
> > >>
> >
> > >>> cnn.com
> >
> > >>>
> >
> > >>>
> >
> > >> Server: 212.24.224.45
> >
> > >> Address: 212.24.224.45#53
> >
> > >>
> >
> > >> Non-authoritative answer:
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.16.116
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.24.12
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.24.20
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.24.28
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.29.120
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.16.20
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.16.52
> >
> > >> Name: cnn.com
> >
> > >> Address: 64.236.16.84
> >
> > >>
> >
> > >> Regards,
> >
> > >> Mohammed Nayeem
> >
> > >>
> >
> > >>
> >
> > >> -----Original Message-----
> >
> > >> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> >
> > >>
> >
> > > Behalf
> >
> > >
> >
> > >> Of Andy Shellam (Mailing Lists)
> >
> > >> Sent: Sunday, December 17, 2006 3:18 PM
> >
> > >> To: Nayeem
> >
> > >> Cc: bind-users at isc.org
> >
> > >> Subject: Re: Domain not resolve but resolve with other ISP domain
> >
> > >>
> >
> > >> It seems your DNS service is not running, not answering within the
> > usual
> >
> > >> 2 seconds that nslookup waits, or TCP/UDP port 53 is being blocked by a
> >
> > >> firewall between your client and DNS server.
> >
> > >>
> >
> > >>
> >
> > >> Nayeem wrote:
> >
> > >>
> >
> > >>
> >
> > >>> Dear All,
> >
> > >>>
> >
> > >>>
> >
> > >>> I'm new to Bind and today I face one problem that one domain
> >
> > >>> plastics4arab.com not resolve with our DNS server but resolve with
> >
> > >>>
> >
> > > another
> >
> > >
> >
> > >>> ISP DNS Server.
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> Presently we are using latest bind 9.2.4 DNS server on Redhat Linux
> Ent
> >
> > >>>
> >
> > >>>
> >
> > >> 4..
> >
> > >>
> >
> > >>
> >
> > >>>
> >
> > >>>
> >
> > >>> # nslookup
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>> plastics4arab.com
> >
> > >>>>
> >
> > >>>>
> >
> > >>>>
> >
> > >>> ;; connection timed out; no servers could be reached
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>> server ns1.shaheer.net.sa
> >
> > >>>>
> >
> > >>>>
> >
> > >>>>
> >
> > >>> Default server: ns1.shaheer.net.sa
> >
> > >>>
> >
> > >>> Address: 212.64.128.12#53
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>> plastics4arab.com
> >
> > >>>>
> >
> > >>>>
> >
> > >>>>
> >
> > >>> Server: ns1.shaheer.net.sa
> >
> > >>>
> >
> > >>> Address: 212.64.128.12#53
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> Non-authoritative answer:
> >
> > >>>
> >
> > >>> Name: plastics4arab.com
> >
> > >>>
> >
> > >>> Address: 75.126.81.155
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>> exit
> >
> > >>>>
> >
> > >>>>
> >
> > >>>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> When I use Dig Command
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> # dig plastics4arab.com
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> ; <<>> DiG 9.2.4 <<>> plastics4arab.com
> >
> > >>>
> >
> > >>> ;; global options: printcmd
> >
> > >>>
> >
> > >>> ;; connection timed out; no servers could be reached
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>> Can any one help us to solve this issue.
> >
> > >>>
> >
> > >>> Mohammed Nayeem
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>>
> >
> > >>
> >
> > >>
> >
> > >
> >
> > >
> >
> > >
> >
> > --
> >
> > Andy Shellam
> >
> > NetServe Support Team
> >
> > the Mail Network
> >
> > "an alternative in a standardised world"
> >
> > p: +44 (0) 121 288 0832/0839
> >
> > m: +44 (0) 7818 000834
> >
> > !DSPAM:37,4585604130869209412022!
>
>
> --
> Andy Shellam
> NetServe Support Team
>
> the Mail Network
> "an alternative in a standardised world"
>
> p: +44 (0) 121 288 0832/0839
> m: +44 (0) 7818 000834
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list