Danny Angus <Danny_Angus <at> slc.co.uk> writes: > 1/ because it doesn't delegate lookups > 2/ because it might also be stymied by your firewall > 3/ because your paranoid network admins won't let you. > > Look at the operating system NS settings on the server.
The firewall is also the DNS and DHCP server and the DNS address supplied to my machine is 10.0.0.138. When I do a dig for the dodgy domain the DNS server indeed has no answer for it. When I dig with a different DNS server it does return the correct answer. So it seems that case 1/ is correct. > Can you do an nslookup (or whatever) for the dodgy domain? > If so use that DNS server IP instead. > If not try to find one that does work. > If not you're kind-of stuck. > > I assume that A and MX records do actually exist for the domain? > Yes the records exist. I don't know much about DNS so I was wondering why programs such as browsers have no problem using this "caching" DNS server which does not resolve recursive lookups but James does. John. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
