Problem w/ DNS Dynamic Registration Resolved

I'm having trouble in VirtualBox with a client which is a server 2003 being able to register itself in DNS with its A/PTR records. Below are the troubleshooting steps/things I've noticed.. Does anybody know what is going wrong here? Thanks in advance.

DNS server and client can only ping by IP and not by NAME.

I think reason is b/c no A record exists for client on DNS server.

Checked client make sure has correct dns suffix. it is using dns server
as its preferred server also.

Tried doing ipconfig /registerdns cmd on client 1 however A/PTR records
are not showing up properly. Even restarted client few times still
A/PTR records are not registering.

Made sure on the DNS server its forward/reverse lookups zone set to allow
dynamic updates.

Book suggested I run some kind of dndcmd to allow
dynamic updates on all zones on the dns server however it does not work
and just says something like unable to update the registry.

Using Virtual box with internal network mode both server/client on same
internal network. Tried switching to bridge networking however same result

As soon as I delete the A/PTR records off the dns server neither can ping
by name again.

DnsApi Warning in Event Log related to client failure to dynamic register
RRs (Resource Recrds) The Event ID is: 11164 reffering to that either
the authoritative zone does not permit dynamic updates or the DNS server
does not support the protocol needed for dynamic updates.

Find more posts tagged with

SAVE $250 on Your Microsoft Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Microsoft Boot Camps

Comments

mrmcmint

Not sure i understand the scenario properly.
When you say "I'm having trouble in VirtualBox with a client which is a server 2003 being able to register itself in DNS with its A/PTR records"

Why is a server trying to register its own a records? Have i understood this properly? Does it have a ns and soa record in dns of its own? what happens when you run a netdiag /fix?

it might also be worth enabling dns debugging and checking the logs.

Could you post an ipconfig /all of a client and a server on the same domain?

can you ping using fqdn?

Is it possible that a firewall is blocking dns activity? - on the back of this try and telnet to port 53 of the server from a client pc.

what is assigning ip's on your network?

cisco_trooper

Make sure the box has permissions on the DNS record.

win2k8

Sorry about the confusion. Let me explain my set up:

1)Virtual machine running server 2003 acting as client (192.168.0.1 255.255.255.0)
In a workgroup.
Primary DNS Suffix: domain1.local
Preferred DNS Server set to: 192.168.0.2 255.255.255.0)

2) Virtual machine running server 2003 acting as dns server. (192.168.0.2 255.255.255.0)
In a workgroup.
Primary DNS Suffix: domain1.local
Preferred DNS server set to: 127.0.0.1

This server host primary zones for domain1.local for both forward and reverse lookup.

All I'm trying to do is have the client update its records to the DNS server by creating an A record automatically like its suppose to register dynamically.

win2k8

mrmcmint

not too sure how this would work to be honest as they are in a workgroup. try changing 127.0.0.1 to 192.168.0.2 firstly, although i dont see really how the client has any sort of permissions to add the record to the dns server. do the client and the server both have the same username/password? if so it should pass through ok.

does the domain1.local domain actually exist as a domain?

cisco_trooper

For Dynamic DNS to function you will have to have AD-integrated DNS Zones if I remember correctly.

win2k8

Here is an output of netdiag /v cmd from the client machine: (it says DNS registration fail which I already know but does not mention any reason why). Also I was searching on google and I found something that mentioned that clients do not dynamically register to top-level domains by default or something of that like not sure. Still trying to find out the solution but i guess this is good troubleshooting incase something like this happens in a production environment.

Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Failed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Connection
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
Testing redirector and browser... Passed
Testing trust relationships... Skipped
Testing Kerberos authentication... Skipped
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.

Computer Name: COMPUTER2
DNS Host Name: COMPUTER2.domain1.local
DNS Domain Name: domain1.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 17 Model 3 Stepping 1, AuthenticAMD
Hotfixes :
Installed? Name
Yes Q147222

Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

Description: AMD PCNET Family PCI Ethernet Adapter
Device: \DEVICE\{1E577BEA-1CB1-4E18-892A-7435F3022A66}

Media State: Connected

Device State: Connected
Connect Time: 00:02:10
Media Speed: 100 Mbps

Packets Sent: 54
Bytes Sent (Optional): 0

Packets Received: 6
Directed Pkts Recd (Optional): 4
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[PASS] - At least one netcard is in the 'Connected' state.

