reverse lookup doenst add ip's

I added a reverse lookup to my2008server
why doest it fill with the ip's that are curently in use?

tx for any info
N.

I have a 2008domaincontroller where I installed the dns service, and it
works fine.
200 computers are listed in that domain on my dns.
I want to do reverse lookups and that's why I added a primary zone for
reverse lookup
the only ip's that get listed in that reverse lookup are my server and a
terminal server that is also in my domain.
None of the 200computers get lsited here, and for that, i cant do reverse
lookups on them.
why are the 200computers not listed?

tx for any help.

N.



"J de Boyne Pollard" <> schreef in bericht
news:b9c74c50-6162-42a7-9bfc-...
> N> I added a reverse lookup to my2008server
> N> why doest it fill with the ip's that are curently in use?
>
> For *at least* three possible, and entirely different, reasons.
>
> <URL:http://homepage.ntlworld.com./jonath...d/FGA/problem-
> report-standard-litany.html>
>
> Tell the world the proper details, and the world will tell you which
> of the possibilities is actually occurring. "I added a reverse
> lookup" and "currently in use" are imprecise and insufficient for
> diagnosis.

"nico" <> wrote in message
news:eubP8r%...
>I have a 2008domaincontroller where I installed the dns service, and it
>works fine.
> 200 computers are listed in that domain on my dns.
> I want to do reverse lookups and that's why I added a primary zone for
> reverse lookup
> the only ip's that get listed in that reverse lookup are my server and a
> terminal server that is also in my domain.
> None of the 200computers get lsited here, and for that, i cant do reverse
> lookups on them.
> why are the 200computers not listed?
>
> tx for any help.
>
> N.
>

Nico,

This can depend on whether the reverse zone was created correctly, and which
DNS servers are listed in the client machines, and if DHCP is involved, or
all the above.

To better assist, please post the following to help us evaluate the
conditions:

1. An ipconfig /all from a sample workstation that is not registering
2. An ipconfig /all from two DCs, one of which will be the DHCP server.
3. Zone updates setting on the reverse zone (Secure or Secure and non-Secure
clients)
4. DHCP properties, DNS tab. How do you have it set to register DHCP
clients? To force all updates, or just set to default?
5. Have you set DHCP in the DnsUpdateProxy Group, or provided DHCP
credentials to own al records, or just to default?
6. DNS Zone scavenging set?


For more info about 4, 5 and 6, please read more on it in the following
link.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the
DnsProxyUpdate Group (How to remove duplicate DNS host records)
http://msmvps.com/blogs/acefekay/arc...ate-group.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

here the date you asked for.
tx.
N.

1 ipconfig /all from a client

Windows IP-configuratie

Hostnaam . . . . . . . . . . . . : it-PC
Primair DNS-achtervoegsel . . . . :
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local

Ethernet-adapter voor LAN-verbinding:

