Client not registering DNS

[Kevin]

Hi

We use a VPN (outsourced) for traveling users. When users log in remotely,
their "VPN"
IP get's registered in our DNS. However, for some reason when they come
back into the office, their IP does not always get updated in our DNS
server. It still has the old IP from when they were on the VPN client the
night before. Even if I do an "ipconfig /flushbns" it still does not
update. I have to delete the record and then do an "ipconfig /flushdns" to
fix it.

I can't figure out why their DNS record is not updating when they log in
at the office. I did verify they are booting up on the network (not in
standby or hibernate).

Any ideas?

Kevin

[WILDPACKET]

After flushdns do you do ipconfig/resgisterdns?

[steve_t]

When you say that the IP isn't getting updated, do you mean that the clients
are not creating valid DNS records, or that the old records are still being
listed in DNS?

"It still has the old IP from when they were on the VPN client the night
before"

Is this referring to the IP address of the workstation or the DNS records
for the workstation on the DNS server? Can the clients communicate on the
network when they boot up on the network?

The ipconfig/flushdns command flushes the DNS resolver cache on the local
client, so it won't do anything w/DNS records on the server. You could try
ipconfig/registerdns on the client, which will refresh the client's DHCP
lease and re-register the DNS names on the server.

Steve

[Kevin D. Goodknecht Sr. [MVP]]

When the client registers through the VPN, is the registration being done by
the client machine, or a DHCP server?
If it is a DHCP server, what OS is the DHCP server(s).
If all DHCP server are Win2k3, you should create a dedicated user account
with a non-expiring password, then on the Properties sheet of the DHCP
server, select the Advanced tab, click the Credentials button and enter
these credentials. Then Configure the DHCP server to always update DNS and
update DNS for DHCP clients that do not request updates. Then turn off DDNS
on the DNS tab of DHCP client's TCP/IP properties. This will force the DHCP
server to register all records which gives the DHCP server ownership of
dynamic records.
For existing dynamic records you can either delete them, or take ownership
of the record, on the properties sheet of the record, Security tab, Advanced
button, owner tab, select other account add the user account used by the
DHCP server, click apply. (Must be done on the Win2k3 server itself)

One other thing you can do is add this setting to the default domain GPO.

Computer Configuration
-Administrative templates
-Network
-DNS Client
+Replace Addresses in conflict (Enable)

This setting is designed for computers that register A resource records in
DNS zones that do not support Secure Dynamic Update. Secure Dynamic Update
preserves ownership of resource records and does not allow a DNS client to
overwrite records that are registered by other computers.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

[Kevin]

Yes. I meant /registerdns.

Thanks.

Kevin

[Kevin]

"steve_t" wrote:

> When you say that the IP isn't getting updated, do you mean that the clients
> are not creating valid DNS records, or that the old records are still being
> listed in DNS?

THE OLD RECORDS ARE STILL BEING LISTED (showing IP from VPN).

>
> "It still has the old IP from when they were on the VPN client the night
> before"
>
> Is this referring to the IP address of the workstation or the DNS records
> for the workstation on the DNS server?

I'M REFERING TO THE IP IN THE DNS RECORD. THE CLIENT RECEIVES THE NEW IP
FROM THE LAN DHCP FINE.

Can the clients communicate on the network when they boot up on the network?

> YES. THEY CAN COMMUNICATE ON THE NETWORK.

> The ipconfig/flushdns command flushes the DNS resolver cache on the local
> client, so it won't do anything w/DNS records on the server. You could try
> ipconfig/registerdns on the client, which will refresh the client's DHCP
> lease and re-register the DNS names on the server.

SORRY. I MEANT "IPCONFIG/REGISTERDNS" (NOT FLUSHDNS)