Discussion:
Solaris 10 x86 u9 DNS problems
(too old to reply)
Andy
2012-02-02 08:43:33 UTC
Permalink
Dear all,
I have an ADSL connexion with a router adr. at 192.168.1.1 so I
configured nameserver 192.168.1.1 in resolv.conf
I get the following results:
# dig 192.168.1.1 ec.eurecom.fr ANY

; <<>> DiG 9.6.1-P3 <<>> 192.168.1.1 ec.eurecom.fr ANY
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;192.168.1.1. IN A

;; ANSWER SECTION:
192.168.1.1. 395 IN A 86.35.3.193
192.168.1.1. 395 IN A 86.35.3.192

;; Query time: 20 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Feb 2 17:51:45 2012
;; MSG SIZE rcvd: 61

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 294
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;ec.eurecom.fr. IN ANY

;; ANSWER SECTION:
ec.eurecom.fr. 172800 IN CNAME eclipse.eurecom.fr.

;; AUTHORITY SECTION:
eurecom.fr. 172800 IN NS dns.eurecom.fr.
eurecom.fr. 172800 IN NS ns6.enst.fr.

;; Query time: 121 msec
;; SERVER: 193.231.236.17#53(193.231.236.17)
;; WHEN: Thu Feb 2 17:51:47 2012
;; MSG SIZE rcvd: 94

# ping 86.35.3.193
86.35.3.193 is alive
# ping 86.35.3.192
86.35.3.192 is alive
# ping ec.eurecom.fr
ping: unknown host ec.eurecom.fr
So why solaris cannot resolve domain names?
Andy
Chris Ridd
2012-02-02 12:09:08 UTC
Permalink
Post by Andy
# ping ec.eurecom.fr
ping: unknown host ec.eurecom.fr
So why solaris cannot resolve domain names?
ping doesn't use DNS directly, it uses the NSS. That's configured by
/etc/nsswitch.conf - check to see that the hosts line in there includes
"dns". (There might be an /etc/nsswitch.dns file you can copy over, or
use as a guide.)
--
Chris
Andy
2012-02-02 12:52:33 UTC
Permalink
Post by Chris Ridd
Post by Andy
# ping ec.eurecom.fr
ping: unknown host ec.eurecom.fr
So why solaris cannot resolve domain names?
ping doesn't use DNS directly, it uses the NSS. That's configured by
/etc/nsswitch.conf - check to see that the hosts line in there includes
"dns". (There might be an /etc/nsswitch.dns file you can copy over, or
use as a guide.)
--
Chris
Your suggestion worked perfectly for me. Thank you.
Andy

Loading...