Reverse zone question x.x.x.x Subnet / x. in-addr-arpa?
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Reverse zone question x.x.x.x Subnet / x. in-addr-arpa?

 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS
Author Message
Mike Bonvie
Guest
Posted: Fri Jan 21, 2005 4:23 am    Post subject: Reverse zone question x.x.x.x Subnet / x. in-addr-arpa? Reply with quote
Using 2003 AD integrated DNS; We added another name server to the AD
"domain"

We 1st ran dcpromo, then installed AD integrated DNS. The forward zones look
fine.

However we noted the reverse zone(s) before the addition had zones in a
naming convention
x.in-addr.arpa.

After the addition of the name server, it seems the way we defined the
reverse lookup zone on the new name server unintentionally as "x.x.x.x
Subnet"

This reverse lookup zone propagated throughout the entire domain AD DNS.
Looking at the contents of the x.x.x.x Subnet reverse zone, all the records
look fine.

Manually deleting/recreating or attempting to make new reverse zones result
in the "x.x.x.x Subnet" not "x.in-addr.arpa"

2 questions:

Is it critical the naming of the existing or any future created reverse
zones have the naming convention "x.in-addr.arpa"?

Is there a functional difference between the reverse zones named as
"x.x.x.x Subnet" not "x.in-addr.arpa"

Any advice or suggestions would be great.
Please reply to the group
Thank You,
Mike Bonvie
Back to top
Herb Martin
Guest
Posted: Fri Jan 21, 2005 6:47 am    Post subject: Re: Reverse zone question x.x.x.x Subnet / x. in-addr-arpa? Reply with quote
The actual name of the zone (x.y.z.in-addr.arpa.)
is critical if you wish reverse lookup to succeed.

You may be seeing a different between some
friendly name (display name) and the real name
so check the zone properties....

--
Herb Martin


"Mike Bonvie" <mike@removeme.com> wrote in message
news:#sz9d6z$EHA.3124@TK2MSFTNGP11.phx.gbl...
Quote:
Using 2003 AD integrated DNS; We added another name server to the AD
"domain"

We 1st ran dcpromo, then installed AD integrated DNS. The forward zones
look
fine.

However we noted the reverse zone(s) before the addition had zones in a
naming convention
x.in-addr.arpa.

After the addition of the name server, it seems the way we defined the
reverse lookup zone on the new name server unintentionally as "x.x.x.x
Subnet"

This reverse lookup zone propagated throughout the entire domain AD DNS.
Looking at the contents of the x.x.x.x Subnet reverse zone, all the
records
look fine.

Manually deleting/recreating or attempting to make new reverse zones
result
in the "x.x.x.x Subnet" not "x.in-addr.arpa"

2 questions:

Is it critical the naming of the existing or any future created reverse
zones have the naming convention "x.in-addr.arpa"?

Is there a functional difference between the reverse zones named as
"x.x.x.x Subnet" not "x.in-addr.arpa"

Any advice or suggestions would be great.
Please reply to the group
Thank You,
Mike Bonvie

Back to top
Kevin D. Goodknecht Sr. [
Guest
Posted: Fri Jan 21, 2005 6:47 am    Post subject: Re: Reverse zone question x.x.x.x Subnet / x. in-addr-arpa? Reply with quote
In news:%23sz9d6z$EHA.3124@TK2MSFTNGP11.phx.gbl,
Mike Bonvie <mike@removeme.com> commented
Then Kevin replied below:
Quote:
Using 2003 AD integrated DNS; We added another name
server to the AD "domain"

We 1st ran dcpromo, then installed AD integrated DNS. The
forward zones look fine.

However we noted the reverse zone(s) before the addition
had zones in a naming convention
x.in-addr.arpa.

After the addition of the name server, it seems the way
we defined the reverse lookup zone on the new name server
unintentionally as "x.x.x.x Subnet"

This reverse lookup zone propagated throughout the entire
domain AD DNS. Looking at the contents of the x.x.x.x
Subnet reverse zone, all the records look fine.

Manually deleting/recreating or attempting to make new
reverse zones result in the "x.x.x.x Subnet" not
"x.in-addr.arpa"

2 questions:

Is it critical the naming of the existing or any future
created reverse zones have the naming convention
"x.in-addr.arpa"?

Is there a functional difference between the reverse
zones named as "x.x.x.x Subnet" not "x.in-addr.arpa"

Any advice or suggestions would be great.

In the View menu, select Advanced.


--
Best regards,
Kevin D4 Dad 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/
===================================
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
===================================
Back to top
Mike Bonvie
Guest
Posted: Fri Jan 21, 2005 8:44 pm    Post subject: Re: Reverse zone question x.x.x.x Subnet / x. in-addr-arpa? Reply with quote
Hi Kevin,

That did it!! Thanks


"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:OFm63h2$EHA.936@TK2MSFTNGP12.phx.gbl...
Quote:
In news:%23sz9d6z$EHA.3124@TK2MSFTNGP11.phx.gbl,
Mike Bonvie <mike@removeme.com> commented
Then Kevin replied below:
Using 2003 AD integrated DNS; We added another name
server to the AD "domain"

We 1st ran dcpromo, then installed AD integrated DNS. The
forward zones look fine.

However we noted the reverse zone(s) before the addition
had zones in a naming convention
x.in-addr.arpa.

After the addition of the name server, it seems the way
we defined the reverse lookup zone on the new name server
unintentionally as "x.x.x.x Subnet"

This reverse lookup zone propagated throughout the entire
domain AD DNS. Looking at the contents of the x.x.x.x
Subnet reverse zone, all the records look fine.

Manually deleting/recreating or attempting to make new
reverse zones result in the "x.x.x.x Subnet" not
"x.in-addr.arpa"

2 questions:

Is it critical the naming of the existing or any future
created reverse zones have the naming convention
"x.in-addr.arpa"?

Is there a functional difference between the reverse
zones named as "x.x.x.x Subnet" not "x.in-addr.arpa"

Any advice or suggestions would be great.

In the View menu, select Advanced.


--
Best regards,
Kevin D4 Dad 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/
===================================
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
===================================

Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB