New Subnet and DNS problems

Can you detail a little bit the physical lay out of your network?
between the 192.168.0.x network and the 192.168.1.x network there has to be a router. I seams that this router don't let the DNS updates passing through.
Also do you have a reverse lookup zone in the DNS for the 192.168.0.x network, and is it updated?
It seams that the DNS is not able to find a PTR record for the 192.168.0.x workstations to map the IP address to the FQDN.

All client machines have a DNS Suffix Search Order. If you don't have your domain name listed, and generally if you're not a member of the domain you won't, then it will be unable to resolve the name without you typing in the FQDN. The same applies to resolution of the Domain Name itself.

Now if they were all on the same subnet, or rather, not seperated by a Firewall (which very probably doesn't relay broadcast traffic), then you probably wouldn't notice this as it falls back on NetBIOS resolution via Broadcast to pick up the names.

When you join the domain the Domain Name is configured on the PC and from then on it should happily be able to resolve by just computer name.

For registering in DNS you must make sure your DNS allows dynamic registration ("ipconfig /registerdns" will force a registration attempt) and of course make sure your Firewall allows the traffic through.

Hi,
As both previous posts indicate you have to have some sort of routing between your both subnets and a gateway address enterd in the workstations so that they can reach the router. You also have to open up ports for any traffic involved in intranet communication

The 192.168.0.x and the 192.168.1.x subnets are on the same router located in the same building.  Both the 1.x and 0.x are listed as secondary on the router.

I have a Reverse lookup zone setup for the 192.168.0.x and 192.168.1.x subnets

Like I said, i can join any workstation on the 192.168.1.x subnet by using the NetBios name (mydomain) with no DNS suffix attached

On the 192.168.0.x subnet (on the same local router and firewall) I have use the FQDN (mydomain.lcl) to join the Domain

If they're defined as seperate subnets the traffic goes through the router, regardless of whether or not the physical network is the same. Remember broadcast traffic is sent to the network broadcast address, i.e. 192.168.0.255 and 192.168.1.255 respectively.

If you had 192.168.0/23 then it wouldn't touch the router. But with 192.168.0/24 and 192.168.1/24 the router cannot be skipped - something has to tell the traffic where it's supposed to go.

So.... broadcast traffic will not be getting through unless you have set it up to relay on the router. And for anyone on the 192.168.0/24 network you either have to use the FQDN or give it a DNS suffix search list - both achieve the same end result.

I added 192.168.0.2 to the DC/DNS server1 and 192.168.0.3 to the DC/DNS server2

From a worktation not yet joined to the domain and with a 192.168.0.x IP address, I can ping both servers using IP addresses.  I cannont ping them using their NETBIOS names.  I can ping them using the FQDN

Even with the above configuration, I still cannot join the Domain using NETBIOS (mydomain) while on the 192.168.0.x subnet...only join the Domain by FQDN (mydomain.lcl)

We even have 7 other subnets (192.168.2.x, 3.x, 4.x, 5.x. 6.x, 7.x) in our WAN that can use (mydomain) instead of (mydomain.lcl) when joining the Domain.

Did you check the routing table on the switch to make sure that you do have a routing between the two subnets

Routing must be in place for pings and DNS traffic to get through.

I would still point the finger at no relaying of Broadcast traffic over the router.

Routing is definitely setup.  I had the router guy force broadcasts from the 192.168.0.x subnet to the 192.168.1.x subnet on the router....still no luck

Now with a secondary IP on each of the DC/DNS servers, I am getting an error message in Event Viewer that a duplicate name exists on the Network

One more thing...

When I added the secondary IPs to the Domain Controllers/DNS servers, the IPs (192.168.0.2, 192.168.0.3) registered themselves in DNS as Host (A) records and are set to update the associated PTR record....but in the Reverse Lookup 0.168.192.in-addr.arpa, the PTR record is not present.  The only records that are in the reverse lookup are the SOA and 2 NS.

Check on the properties of the reverse zone if and how do you allow dynamic updates, you must accept them, and select Nonsecure and secure or secure only depending on how you setup communications between your workstations and the server.
Also under Security check if you have the appropriate rights for authenticated users.
And finally on the workstations the dns settings must point the the new 192.168.0.x addresses on the servers.
In my network I have DHCP , and configured it to update the dns records both for forward and reverse zones, so a never had this kind o issues.

I wish we had DHCP, it would make my life 10x easier but for some reason my boss wants all static.  

Everything is setup in DNS correctly.  I did find out that the being that the 2 subnets are on the same router, the router is having issues with bassing NETBIOS from one subnet to the other.  If the 2 subnets were on different routers, it would be easier to accomplish.  I think for now, I am going to inform my people to just use the FQDN when joining anything to the Domain

Do you have enable NetBios over TCP/IP selected on the workstations?

FQDN is more secure...

Really it would be better (both in terms of security and network load) to deny broadcast over the routers.

A bit situational though...