Re: Name Resolution

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: don'tspam (kmarinelli_at_nationalticket.com.(don'tspam))
Date: 02/03/05 

Date: Thu, 3 Feb 2005 12:09:05 -0800

I have 2 domains. Domain 1 is an NT domain, domain 2 is a Windows 2003
domain. The are both on the same physical segment (hubs/switches?). I
have a trust setup between the 2 domains. I am using a multi-homed Windows
2003 Server as a router between the two domains (See below). I do have ip
routing enabled on the server.

My NT domain (Domain 1) is using Wins for name resolution on its local
domain, the DNS server is pointing to our ISP. On the Windows 2003 domain
(Domain 2) our local name resolution is using our DNS Active Directory Server
and anything outside our domain is being forwarded to our ISP. I do have a
forwarder set up.

I can ping anything by ip address on either domain, from either domain. My
problem is Domain 1 can't ping Domain 2 by name, and vice versa

Sorry that I wasn't clear on my last post.

Thank you.

"Yor Suiris" wrote:

> Are ALL Clients/Servers using YOUR DNS server for nAlame resolution?
> Does YOUR DNS server have Zones/Entries for both LANs?
> When you do nslookup from LAN1 what DNS server does it connect too?
> When you do nslookup from LAN2 what DNS server does it connect too?
>
> You say you have a Trust between the Two LANs, does this mean Two Domains?
> Are they both AD? Do they each have Their Own DNS Server and/or Zone files?
> (If Yes, then make each a secondary for the other).
> What is in-between the LANs (How do they connect)? Does this junction allow
> all traffic or is it restricted in any way?
>
>
> --
> Yor Suiris
> Remove the kNOT to reply.
> But it is best to share it with the group.
>
>
>
>
>
> "Kim" <kmarinelli@nationalticket.com.(don'tspam)> wrote in message
> news:8DC210F2-DC42-4B7D-AB3A-2E09F6A3FA28@microsoft.com...
> > My local DNS server is setup on the multi-homed Windows 2003 server. I
> > have
> > a forwarder set up for name resolution of internet names. Both lans can
> > access the internet however Lan 2 can't resolve Lan 1 client machines.
> > Lan 1
> > has the wins server and that is where I'm pointing everything to. I have
> > a
> > trust setup between Lan 1 and Lan 2
> >
> > Thanks
> >
> > "Yor Suiris" wrote:
> >
> >> More likely DNS then WINS. Do not confuse Internet DNS with MS AD DNS.
> >> Point all your Clients at "Your" DNS server not one outside your system.
> >> Your AD Dynamic DNS should be set to forward to your ISPs DNS (only place
> >> on
> >> your system that should have an external DNS entry) and every thing else
> >> DNS
> >> related gets pointed to "Your" AD Dynamic DNS server/s.
> >> I would put a DNS server on each LAN and make each a secondary to the
> >> other.
> >> So all DNS info is availed on each LAN. And you have a backup if one
> >> fails.
> >> --
> >> Yor Suiris
> >> Remove the kNOT to reply.
> >> But it is best to share it with the group.
> >>
> >>
> >> "Kim" <kmarinelli@nationalticket.com.(don'tspam)> wrote in message
> >> news:8F442F0F-4830-4DFD-ABE4-ACE66120ED84@microsoft.com...
> >> >I have two lans set up on the same segment. MY lan 2 clients can ping
> >> > everything on Lan 1 but can't do name resolving. I think its a Wins
> >> > issue
> >> > and am not sure what to do. I have my current configuration below.
> >> > Does
> >> > anyone know what my problem is. I do not have a Wins Server on the
> >> > 2003
> >> > Server, this is why I'm pointing everything to the Lan 1 Wins Server
> >> >
> >> >
> >> > pix firewall 192.168.100.254 ip address
> >> >
> >> > Lan 1 clients 192.168.100.x
> >> > 192.168.100.224 default gateway
> >> > 192.168.100.202 Wins Server
> >> > DNS is pointing to outside source
> >> >
> >> > Multi-homed Windows Server 2003 with routing enabled & DNS enabled for
> >> > local
> >> > domain
> >> > 192.168.100.224
> >> > NIC 1 192.168.100.254 default gateway
> >> > 192.168.100.202 Wins Server
> >> >
> >> > 192.168.200.201
> >> > NIC 2 blank default gateway
> >> > 192.168.100.202 Wins Server
> >> >
> >> > Lan 2 clients 192.168.200.x
> >> > 192.168.200.201 default gateway
> >> > 192.168.100.202 Wins Server
> >> > 192.168.200.201 DNS Server for local domain
> >> >
> >> > Thanks,
> >> >
> >> > Kim
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Relevant Pages

  • Re: Cannot get access to router on SBS server
    ... point the DNS server setting to the IP of the SBS ... calling CNetCommit::ValidateFulltimeConnectionProperties. ... Call to Reading web publishing selection returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: Herb Martin...Global Catalog SRV record missing!
    ... Error: Root hints list has invalid root hint server: ... DNS server: 128.63.2.53 ... PTR record query for the ...
    (microsoft.public.windows.server.dns)
  • [UNIX] Hardening the BIND DNS Server
    ... Hardening the BIND DNS Server ... Your Domain Name Service is the road sign to your systems on the Internet. ...
    (Securiteam)
  • Re: NTDS Inbound neighbos removal
    ... There is no primary WINS server defined for this adapter. ... There is no secondary WINS server defined for this adapter. ... PASS - All the DNS entries for DC are registered on DNS server ... Upper Component: NWLink SPX/SPXII Protocol ...
    (microsoft.public.windows.server.active_directory)
  • RE: Server 2003 Network problems since IP address change
    ... Is there any firewall running on client or server? ... DNS server contacted refused the update request. ... zone WSW.local. ...
    (microsoft.public.windows.server.networking)