DNS problem in VMware Solaris 10
Mohun Biswas
on Windows XP (long story: need to demo a Solaris tool and plan to do so
on a Windows laptop using VMware). This is not exactly supported but
I've got it working pretty well.
But there remains a problem with DNS. My guess is it's not related to
the VMware "bridged networking" but just a regular dumb Unix
configuration mistake. The symptom is that I can't resolve remote
hostnames using the regular resolver, but nslookup and dig can! Isn't
that strange? Here's an example, with my internal IP changed:
% dig mirror.unixheads.com
; <<>> DiG 8.4 <<>> mirror.unixheads.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18404
;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; mirror.unixheads.com, type = A, class = IN
;; ANSWER SECTION:
mirror.unixheads.com. 15M IN A 24.94.148.201
;; Total query time: 392 msec
;; FROM: vmsol10 to SERVER: 10.xx.xx.xx
;; WHEN: Tue Oct 5 11:15:54 2004
;; MSG SIZE sent: 38 rcvd: 54
% ping mirror.unixheads.com
ping: unknown host mirror.unixheads.com
% pkg-get -a
WARNING: no catalog file for site mirror.unixheads.com
Updating catalog file first
Getting catalog...
--11:24:36-- http://mirror.unixheads.com/csw/unstable/i386/5.10/catalog
=> `catalog.1'
Resolving mirror.unixheads.com... failed: Host not found.
ERROR: could not get catalog file
As you can see, I'm trying to get to a blastwave mirror to get the rest
of the tools I need.
I've done all the config by hand since it's a special environment: I set
/etc/defaultrouter to contain "10.xx.xx.xx", changed /etc/nsswitch.conf
to say "network: files dns", and put the following in /etc/recolv.conf:
domain mydomain.com
# comcast.net nameservers
216.148.227.79
204.127.202.19
# Internal
nameserver 10.xx.xx.xx
What did I miss?
--
Thanks,
M.Biswas
Darren Dunham
> the VMware "bridged networking" but just a regular dumb Unix
> configuration mistake. The symptom is that I can't resolve remote
> hostnames using the regular resolver, but nslookup and dig can! Isn't
> that strange?
No. On Solaris, 'nslookup' is a dns-only debugging tool. It will
always use the /etc/resolv.conf file for DNS interpretation.
Other tools (such as 'getent', and 'ping') will use /etc/nsswitch.conf
to determine resolver configuration.
> I've done all the config by hand since it's a special environment: I set
> /etc/defaultrouter to contain "10.xx.xx.xx", changed /etc/nsswitch.conf
> to say "network: files dns", and put the following in /etc/recolv.conf:
Oops. I think you mean
hosts: files dns
The 'networks' database is for resolution of the information normally
found in /etc/networks. Not hostname resolution.
--
Darren Dunham ddu...@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Mohun Biswas
> Mohun Biswas <m.bi...@invalid.addr> wrote:
>>the VMware "bridged networking" but just a regular dumb Unix
>>configuration mistake.
>
> hosts: files dns
Thanks. At least I was right that it was just a regular dumb Unix admin
mistake!
--
M.Biswas