dynamic update with ipv6 address

[Ramon Smits]

Hi all,

I have a DNS server and with DHCP clients I have dynamic registration.
But it does not register the AAAA ipv6 records. I am using DNS on a
Windows 2003 box.

Does dynamic registration only work with dhcp clients?

A clients that has a static configuration does not register itself on
the dns server. Also forcing it with "ipconfig /registerdns" does not
work either.

The server is a 2003 box and all clients are an ipaq 2210 pocketpc and
several Windows XP boxes.

Kind regards,
Ramon Smits

 

[Jonathan de Boyne Pollard]

RS> But it does not register the AAAA ipv6 records.

What reverse lookup "zones" do you have ?

RS> Does dynamic registration only work with dhcp clients?

The Microsoft DHCP Client service performs Dynamic DNS updates, but it does so
for all (specified) IP addresses, irrespective of whether they were obtained
via DHCP. This is stated in the product documentation.

RS> A clients that has a static configuration does not register
RS> itself on the dns server.

And so did you check that the machine is actually granted access to perform
dynamic updates in the first place ?

 

[Michael Johnston [MSFT]]

Clients should be able to register dynamically on their own. Verify in the advanced properties of TCP/IP on the DNS tab, that
Regsiter this connection's addresses in DNS is checked. Next, verify the primary DNS suffix on the client matches that of the
zone you want the client to regsiter in. The primary DNS suffix on Windows 2000 and XP is found in the properties of My
Computer on the "Network Identification" tab for W2k and "Computer Name" tab for XP. Click the Change button, then click More.
Lastly, verify on the DNS that the zone allows secure and non-secure updates. The clients should only be pointing at the DNS
server that is hosting this zone.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Ramon Smits]

RS> But it does not register the AAAA ipv6 records.

What reverse lookup "zones" do you have ?

I don't have a reverse lookup zone for my ipv4 address only for ipv6
which is

3.5.9.1.8.8.8.0.1.0.0.2.ip6.arpa.dns

Why is this relevant? Do you need a reverse lookup zone for dynamic
registration?

RS> Does dynamic registration only work with dhcp clients?

The Microsoft DHCP Client service performs Dynamic DNS updates, but it does so
for all (specified) IP addresses, irrespective of whether they were obtained
via DHCP. This is stated in the product documentation.

Yes I knew that is should support it but it does not in my configuration .

RS> A clients that has a static configuration does not register
RS> itself on the dns server.

And so did you check that the machine is actually granted access to perform
dynamic updates in the first place ?

Is is part of a domain of my LAN and I have nonsecure updates enabled on
the forward zone.

If I run the client with DHCP then it does register it's ipv4 A record
but is does not do the AAAA ipv6 records.

When run with a static configuration it does not register it's A and
AAAA records.


Kind regards,
Ramon Smits

 

[Ramon Smits]

Clients should be able to register dynamically on their own. Verify in the advanced properties of TCP/IP on the DNS tab, that
Regsiter this connection's addresses in DNS is checked. Next, verify the primary DNS suffix on the client matches that of the
zone you want the client to regsiter in. The primary DNS suffix on Windows 2000 and XP is found in the properties of My

Yes the DNS suffix that I use is 'lan.exyll.net' and is delegated to
nameserver.exyll.net which manages the forward lookup zone. As said in
another post in this thread it does register it's A record when DHCP is
used but not its AAAA. It used in a static configuration is does not
register both.

Computer on the "Network Identification" tab for W2k and "Computer Name" tab for XP. Click the Change button, then click More.
Lastly, verify on the DNS that the zone allows secure and non-secure updates. The clients should only be pointing at the DNS
server that is hosting this zone.

The clients use DNS server 10.0.0.55 which is the same as
nameserver.exyll.net and indeed allows non-secure updates.


Kind regards,
Ramon Smits

 

[Rahul Indurkar [MS]]

As far as I know the PocketPC OS doesn't do dynamic registrations. I might
be wrong on this...

The WindowsXP clients should be registering both A and AAAA in a domain
config. Can you check the system eventlog to see if there any errors
relating to those registrations failing?

 

[Ramon Smits]

As far as I know the PocketPC OS doesn't do dynamic registrations. I might
be wrong on this...

I have enabled that in the DNS options of the Windows2003 box and the
pocketpc device is registered when it obtaince an address with dhcp.

The WindowsXP clients should be registering both A and AAAA in a domain
config. Can you check the system eventlog to see if there any errors
relating to those registrations failing?

hmm something that I had not thought of.

The eventlog on the server does not have entries related to registration
of clients. The clients do have an error like the following:

========================================================================
The system failed to register network adapter with settings:

Adapter Name : {3AD04A6F-B8EA-4A8F-A965-EDD1A23C2A3B}
Host Name : venus
Adapter-specific Domain Suffix : lan.exyll.net
DNS server list :
10.0.0.55
Sent update to server : <?>
IP Address(es) :
10.0.0.51

The cause of this DNS registration failure was because of DNS server
failure. This may be due to a zone transfer that has locked the DNS
server for the applicable zone that your computer needs to register
itself with.

(The applicable zone should typically correspond to the
Adapter-specific Domain Suffix that was indicated above.) You can
manually retry registration of the network adapter and its settings by
typing "ipconfig /registerdns" at the command prompt. If problems still
persist, contact your network systems administrator to verify network
conditions.
========================================================================

The thing I noticed is the line "Sent update to server : <?>". I assume
that at <?> should be the hostname of the dns server? The ip address
underneath (10.0.0.51) is the correct host.

Kind regards,
Ramon