VMWare and Connecting Sessions

I'm doing a lab that requires a partner, so I've set up two VMWare sessions. I've set the static IP addresses of those to 192.168.1.3 and 192.168.1.4. I've installed DNS on both sessions and have them up to be Primary Zones. The lab is asking me to create a secondary zone, so I'm trying to connect to my other VMWare session. From my one VMWare session (192.168.1.3), I try to do this but after I create the secondary zone for 192.168.1.4, and click on the Forward Lookup Zone, I get the following error:

Zone Not Loaded by DNS Server

At first I thought it might be because the two sessions aren't seeing one another, but I am able to ping 192.168.1.4 from the other session, and vice versa, so it looks like they're able to see one another.

Right now both sessions are set to use Bridged Networking.

Thanks in advance!

Find more posts tagged with

Comments

dynamik

Are these machines domain controllers?

Are you using Active Directory-Integrated Zones?

Have you allowed zone transfers to the correct machines (if necessary)?

What do you see in your event logs under DNS?

Johnny Johnson

dynamik wrote: »

Are these machines domain controllers?

Are you using Active Directory-Integrated Zones?

Have you allowed zone transfers to the correct machines (if necessary)?

What do you see in your event logs under DNS?

Neither machine is a domain controller.

Neither machine is using an AD-Integrated Zone.

I was getting an Event ID 6525, which has to do with Zone Transfers.

I had never set the 2nd machine up to Allow Zone Transfers to any server.

Now I'm getting an event log that says that the DNS Server successfully completed a transfer.

Thanks for pointing me in the right direction!

Update: Now I'm having issues with the following exercise. I've set my preferred DNS server to the IP address of the local area connection, like the lab says. When I try to perform a NSLOOKUP, it gives me the following:

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.3: Timed out
Default Server: Unknown
Address: 192.168.1.3

Any ideas?

dynamik

Johnny Johnson wrote: »

Thanks for pointing me in the right direction!

Johnny Johnson wrote: »

Update: Now I'm having issues with the following exercise. I've set my preferred DNS server to the IP address of the local area connection, like the lab says. When I try to perform a NSLOOKUP, it gives me the following:

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.3: Timed out
Default Server: Unknown
Address: 192.168.1.3

Any ideas?

It looks like it's trying to do a reverse lookup for 192.168.1.3. Have you created any reverse-lookup zones?

Johnny Johnson

dynamik wrote: »

NP

It looks like it's trying to do a reverse lookup for 192.168.1.3. Have you created any reverse-lookup zones?

I haven't tried to create any reverse lookup zones since the lab hasn't instructed me to yet.