Per interface results:

Adapter : Local Area Connection
Adapter ID . . . . . . . . : {1E577BEA-1CB1-4E18-892A-7435F3022A66}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : COMPUTER2.domain1.local
Description. . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
Physical Address . . . . . : 08-00-27-5D-86-7B
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.0.2
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.0.1

IpConfig results . . . . . : Passed

AutoConfiguration results. . . . . . : Passed
AutoConfiguration is not in use.

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}
COMPUTER2 <00> UNIQUE REGISTERED
WORKGROUP <00> GROUP REGISTERED
COMPUTER2 <20> UNIQUE REGISTERED
WORKGROUP <1E> GROUP REGISTERED
WORKGROUP <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

No remote names have been found.

WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.
IPX test : IPX is not installed on this machine.

Global results:

IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No

Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Standalone Server
Netbios Workgroup name . . . . : WORKGROUP
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : Administrator
Logon Domain . . . . . . . . . : COMPUTER2

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}
1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed
PASS - you have at least one non-autoconfigured IP address

IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.

Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.

NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 10
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :6
Description: RSVP TCP Service Provider
Provider Version :6
Max message size : Stream Oriented
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{A6CB6723-4CAB-458A-8A2C-E7577FA67881}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{A6CB6723-4CAB-458A-8A2C-E7577FA67881}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{35C8B466-4125-4997-B9EF-2E677E86AF50}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{35C8B466-4125-4997-B9EF-2E677E86AF50}] DATAGRAM 2
Provider Version :2

Max UDP size : 65507 bytes

DNS test . . . . . . . . . . . . . : Passed
Interface {1E577BEA-1CB1-4E18-892A-7435F3022A66}
DNS Domain: domain1.local
DNS Servers: 192.168.0.1
IP Address: Expected registration with PDN (primary DNS domain name):
Hostname: COMPUTER2.domain1.local.
[WARNING] Cannot find a primary authoritative DNS server for the name
'COMPUTER2.domain1.local.'. [ERROR_TIMEOUT]
The name 'COMPUTER2.domain1.local.' may not be registered in DNS.

Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{1E577BEA-1CB1-4E18-892A-7435F3022A66}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Skipped

DC list test . . . . . . . . . . . : Skipped

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Skipped

LDAP test. . . . . . . . . . . . . : Skipped

Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
No persistent route entries.

Netstat information test . . . . . : Passed

Interface Statistics

Received Sent
Unicast Packets 10356 11270
Non-unicast packets 44 42
Discards 0 0
Errors 0 0
Unknown protocols 0 458284

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 1342730730
Output Queue Length = 0

Interface index = 65539
Description = AMD PCNET Family PCI Ethernet Adapter
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 08-00-27-5D-86-7B
Administrative Status = 1
Operational Status = 1
Last Changed = 1342731179
Output Queue Length = 0

Active Connections

Proto Local Address Foreign Address State
TCP COMPUTER2:epmap COMPUTER2.domain1.local:49316 LISTENING
TCP COMPUTER2:microsoft-ds COMPUTER2.domain1.local:39054 LISTENING
TCP COMPUTER2:1027 COMPUTER2.domain1.local:222 LISTENING
TCP COMPUTER2:1028 COMPUTER2.domain1.local:38942 LISTENING
TCP COMPUTER2:netbios-ssn COMPUTER2.domain1.local:39150 LISTENING
UDP COMPUTER2:microsoft-ds *:*
UDP COMPUTER2:1025 *:*
UDP COMPUTER2:ntp *:*
UDP COMPUTER2:1026 *:*
UDP COMPUTER2:ntp *:*
UDP COMPUTER2:netbios-ns *:*
UDP COMPUTER2:netbios-dgm *:*

IP Statistics

Packets Received = 81
Received Header Errors = 0
Received Address Errors = 0
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 81
Output Requests = 95
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 0
Reassembly Successful = 0
Reassembly Failures = 0
Datagrams successfully fragmented = 0
Datagrams failing fragmentation = 0
Fragments Created = 0
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60

TCP Statistics

Active Opens = 1
Passive Opens = 1
Failed Connection Attempts = 0
Reset Connections = 2
Current Connections = 0
Received Segments = 20
Segment Sent = 20
Segment Retransmitted = 0
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120,000
Maximum Number of Connections = -1

