Resolving a domain
Andy Shellam (Mailing Lists)
andy.shellam-lists at mailnetwork.co.uk
Sun Dec 17 16:00:30 UTC 2006
Is your server authoritative for that domain?
If not, try querying the authoritative server directly.
Rasheed Darras wrote:
> All servers in /etc/resolv.conf working and I have only problem with this
> domain.
>
> # dig @localhost arishost.com
>
> ; <<>> DiG 9.3.0 <<>> @localhost arishost.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> Localhost will not work because I'm having in named.conf:-
>
> listen-on { 212.93.192.4; };
>
> # dig ns.com a
>
> ; <<>> DiG 9.3.0 <<>> ns.com a
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 638
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;ns.com. IN A
>
> ;; ANSWER SECTION:
> ns.com. 3600 IN A 216.193.241.178
>
> ;; AUTHORITY SECTION:
> ns.com. 172799 IN NS ns2.ns.com.
> ns.com. 172799 IN NS ns0.ns.com.
> ns.com. 172799 IN NS ns1.ns.com.
>
> ;; Query time: 836 msec
> ;; SERVER: 212.93.192.4#53(212.93.192.4)
> ;; WHEN: Sun Dec 17 18:44:29 2006
> ;; MSG SIZE rcvd: 94
>
> Rasheed
>
>
> -----Original Message-----
> From: Andy Shellam (Mailing Lists)
> [mailto:andy.shellam-lists at mailnetwork.co.uk]
> Sent: Sunday, December 17, 2006 6:37 PM
> To: Rasheed Darras
> Cc: bind-users at isc.org
> Subject: Re: Resolving a domain
>
> Check the servers listed in /etc/resolv.conf are working, or try "dig
> @localhost arishost.com"
>
> Rasheed Darras wrote:
>
>> Dears,
>>
>>
>> I have problem resolving domain arishost.com. I'm unable to get it
>> despite I can use their DNS to resolve the domain.
>>
>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>>
>> # dig @dns1.arishost.com arishost.com a
>>
>> ; <<>> DiG 9.3.0 <<>> @dns1.arishost.com arishost.com a ;; global
>> options: printcmd ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1835 ;; flags: qr
>> aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
>>
>> ;; QUESTION SECTION:
>> ;arishost.com. IN A
>>
>> ;; ANSWER SECTION:
>> arishost.com. 1800 IN A 69.28.157.196
>>
>> ;; AUTHORITY SECTION:
>> arishost.com. 1800 IN NS dns1.arishost.com.
>> arishost.com. 1800 IN NS dns2.arishost.com.
>> arishost.com. 1800 IN NS dns3.arishost.com.
>> arishost.com. 1800 IN NS dns4.arishost.com.
>>
>> ;; ADDITIONAL SECTION:
>> dns1.arishost.com. 1800 IN A 208.64.200.100
>> dns2.arishost.com. 1800 IN A 208.64.200.101
>> dns3.arishost.com. 1800 IN A 208.64.200.100
>> dns4.arishost.com. 1800 IN A 208.64.200.101
>>
>> ;; Query time: 177 msec
>> ;; SERVER: 208.64.200.100#53(dns1.arishost.com)
>> ;; WHEN: Sun Dec 17 18:05:20 2006
>> ;; MSG SIZE rcvd: 186
>>
>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>>
>> # dig dns1.arishost.com a
>>
>> ; <<>> DiG 9.3.0 <<>> dns1.arishost.com a ;; global options: printcmd
>> ;; connection timed out; no servers could be reached
>>
>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>>
>> # dig www.arishost.com a
>>
>> ; <<>> DiG 9.3.0 <<>> www.arishost.com a ;; global options: printcmd
>> ;; connection timed out; no servers could be reached
>>
>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>>
>>
>> I dump my DNS cache and found the following:-
>>
>> arishost.com. 172033 NS dns1.arishost.com.
>> 172033 NS dns2.arishost.com.
>> 172033 NS dns3.arishost.com.
>> 172033 NS dns4.arishost.com.
>> dns1.arishost.com. 171978 A 208.64.200.100
>> dns2.arishost.com. 171978 A 208.64.200.101
>> dns3.arishost.com. 172033 A 208.64.200.100
>> dns4.arishost.com. 172033 A 208.64.200.101
>> etedm.com. 171978 NS dns1.arishost.com.
>> 171978 NS dns2.arishost.com.
>> ; dns2.arishost.com [v4 TTL -17] [v4 success] [v6 unexpected] ;
>> dns2.arishost.com [v4 TTL -53] [v4 success] [v6 unexpected] ;
>> dns1.arishost.com [v4 TTL -17] [v4 success] [v6 unexpected] ;
>> dns1.arishost.com [v4 TTL -53] [v4 success] [v6 unexpected] ;
>> dns4.arishost.com [v4 TTL -17] [v4 success] [v6 unexpected] ;
>> dns3.arishost.com [v4 TTL -17] [v4 success] [v6 unexpected]
>>
>> What could be the reason cause this problem?
>>
>> Rasheed
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> 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,458567af30862053840820!
>
>
>
--
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
More information about the bind-users
mailing list