Avatar of glopezz
glopezz
Flag for Mexico asked on

How to resolve internal network computer's names?

Hi Experts!
I have a Cisco 1811 router which connects my network to the Internet and provides ip addresses to clients via DHCP. Internally, I have a MS Small Business Server that serves as the internal DNS and forwards requests to OpenDns.org

I have recently installed some network tools to analyze internal traffic (packetter / netflow analyzer), however the tool can not resolve and internal ip's name. For example, if a client is given ip 192.168.1.10 I need to know the computer name (ej. JDOE). I thought of adding the names to the local DNS but since we are using DHCP they are constantly changing.

What would be the best solution?

THanks
DNSMicrosoft Server Apps

Avatar of undefined
Last Comment
lpacker

8/22/2022 - Mon
jar3817

If the DNS is active directly integrated, it should update automatically. How is your DNS setup?
lpacker

In this situation, I would move my DHCP scope to the SB Server. This will allow the Server to dynamically update DNS when DHCP changes.  
Chris Dent


The client can do that without DHCP updating on their behalf. But...

1. The Lease must be moderately long so it doesn't change too frequently (long is anything greater than 1 - 2 days in this case)
2. Aging / Scavenging must be configured
3. A Reverse Lookup Zone must be configured (for IP to Name resolution)

You might consider moving DHCP to the SBS server anyway, I thought SBS complained endlessly if it wasn't the DHCP server (it's been a while though and I could have just imagined that).

Chris
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
glopezz

ASKER
Hi Everyone and thanks for your replies.
I have disabled DHCP in the router and activated it in the SBS. When looking at the DHCP control panel - Adress Leases I can now see the ip and the name of the computer:

Client IP Address: 192.168.1.130
Name: JDOE.domain.local

I created the scope with a 4 day lease time.

However, when using SBS for an nslookup I get:

> server 192.168.2.50
Default server: 192.168.2.50
Address: 192.168.2.50#53
> 192.168.2.144
Server:            192.168.2.50
Address:      192.168.2.50#53

** server can't find 144.2.168.192.in-addr.arpa.: NXDOMAIN

In my DNS configuration I have a Reverse Lookup Zone: 192.168.1.x Subnet but this doesn't seem to work. How do I configure Aging / Scavenging?

Thanks again!
glopezz

ASKER
Sorry, all IP addresses are 192.168.1.x, so:

> server 192.168.1.50
Default server: 192.168.1.50
Address: 192.168.1.50#53
> 192.168.1.144
Server:            192.168.1.50
Address:      192.168.2.50#53

** server can't find 144.1.168.192.in-addr.arpa.: NXDOMAIN
Chris Dent


I guess no records are under the Reverse Lookup Zone at the moment then? Is Dynamic Updates enabled on that zone (in the properties for the zone)?

For Scavenging this article does a better job of describing it than I:

http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

If you have any questions about anything within that article I will happy answer them though :)

Chris
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
lpacker

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
glopezz

ASKER
Thanks everyone!
I have changed the Dynamic Update settings according to lpacker comments and also on the Reverse Zone for 192.168.2.x

When I refresh the zone I now see 2 or 3 machines with their name! However I am missing the rest of the machines, the network is about 20 computers. Should I wait until the users disconnect and reconnect again?

I think we're getting very close.

SOLUTION
Chris Dent

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
lpacker

Chris-Dent is right. I did say it in my previous post, however after re-reading it I couldn't understand what I said. All the client machines will need to register (request an IP address) from the SMB server before your DNS is syncronized. The client machines will do this on their own half-way through there lease expiration. However, you can force this behavior by releasing and renewing the IP address on each client machine.
Side-Note: If you check your DHCP leases, you may see a few NACK registrations. These entries can be deleted. It occurs when a client requests an IP address that is already in use. This will happen when switching DHCP servers.
glopezz

ASKER
Hi Guys!
I waited a couple of days (since my lease time is 3 days) to see if more hosts were reflected in the reverse zone. Just a few more have (still missing about 15), but it seems to be working. Perhaps in couple of more days all hosts will be updated?
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
lpacker

Keep us informed.
glopezz

ASKER
Hi everyone.

Another couple of hosts have been added to the list, but it is taking a long time for the rest. I have pplied ipconfi /release - ipconfig /renew, disabled and enable the network cards but still not in the DNS.
Any clues?
THanks
lpacker

Ensure there are no NACKs in the DHCP scope. If so, delete them.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.