Re: Linux DNS Client Against Windows 2000 DNS Server

From: Robert A. Reissaus (r.a.reissaus_at_risdi.com)
Date: 06/15/04 

Date: 15 Jun 2004 05:19:21 -0700

I have, more or less, the same problem. Only I am using WYP Sp1a Which
doesn't the Windows->Linux problem. But I do have the same problem
between SuSE 9.1 and SuSE 9.0. I believe it is caused by SuSE 9.1
using only IPv6 and addressing interfaces by a hardware address
instead of an interface name. I say this because after having
installed SuSE 9.1 Pro on another machine the problem no longer exists
between those two. I am not sure about WY2K, but the problem would
probably go away if you there would be a IPv6 path.

(b.t.w. I noticed that I suddenly have another route added (to
169.254.0.0 -> to internal card) which has nothing to do with my
network; do you have the same?)

Regards,
Robert A. Reissaus
r.a.reissaus@risdi.com
IBM/Informix Consultants fot the BeNeLux 

---
daniel.rigal@ntlworld.com (Daniel Rigal) wrote in message news:<4171a413.0406140820.7e6c879b@posting.google.com>...
> Hi everybody,
> 
> How weird is this?
> 
> I installed a Linux server for the company Intranet (SuSE 9.1 Pro) and
> gave it a static IP address. I set up the Linux box to use our Windows
> 2000 Active Directory server for its DNS and that is where it gets
> weird. It almost works. DNS works fine as far as external (internet)
> addreses are concerned. They are resolvable and pingable. It is only
> internal addresses which are problematic and even these are only
> partially broken. "nslookup" works fine on an internal address when
> run from the linux box. "host" works fine too. "dig" only works if you
> give it a fully qualified domain name to look up but fails on an
> unqualified one. The really annoying thing is that the command line
> utilities like "ping" can't resolve internal addresses at all, whether
> they are fully qualified or not, which makes life rather difficult.
> 
> Before anybody asks, I don't think I have done anything stupid setting
> it up. There is only one DNS server listed and nsswitch.conf is set up
> to use DNS for host resolution.
> 
> Does anybody have a clue what could be going on? Does anybody else
> have similar issues, or must I have done something silly to mess it
> up? I know that people mistrust the Windows 2000 DNS server but, given
> that "nslookup" and "host" can resolve against it, you would think
> that everything else could too? Do they use different methods to query
> the DNS server?
> 
> Any suggestions for resolving this would be appreciated.
> 
> Regards,
> 
> Daniel Rigal MSc.

Relevant Pages

  • Re: Is this a split / shadow situation resolving non routable IPs without DNS authourity.
    ... Active Directory root zone is abccompany.com inside the firewall. ... This DNS server then uses forewarders to resolve Internet ...
    (microsoft.public.win2000.dns)
  • Re: conditional forwarding configuration issues
    ... > default during Win2000 setup when no Internet connection ... > if all internal clients are Domain Windows machines. ... I want to continue to resolve these internal namespaces as I have ... >> clients that are using this DNS server to be able to get to these web ...
    (microsoft.public.windows.server.dns)
  • Re: DNS resolving !!
    ... Your internal server can not resolve external addresses. ... And these will froward the answers to your internal dns server which will passw the info to the clients. ... but i have couple of external DNSs that act ... external DNSs to resolve it from the internet ...
    (microsoft.public.windows.server.networking)
  • Re: Is this a split / shadow situation resolving non routable IPs without DNS authourity.
    ... External is abc-company.com DNS server for abc-company.com is in our DMZ as well as that web host. ... (This is the single example, reality is there are multiple externals def-company.com, ghi-company.com) ... This DNS server then uses forewarders to resolve Internet ...
    (microsoft.public.win2000.dns)
  • Re: Can use unternet explorer using ics
    ... Could be a dns problem. ... your internal dns server - a domain controller would need to be able ... to resolve internet names via the use of a forwarder or using root hints. ...
    (microsoft.public.windows.server.networking)