BatchFile Posted December 2, 2010 Posted December 2, 2010 (edited) I'm having another exploratory foray into Ubuntu as a possible alternative to Windows for some of our workstations, as I'm looking into the feasibility of buying out of our MS School agreement next summer. I installed Ubuntu a while ago and it looks like it could be a go-er. but one thing's puzzling me: I can't get ip addresses of internal servers to resolve. Anything outside the school works fine (i've put the LEA proxy in as the network proxy) and software centre etc is fine, ie I can ping bbc.co.uk but not cpsfilesrv1 (a server on the network). Edit: adding 10.105.* (covering our internal range) to the "ignored hosts" list in the network proxy bit has no effect - is there something else I should be putting in there? DNS seems to be working fine for Windows workstations, just not Ubuntu. Terminal Server Client won't connect with a server name, but will happily with an IP address. Oddly, "Places-Connect To Server" DOES work with server names:confused: DNS security allows "ANONYMOUS LOGIN" read access and It's a vanilla Windows 2003 Network (for now)... any suggestions where to look (at either end)? Edited December 2, 2010 by BatchFile
dhicks Posted December 2, 2010 Posted December 2, 2010 I can't get ip addresses of internal servers to resolve. Is Ubuntu using the correct DNS server? How is the DNS server assigned, via DHCP or by static network settings? -- David Hicks
tom_newton Posted December 2, 2010 Posted December 2, 2010 You should be putting your internal domains in the "do not proxy for" list. Otherwise the DNS lookup gets done on-proxy. Lets step back a bit from web browsers tho - they confuse matters. Try: $ ping cpsfilesrv1 $ cat /etc/resolv.conf 1
BatchFile Posted December 2, 2010 Author Posted December 2, 2010 You should be putting your internal domains in the "do not proxy for" list. Otherwise the DNS lookup gets done on-proxy. Lets step back a bit from web browsers tho - they confuse matters. Try: $ ping cpsfilesrv1 $ cat /etc/resolv.conf that gives: tony@tony-laptop-linux:~$ ping cpsfilesrv1 ping: unknown host cpsfilesrv1 tony@tony-laptop-linux:~$ cat /etc/resolv.conf # Generated by NetworkManager search cps nameserver 10.105.16.10 nameserver 10.105.16.9 nameserver 10.96.0.2 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 10.64.0.2 The "nameserver"s are correct - the first two are internal, the others at the LEA
localzuk Posted December 2, 2010 Posted December 2, 2010 (edited) Why do you have your LEA nameservers being directed at your clients? They should be set up as forwarders on your DNS servers only, that way your DNS servers handle all traffic. Ie: Client -> DNS Request -> Internal DNS Server -> DNS request -> LEA DNS Server -> DNS Request -> Top level DNS server etc... Edited December 2, 2010 by localzuk 1
BatchFile Posted December 2, 2010 Author Posted December 2, 2010 Are you trying to resolve using the short name or fully qualified DNS name? If it works for FQDN but not for the short name, you could add the domain suffix in your network setup. I tried both, neither work
BatchFile Posted December 2, 2010 Author Posted December 2, 2010 (edited) Why do you have your LEA nameservers being directed at your clients? They should be set up as forwarders on your DNS servers only, that way your DNS servers handle all traffic. Damn good question... I didn't set that bit up - and now you ask I can't think of a good reason! Edit: I've removed them manually, and now it works :) Edited December 2, 2010 by BatchFile
localzuk Posted December 2, 2010 Posted December 2, 2010 If you try doing an nslookup (ie. nslookup cpsfilesrv1) what is returned. Then, if you do an nslookup Google, what do you get?
BatchFile Posted December 2, 2010 Author Posted December 2, 2010 glad to report that with the settings localzuk suggested, it's working - I configured them manually initially, but now have corrected the DHCP options too. Cheers all! I'm sure I'll be back when I hit the next mystery
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now