two reverse record for one host

  • Thread starter Thread starter Dwane
  • Start date Start date
D

Dwane

We have an instance where we are receiving two reverse records for
each server and each DHCP entry. We are using Windows 2003 server for
DNS and DHCP with AD Integration. When we enter a host, we will get
an reverse record like 10.10.100.5 johnson.win.mydomain.com (from
AD) and then get
10.10.100.5 johnson.v19.mydomain.com
(FQDN)

WE would prefer the FQDN to be the resolution for teh IP address. If
you do an 'nslookup 10.10.100.5' it will give you the AD response and
then the next time, it will respond with the FQDN address and then
repeat the responses AD then FQDN for each one afterwards.

ANy ideas of how to stop this?

Thank you
 
Dwane said:
We have an instance where we are receiving two reverse records for
each server and each DHCP entry. We are using Windows 2003 server for
DNS and DHCP with AD Integration. When we enter a host, we will get
an reverse record like 10.10.100.5 johnson.win.mydomain.com (from
AD) and then get
10.10.100.5 johnson.v19.mydomain.com
(FQDN)
Click to expand...

Likely it has (at least one) a NIC specific DNS Suffix.

A single NIC machine almost never needs that at all.

The Primary DNS Suffix should be set in the System Control Panel (only)
 
Likely it has (at least one) a NIC specific DNS Suffix.

A single NIC machine almost never needs that at all.

The Primary DNS Suffix should be set in the System Control Panel (only)






- Show quoted text -
Click to expand...

SIr, all of our devices have the "register this connections address
in DNS" and it is one issue in the replacing DNS servers. Is there a
way in Windows 2003 or Windows 2008 DNS server that will allow us to
choose which Reverse Lookup we prefer? You would think that there
would be a check box or something that we can utilize for this. I
would also think that the server would be able the controlling
authority on this.

THanks for your help.

Dwane
 
Sorry for blank--this web based nntp client is kind of lame.

To eliminate the second undesired PTR record (if it's being consistently
produced after you've deleted it), simply disable the unsecured dynamic dns
on the v19.mydomain.com zone. Not many scenarios that you need hosts
registering in that zone, not many reasons at all.

Just leave dyn dns on the AD zone (it'd be real bad to disable dyn dns
updates on a zzone for an active directory
 
Sorry for blank--this web based nntp client is kind of lame.

To eliminate the second undesired PTR record (if it's being consistently
produced after you've deleted it), simply disable the unsecured dynamic dns
on the v19.mydomain.com zone.  Not many scenarios that you need hosts
registering in that zone, not many reasons at all.

Just leave dyn dns on the AD zone (it'd be real bad to disable dyn dns
updates on a zzone for an active directory
--
Remotely managing and monitoring Phoenix AZ Networks

:






- Show quoted text -
Click to expand...

Thank you for the quick response. The issue we have is that we would
like the FQDN entry so that we can use it as a troubleshooting tool.
By using just the AD entry, we just know that the device exists on the
network. By using the FQDN entry, it tells us what department it is
in. My superiors have request the FQDN as well.

My question is, does Microsoft DNS have a way to tell the client that
regardless of what you have in your network connection properties, I
want you to use this suffix based on the DHCP address you have
requested via your Vlan setting?

I certainly appreciate everyone's response since I am fairly new at
this Microsoft DNS and DHCP services.
 
Read inline please.

In
Dwane said:
We have an instance where we are receiving two reverse records for
each server and each DHCP entry. We are using Windows 2003 server for
DNS and DHCP with AD Integration. When we enter a host, we will get
an reverse record like 10.10.100.5 johnson.win.mydomain.com (from
AD) and then get
10.10.100.5 johnson.v19.mydomain.com
(FQDN)

WE would prefer the FQDN to be the resolution for teh IP address. If
you do an 'nslookup 10.10.100.5' it will give you the AD response and
then the next time, it will respond with the FQDN address and then
repeat the responses AD then FQDN for each one afterwards.

ANy ideas of how to stop this?
Click to expand...

This is happening because your Primary and Connection DNS suffixes are
different and both are registering. IF you have DHCP properly setup to
always register A and PTR records, you can disable DNS Registration in
TCP/IP properties. This will allow the DHCP server to register for the
client, even though it is disabled on the client. I've never tested this,
but you can disable only the PTR registrations, and try letting DHCP
register the PTR for the Connection Specific suffix.



--
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
===================================
 
In
Dwane said:
We have an instance where we are receiving two reverse records for
each server and each DHCP entry. We are using Windows 2003 server for
DNS and DHCP with AD Integration. When we enter a host, we will get
an reverse record like 10.10.100.5 johnson.win.mydomain.com (from
AD) and then get
10.10.100.5 johnson.v19.mydomain.com
(FQDN)

WE would prefer the FQDN to be the resolution for teh IP address. If
you do an 'nslookup 10.10.100.5' it will give you the AD response and
then the next time, it will respond with the FQDN address and then
repeat the responses AD then FQDN for each one afterwards.

ANy ideas of how to stop this?

Thank you
Click to expand...

Normally the FQDN, if there is one, will always be the response. So what
you're seeing is Round Robin. That can be disabled, but it will always take
the first entry so you really don't want to do that, plus it messes up with
DC responses to GPO requests and other requests.

But what bothers me is why is it registering into two different zone names?
What is the Primary DNS Suffix on "johnson's" machine? Also, what do you
have it set to register into both v19.domain.com zone and the
win.mydomain.com zones? Is the "win" zone based on "DNS uses WINS resolution
being set?"

Can you post an ipconfig /all of the johnson machine please?

Thanks.

--
Regards,
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

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

Infinite Diversities in Infinite Combinations
 
Back
Top