Missing DNS Host (A) Records

[Debbie Fisher]

Clients are able to resolve DNS names against DNS server.
However, when looking for A records, it appears to be
missing. An assoc PTR record is there. A network trace
confirms the DNS server is replying with the IP address.

Any help would be appreciated!

 

[Michael Johnston [MSFT]]

Depending on the view configured in DNS, "A" records may appear as HOST records. Also, if you see the PTR record, then you are looking at the reverse
lookup zone. The reverse lookup zone will not have a "A" record in it. Only the forward lookup zones contain "A" records.


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.

 

[Ace Fekay [MVP]]

In

Clients are able to resolve DNS names against DNS server.
However, when looking for A records, it appears to be
missing. An assoc PTR record is there. A network trace
confirms the DNS server is replying with the IP address.

Any help would be appreciated!

In addition to Michael's response:

Do you have zone updates allowed on the zone?
Do the clients have the zone's name as their Primary DNS Suffix?
Do the clients only point to this internal DNS server?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Debbie FIsher]

I can confirm that I am looking at the correct screen and
that I understand how records appear. The problem is that
there are ptr records that have been created dynamically
in the reverse lookup zone, but there may not be a
corresponding RR in the forward lookup zone.

-----Original Message-----
Depending on the view configured in DNS, "A" records may

appear as HOST records. Also, if you see the PTR record,
then you are looking at the reverse

lookup zone. The reverse lookup zone will not have a "A"

record in it. Only the forward lookup zones contain "A"
records.

Thank you,
Mike Johnston
Microsoft Network Support

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.

 

[Debbie Fisher]

Than you for your comments.
I have checked the suggestions that you gave and can
confirm that the zone updates automatically, the clients
do all have the the zones name as theit primary DNS suffix
and they all point to the same internal DNS server.

Have you any further advice? It would be much appreciated!

 

[Ace Fekay [MVP]]

In

Clients are able to resolve DNS names against DNS server.
However, when looking for A records, it appears to be
missing. An assoc PTR record is there. A network trace
confirms the DNS server is replying with the IP address.

Any help would be appreciated!

A number of things dictate registration.
1. The Primary DNS Suffix of the machine needs to be the same exact name as
the zone in DNS.
2. Only pointing to the internal DNS server that you want to register to,
and not any others.
3. Updates set to at least YES on the zone.
4. Win2k, XP and W2k3 will register. NT4, Win9x, Mac's, etc, will not,
unless you use Option 081 features in DHCP and as long as they're DHCP
clients.

Hope that helps

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[TIM ROBERTS]

Is your zone set to allow dynamtic updates Yes or secure only? What SP do
you have installed?