UDP Statistics

Datagrams Received = 43
No Ports = 11
Receive Errors = 0
Datagrams Sent = 58

ICMP Statistics

Received Sent
Messages 17 17
Errors 0 0
Destination Unreachable 1 1
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 8 8
Echo Replies 8 8
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0

Bindings test. . . . . . . . . . . : Passed
Component Name : Network Monitor Driver
Bind Name: NM
Binding Paths:
Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Monitor Driver
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanbh
Upper Component: Network Monitor Driver
Lower Component: WAN Miniport (Network Monitor)

Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Component Name : Point to Point Protocol Over Ethernet
Bind Name: RasPppoe
Binding Paths:
Owner of the binding path : Point to Point Protocol Over Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Point to Point Protocol Over Ethernet
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Component Name : Point to Point Tunneling Protocol
Bind Name: mspptp
Binding Paths:

Component Name : Layer 2 Tunneling Protocol
Bind Name: msl2tp
Binding Paths:

Component Name : Remote Access NDIS WAN Driver
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Direct Parallel

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPPOE)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPTP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (L2TP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS Async Adapter

Component Name : Message-oriented TCP/IP Protocol (SMB session)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)

Component Name : Internet Protocol (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)

Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)

Component Name : WebClient
Bind Name: WebClient
Binding Paths:

Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:

Component Name : Network Load Balancing
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:

Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:

Component Name : Dial-Up Client
Bind Name: msrascli
Binding Paths:

Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : File and Printer Sharing for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : File and Printer Sharing for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)

Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: AMD PCNET Family PCI Ethernet Adapter

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)

Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:

Component Name : Application Layer Gateway
Bind Name: ALG
Binding Paths:

Component Name : WAN Miniport (Network Monitor)
Bind Name: NdisWanBh
Binding Paths:

Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Direct Parallel
Bind Name: {34785048-EB49-4321-BCF3-247118F4BBC4}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {C3C864E8-1C49-4C8F-A5F4-47182AA147F1}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {B7CEF058-AFDE-4629-9B31-1CFAB6E8C21E}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {F6E4E5AD-F7D1-4F06-9CD1-6AA0AF782174}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {48D8ABF3-34F5-4F3F-ADCE-01D87FD042C6}
Binding Paths:

Component Name : AMD PCNET Family PCI Ethernet Adapter
Bind Name: {1E577BEA-1CB1-4E18-892A-7435F3022A66}
Binding Paths:

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully

win2k8

I figured it out.... It was in fact because It was a top level domain "domain1.local" and I remember reading on some website that clients do not register by default for top-level domains you have go and change some registry setting or something. But anyways to test this theory, I created a new primary zone called test.domain1.local, and added this suffix to the connection list on the client and when I checked back on the primary zone the A record was automatically registered. I cant believe the Microsoft book does not mention anything about this and expects the records to be registered dynamically even though they suggested using the name domain1.local unless of course they made a correction.

Thanks again for everyone for helping. Now I can continue on with the book with peace if mind and go ahead with the next part of the lab.

win2k8

mrmcmint

Glad you found the solution! Thanks for letting us know.

win2k8

Just to let everyone know I figured out this afternoon it had nothing to do with the dns suffix etc.. The ultimate fix was just to delete the primary zone and recreate it, though I chose my own name rather than domain1.local I chose testlab.local instead. And everything works, I still havent a clue why it didnt work first time maybe corrupt zone or something? LOL. Anyways I thought i post the correct fix so not to confuse people about what the fix was. So in short if it does not work the first time delete it and and start over he he.

dynamik

Sorry I didn't see this sooner. You should have used dcdiag instead of netdiag. The /testdns switch would have given you a lot more info and the /fix might have taken care of the problem automatically.

mrmcmint

dynamik wrote: »

Sorry I didn't see this sooner. You should have used dcdiag instead of netdiag. The /testdns switch would have given you a lot more info and the /fix might have taken care of the problem automatically.

dynamik - could you clear something up for my poor confused brain? i thought dcdiag was for use on domain controllers, this setup is a workgroup... or have i got my wires crossed here?

Thanks!!

dynamik

Yea, you're right. I just skimmed since he said it was resolved; I missed that.

To the OP, just curious, what is your dynamic DNS security setting set at?

mrmcmint

Cool no worries - just thought I had better check and make sure I hadn't misunderstood something!