Re: dig problem - acting strange

2 msg	Views
2 msg	Vounerability if master dies - redundancy neede...
3 msg	How to disable DNS updates on LINUX server?
1 msg	[Fwd: Strange named-checkzone behaviour] - erro...
7 msg	DNS Lookup Outsourcing?
2 msg	Strange named-checkzone behaviour
6 msg	BIND and MS DNS
2 msg	migrating from mydns to bind9.4/DLZ extensions
1 msg	DH help
1 msg	Setting up DH key exchange
3 msg	Creating bogus response for a particular subnet
8 msg	'Stealing' an outside domain within a LAN

dig problem - acting strange
\ mmccaws2 (20 Nov 2006)
. \ Kevin Darcy (21 Nov 2006)

4 msg	domains on the same host, same IP, same nameser...
20 msg	I need to manage multiple domains
6 msg	root nameserver has stale entry
2 msg	named connection failed
3 msg	mutiple dns servers
2 msg	I need to start migrating to a new domain (DNS/...
6 msg	bind forward to rbldns server intermittently fails

Subject:	Re: dig problem - acting strange
Group:	Bind-users
From:	Kevin Darcy
Date:	21 Nov 2006

mmccaws2 wrote:
> Hi I thought it was working fine when I installed it 2005, but I kept
> getting this error message
>
>
> ; <<>> DiG 9.3.2 <<>> www.metrokc.gov.
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> So I upgrade to the one above., 9.3.2
>
> I still get that message
>
> my resolv.conf file has
> nameserver {ip address}
>
> Then I tried
>
> dig @{ip address} www.metrokc.gov.
>
> and it works.
>
> so is this a path problem, or do I have to run a flag for resolv.conf
> to be found?
>
>
No, dig will use /etc/resolv.conf by default. Do you perchance have
@{some other address} in your ~/.digrc? That would override the
/etc/resolv.conf default.

- Kevin