dig problem - acting strange

[Kevin Darcy]

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