Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Tim Jones on September 12, 2003, 04:10:58 AM
-
Hi Folks,
Under SME 5.6U4, we have added local systems to our server via the server-manager. The entries all look correct - i.e.:
anvil.tolisgroup.com Local Local 192.168.1.6
I've also checked /home/dns/db.tolisgroup.com and the entry exists:
anvil IN A 192.168.1.6
However, neither the SME server nor any client can resolve the anvil machine. Any attempt to 'dig' anvil results in:
bash-2.05a# dig anvil
; <<>> DiG 8.3 <<>> anvil
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;; anvil, type = A, class = IN
;; AUTHORITY SECTION:
. 3H IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. (
2003091101 ; serial
30M ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
;; Total query time: 121 msec
;; FROM: G4-1.local. to SERVER: default -- 192.168.1.1
;; WHEN: Thu Sep 11 16:06:57 2003
;; MSG SIZE sent: 23 rcvd: 98
This is incorrect as the SME named had (for some reason) sent the resquest through to the root server for resolution. We do have a forwarder setup in the named.conf file that points to our ISP's name server.
nsswitch is set to files dns
the resolve.conf is the default created by the templates
Can someone provide pointers as to what further troubleshooting can be done to resolve (pun intended) this issue? It's tough to operate when we have to remember the IP addresses (or manually install /etc/hosts files).
Tim Jones
TOLIS Group, inc.
-
Tim Jones wrote:
> We do have a forwarder setup in the named.conf file that points
> to our ISP's name server.
That's almost always the wrong thing to do. So much so that in latest development versions of the console we've removed that dialog. Let the SME server resolve all names.
Charlie
-
Hi Charlie,
That did it. I removed the upstream resolver and voila!
Thanks,
Tim
(of course, while we'll probably never know - why did it work under 5.1.2 with a forwarder defined?)