PTR problem.

  • Thread starter Thread starter Corey Fisher
  • Start date Start date
C

Corey Fisher

We use a class B address space. (128.1.0.0) When I attempt to create
a reverse pointer for our domain, I'm only aloud to add the last
octet, as though my network is a class C.
It looks like I screwed something up when moving to DNS years ago...
Currently my reverse pointer shows 1.1.128.in-addr.arpa, which is
WRONG. But even when I create a new Reverse Lookup Zone of
1.128.in-addr.arpa, I still am limited to a class C PTR
record....What's going on?


Should I kill everything and start over? Or is there a fix?
 
CF> When I attempt to create a reverse pointer for our domain,
CF> I'm only aloud to add the last octet, as though my network
CF> is a class C.

Really ? When you attempt to add a "PTR" resource for the subdomain name
"1.0", what is the error message ?
 
In
Corey Fisher said:
We use a class B address space. (128.1.0.0) When I attempt to create
a reverse pointer for our domain, I'm only aloud to add the last
octet, as though my network is a class C.
It looks like I screwed something up when moving to DNS years ago...
Currently my reverse pointer shows 1.1.128.in-addr.arpa, which is
WRONG. But even when I create a new Reverse Lookup Zone of
1.128.in-addr.arpa, I still am limited to a class C PTR
record....What's going on?


Should I kill everything and start over? Or is there a fix?
Click to expand...

Probably depends on how the zone was created. If it was created as 128.0.0.x
(by inputing 128.0.0 and hitting next in the wizard), or
0.0.128.in-addr.arpa it would do that.

If it was created as 128.x.x.x (by inputing just 128 and hitting next in the
wizard) or 128.in-addr.arpa, it shouldn't cause that error.

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
 
Back
Top