On Thu, 23 Jul 2009 21:27:23 -0500
Harry Putnam <[email protected]> wrote:
[...]
> However all of a sudden I cannot resolve alphabetic internet
> addresses. While numeric works.
>
> Well right away I think there is something wrong with the resolver but
> I've made no changes there. So maybe something else is involved in
> resolving. I've made no intentional changes in /etc/nsswitch.conf
> either. And don't think it has been involved anyway.
nsswitch.conf is definitely involved in name resolution. It tells you
which methods to use? Look at 'grep hosts /etc/nsswitch.conf'.
>
> cat /etc/resolv.conf:
> # Comcast name server
> nameserver 68.87.72.130
>
> # Local gateway router
> nameserver 192.168.0.20
>
> Resolving on the internet fails like so:
>
> # ping ftp.ucsb.edu
> ping: unknown host ftp.ucsb.edu
>
> But the numeric address of ftp.ucsb.edu works.
>
> # ping 128.111.24.43
> 128.111.24.43 is alive
>
> So it has to be something to do with resolving...
> How can I debug this.
Start out at nsswitch.conf and then make sure that the methods you have
configured would 1) return the data you need and 2) are configured
correctly (for example of dns is in the set then look at resolv.conf).
Use dig, route, etc. in the above.
>
> svcs -a |grep physical shows:
> # svcs -a |grep physical
> disabled 21:24:05 svc:/network/physical:default
> online 21:24:43 svc:/network/physical:nwam
>
> I've also tried restarting physical:default... which appears to make
> no difference. Ditto for physical:nwam.
These are mutually exclusive. Restarting something that is disabled
has no effect.
mph
>
>
> _______________________________________________
> networking-discuss mailing list
> [email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