Verbindingsspec. DNS-achtervoegsel: pcvomeetjesland.local
Beschrijving. . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family
PCI-E
Gigabit Ethernet NIC (NDIS 6.20)
Fysiek adres. . . . . . . . . . . : 00-21-85-10-24-DF
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . :
fe80::d563:d01d:3550:324f%11(voorkeur)
IPv4-adres. . . . . . . . . . . . : 172.16.4.101(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.240.0
Lease verkregen . . . . . . . . . : dinsdag 8 december 2009 8:37:31
Lease verlopen. . . . . . . . . . : woensdag 16 december 2009 9:37:31
Standaardgateway. . . . . . . . . : 172.16.0.254
DHCP-server . . . . . . . . . . . : 172.16.0.1
DHCPv6 IAID . . . . . . . . . . . : 234889605
DHCPv6-client DUID. . . . . . . . :
00-01-00-01-12-4E-6D-08-00-21-85-10-24-DF

DNS-servers . . . . . . . . . . . : 172.16.0.1
Primaire WINS-server. . . . . . . : 172.16.0.1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld

2. ipconfig /all DC, dns, dhcp, winsserver


Windows IP-configuratie

Hostnaam . . . . . . . . . . . . : pcvo-server
Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local

Ethernet-adapter LAN-verbinding:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Fysiek adres. . . . . . . . . . . : 00-10-18-2F-39-0A
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
IPv4-adres. . . . . . . . . . . . : 172.16.0.1(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.240.0
Standaardgateway. . . . . . . . . : 172.16.0.254
DNS-servers . . . . . . . . . . . : 172.16.0.1
Primaire WINS-server. . . . . . . : 172.16.0.1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld

3. ipconfig /all terminal server

C:\Users\Administrator.PCVOM>ipconfig /all

Windows IP-configuratie

Hostnaam . . . . . . . . . . . . : ts
Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local

Ethernet-adapter LAN-verbinding:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Fysiek adres. . . . . . . . . . . : 00-10-18-2F-3C-25
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
IPv4-adres. . . . . . . . . . . . : 172.16.0.2(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.240.0
Standaardgateway. . . . . . . . . : 172.16.0.254
DNS-servers . . . . . . . . . . . : 172.16.0.1
Primaire WINS-server. . . . . . . : 172.16.0.1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld

4a. dhcp prop

172.16.0.1 dns server
172.16.0.254 router
172.16.0.1 wins
all the rest are default settings

4b dns prop

DNS
PCVO-SERVER
FORWARD LOOKUP
PCVOMEETJESLAND.LOCAL
200 records with ip's & computername's
REVERSE LOOKUP
0.16.172.in-addr.arpa
2ip's, from my 2 2008servers with fixed ip

5. dhcp setteings
dhcp settings are default

6. DNS Zone scavenging
is not set


"Ace Fekay [MCT]" <> schreef in bericht
news:uvqQC#...
> "nico" <> wrote in message
> news:eubP8r%...
>>I have a 2008domaincontroller where I installed the dns service, and it
>>works fine.
>> 200 computers are listed in that domain on my dns.
>> I want to do reverse lookups and that's why I added a primary zone for
>> reverse lookup
>> the only ip's that get listed in that reverse lookup are my server and a
>> terminal server that is also in my domain.
>> None of the 200computers get lsited here, and for that, i cant do reverse
>> lookups on them.
>> why are the 200computers not listed?
>>
>> tx for any help.
>>
>> N.
>>
>
> Nico,
>
> This can depend on whether the reverse zone was created correctly, and
> which DNS servers are listed in the client machines, and if DHCP is
> involved, or all the above.
>
> To better assist, please post the following to help us evaluate the
> conditions:
>
> 1. An ipconfig /all from a sample workstation that is not registering
> 2. An ipconfig /all from two DCs, one of which will be the DHCP server.
> 3. Zone updates setting on the reverse zone (Secure or Secure and
> non-Secure clients)
> 4. DHCP properties, DNS tab. How do you have it set to register DHCP
> clients? To force all updates, or just set to default?
> 5. Have you set DHCP in the DnsUpdateProxy Group, or provided DHCP
> credentials to own al records, or just to default?
> 6. DNS Zone scavenging set?
>
>
> For more info about 4, 5 and 6, please read more on it in the following
> link.
>
> DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and
> the DnsProxyUpdate Group (How to remove duplicate DNS host records)
> http://msmvps.com/blogs/acefekay/arc...ate-group.aspx
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>

"nico" <> wrote in message
news:...
> here the date you asked for.
> tx.
> N.
>
> 1 ipconfig /all from a client
>
> Windows IP-configuratie
>
> Hostnaam . . . . . . . . . . . . : it-PC
> Primair DNS-achtervoegsel . . . . :
> Knooppunttype . . . . . . . . . . : hybride
> IP-routering ingeschakeld . . . . : nee
> WINS-proxy ingeschakeld . . . . . : nee
> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>
> Ethernet-adapter voor LAN-verbinding:
>
> Verbindingsspec. DNS-achtervoegsel: pcvomeetjesland.local
> Beschrijving. . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family
> PCI-E
> Gigabit Ethernet NIC (NDIS 6.20)
> Fysiek adres. . . . . . . . . . . : 00-21-85-10-24-DF
> DHCP ingeschakeld . . . . . . . . : ja
> Autom. configuratie ingeschakeld : ja
> Link-local IPv6-adres . . . . . . :
> fe80::d563:d01d:3550:324f%11(voorkeur)
> IPv4-adres. . . . . . . . . . . . : 172.16.4.101(voorkeur)
> Subnetmasker. . . . . . . . . . . : 255.255.240.0
> Lease verkregen . . . . . . . . . : dinsdag 8 december 2009 8:37:31
> Lease verlopen. . . . . . . . . . : woensdag 16 december 2009 9:37:31
> Standaardgateway. . . . . . . . . : 172.16.0.254
> DHCP-server . . . . . . . . . . . : 172.16.0.1
> DHCPv6 IAID . . . . . . . . . . . : 234889605
> DHCPv6-client DUID. . . . . . . . :
> 00-01-00-01-12-4E-6D-08-00-21-85-10-24-DF
>
> DNS-servers . . . . . . . . . . . : 172.16.0.1
> Primaire WINS-server. . . . . . . : 172.16.0.1
> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>
> 2. ipconfig /all DC, dns, dhcp, winsserver
>
>
> Windows IP-configuratie
>
> Hostnaam . . . . . . . . . . . . : pcvo-server
> Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
> Knooppunttype . . . . . . . . . . : hybride
> IP-routering ingeschakeld . . . . : nee
> WINS-proxy ingeschakeld . . . . . : nee
> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>
> Ethernet-adapter LAN-verbinding:
>
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> Fysiek adres. . . . . . . . . . . : 00-10-18-2F-39-0A
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
> IPv4-adres. . . . . . . . . . . . : 172.16.0.1(voorkeur)
> Subnetmasker. . . . . . . . . . . : 255.255.240.0
> Standaardgateway. . . . . . . . . : 172.16.0.254
> DNS-servers . . . . . . . . . . . : 172.16.0.1
> Primaire WINS-server. . . . . . . : 172.16.0.1
> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>
> 3. ipconfig /all terminal server
>
> C:\Users\Administrator.PCVOM>ipconfig /all
>
> Windows IP-configuratie
>
> Hostnaam . . . . . . . . . . . . : ts
> Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
> Knooppunttype . . . . . . . . . . : hybride
> IP-routering ingeschakeld . . . . : nee
> WINS-proxy ingeschakeld . . . . . : nee
> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>
> Ethernet-adapter LAN-verbinding:
>
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> Fysiek adres. . . . . . . . . . . : 00-10-18-2F-3C-25
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
> IPv4-adres. . . . . . . . . . . . : 172.16.0.2(voorkeur)
> Subnetmasker. . . . . . . . . . . : 255.255.240.0
> Standaardgateway. . . . . . . . . : 172.16.0.254
> DNS-servers . . . . . . . . . . . : 172.16.0.1
> Primaire WINS-server. . . . . . . : 172.16.0.1
> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>
> 4a. dhcp prop
>
> 172.16.0.1 dns server
> 172.16.0.254 router
> 172.16.0.1 wins
> all the rest are default settings
>
> 4b dns prop
>
> DNS
> PCVO-SERVER
> FORWARD LOOKUP
> PCVOMEETJESLAND.LOCAL
> 200 records with ip's & computername's
> REVERSE LOOKUP
> 0.16.172.in-addr.arpa
> 2ip's, from my 2 2008servers with fixed ip
>
> 5. dhcp setteings
> dhcp settings are default
>
> 6. DNS Zone scavenging
> is not set
>


Hi Nico,

Thank you for taking the time to gather and posting the data.

Most of the ipconfigs look fine. Two things bring up questions:

#1 - I am concerned with the client ipconfig. It has no Primary DNS Suffix.
It should be "pcvomeetjesland.local." Are the clients joined to the domain?

#4b - The Reverse zone looks fine as stated. Also, are you seeing name
server and SOA entries and not the actual PTR (reverse) entries? Is the
setting to allow updates enabled for the reverse zone?

#5 & #6 - I suggest to enable scavenging, as well as configuring DHCP to
update all clients whether they can update or not andsetting DHCP
credentials so DHCP owns the records it updates so it can update the records
if the IPs change. This avoids duplicate entries for machines when they get
a new IP address.My blog explains how to do that.


Thank you,

Ace

"Ace Fekay [MCT]" <> schreef in bericht
news:#...
> "nico" <> wrote in message
> news:...
>> here the date you asked for.
>> tx.
>> N.
>>
>> 1 ipconfig /all from a client
>>
>> Windows IP-configuratie
>>
>> Hostnaam . . . . . . . . . . . . : it-PC
>> Primair DNS-achtervoegsel . . . . :
>> Knooppunttype . . . . . . . . . . : hybride
>> IP-routering ingeschakeld . . . . : nee
>> WINS-proxy ingeschakeld . . . . . : nee
>> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>>
>> Ethernet-adapter voor LAN-verbinding:
>>
>> Verbindingsspec. DNS-achtervoegsel: pcvomeetjesland.local
>> Beschrijving. . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family
>> PCI-E
>> Gigabit Ethernet NIC (NDIS 6.20)
>> Fysiek adres. . . . . . . . . . . : 00-21-85-10-24-DF
>> DHCP ingeschakeld . . . . . . . . : ja
>> Autom. configuratie ingeschakeld : ja
>> Link-local IPv6-adres . . . . . . :
>> fe80::d563:d01d:3550:324f%11(voorkeur)
>> IPv4-adres. . . . . . . . . . . . : 172.16.4.101(voorkeur)
>> Subnetmasker. . . . . . . . . . . : 255.255.240.0
>> Lease verkregen . . . . . . . . . : dinsdag 8 december 2009 8:37:31
>> Lease verlopen. . . . . . . . . . : woensdag 16 december 2009 9:37:31
>> Standaardgateway. . . . . . . . . : 172.16.0.254
>> DHCP-server . . . . . . . . . . . : 172.16.0.1
>> DHCPv6 IAID . . . . . . . . . . . : 234889605
>> DHCPv6-client DUID. . . . . . . . :
>> 00-01-00-01-12-4E-6D-08-00-21-85-10-24-DF
>>
>> DNS-servers . . . . . . . . . . . : 172.16.0.1
>> Primaire WINS-server. . . . . . . : 172.16.0.1
>> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>>
>> 2. ipconfig /all DC, dns, dhcp, winsserver
>>
>>
>> Windows IP-configuratie
>>
>> Hostnaam . . . . . . . . . . . . : pcvo-server
>> Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
>> Knooppunttype . . . . . . . . . . : hybride
>> IP-routering ingeschakeld . . . . : nee
>> WINS-proxy ingeschakeld . . . . . : nee
>> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>>
>> Ethernet-adapter LAN-verbinding:
>>
>> Verbindingsspec. DNS-achtervoegsel:
>> Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
>> Fysiek adres. . . . . . . . . . . : 00-10-18-2F-39-0A
>> DHCP ingeschakeld . . . . . . . . : nee
>> Autom. configuratie ingeschakeld : ja
>> IPv4-adres. . . . . . . . . . . . : 172.16.0.1(voorkeur)
>> Subnetmasker. . . . . . . . . . . : 255.255.240.0
>> Standaardgateway. . . . . . . . . : 172.16.0.254
>> DNS-servers . . . . . . . . . . . : 172.16.0.1
>> Primaire WINS-server. . . . . . . : 172.16.0.1
>> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>>
>> 3. ipconfig /all terminal server
>>
>> C:\Users\Administrator.PCVOM>ipconfig /all
>>
>> Windows IP-configuratie
>>
>> Hostnaam . . . . . . . . . . . . : ts
>> Primair DNS-achtervoegsel . . . . : pcvomeetjesland.local
>> Knooppunttype . . . . . . . . . . : hybride
>> IP-routering ingeschakeld . . . . : nee
>> WINS-proxy ingeschakeld . . . . . : nee
>> DNS-achtervoegselzoeklijst. . . . : pcvomeetjesland.local
>>
>> Ethernet-adapter LAN-verbinding:
>>
>> Verbindingsspec. DNS-achtervoegsel:
>> Beschrijving. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
>> Fysiek adres. . . . . . . . . . . : 00-10-18-2F-3C-25
>> DHCP ingeschakeld . . . . . . . . : nee
>> Autom. configuratie ingeschakeld : ja
>> IPv4-adres. . . . . . . . . . . . : 172.16.0.2(voorkeur)
>> Subnetmasker. . . . . . . . . . . : 255.255.240.0
>> Standaardgateway. . . . . . . . . : 172.16.0.254
>> DNS-servers . . . . . . . . . . . : 172.16.0.1
>> Primaire WINS-server. . . . . . . : 172.16.0.1
>> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>>
>> 4a. dhcp prop
>>
>> 172.16.0.1 dns server
>> 172.16.0.254 router
>> 172.16.0.1 wins
>> all the rest are default settings
>>
>> 4b dns prop
>>
>> DNS
>> PCVO-SERVER
>> FORWARD LOOKUP
>> PCVOMEETJESLAND.LOCAL
>> 200 records with ip's & computername's
>> REVERSE LOOKUP
>> 0.16.172.in-addr.arpa
>> 2ip's, from my 2 2008servers with fixed ip
>>
>> 5. dhcp setteings
>> dhcp settings are default
>>
>> 6. DNS Zone scavenging
>> is not set
>>
>
>
> Hi Nico,
>
> Thank you for taking the time to gather and posting the data.
>
> Most of the ipconfigs look fine. Two things bring up questions:
>
> #1 - I am concerned with the client ipconfig. It has no Primary DNS
> Suffix. It should be "pcvomeetjesland.local." Are the clients joined to
> the domain?

this one wasn't joined 2 the domain, but besides that the ipconfigs from the
clients are similar.
>
> #4b - The Reverse zone looks fine as stated. Also, are you seeing name
> server and SOA entries and not the actual PTR (reverse) entries? Is the
> setting to allow updates enabled for the reverse zone?
the entries I see are all pointers, one extra just popped up, a fixed ip
from a copymachine.
dynamic update's are allowed( secure & unsecured)

>
> #5 & #6 - I suggest to enable scavenging, as well as configuring DHCP to
> update all clients whether they can update or not andsetting DHCP
> credentials so DHCP owns the records it updates so it can update the
> records if the IPs change. This avoids duplicate entries for machines when
> they get a new IP address.My blog explains how to do that.

done that.
>
>
> Thank you,
Thank you,
N.

>
> Ace
>

"nico" <> wrote in message
news:%...
>
>> Hi Nico,
>>
>> Thank you for taking the time to gather and posting the data.
>>
>> Most of the ipconfigs look fine. Two things bring up questions:
>>
>> #1 - I am concerned with the client ipconfig. It has no Primary DNS
>> Suffix. It should be "pcvomeetjesland.local." Are the clients joined to
>> the domain?
>
> this one wasn't joined 2 the domain, but besides that the ipconfigs from
> the clients are similar.

The Primary DNS Suffix is what the registration process uses to register
into a Forward Lookup Zone. Is that client machine registering into the
pcvomeetjesland.local zone? If so, I assume then that you have Option 015
set to your AD zone, pcvomeetjesland.local?

>>
>> #4b - The Reverse zone looks fine as stated. Also, are you seeing name
>> server and SOA entries and not the actual PTR (reverse) entries? Is the
>> setting to allow updates enabled for the reverse zone?
> the entries I see are all pointers, one extra just popped up, a fixed ip
> from a copymachine.
> dynamic update's are allowed( secure & unsecured)
>
>>
>> #5 & #6 - I suggest to enable scavenging, as well as configuring DHCP to
>> update all clients whether they can update or not andsetting DHCP
>> credentials so DHCP owns the records it updates so it can update the
>> records if the IPs change. This avoids duplicate entries for machines
>> when they get a new IP address.My blog explains how to do that.
>
> done that.

That was previously set, or you just set it yesterday?


>>
>>
>> Thank you,
>> N.

I'm surprised that the machines are not registering into the reverse zone.
Assuming DHCP is set to register everything (not the default), then it
should be registering. Are there any errors on the client side or any of the
servers?

Ace