Windows 2003 Reverse Lookup problem

Microsoft / Windows 2003
April 4, 2009 at 03:01:37
Specs: Windows 2003
I have Windows 2003 domain .We are using class B ip addresses. some host have MASK and some host have MASK and some host have MASK means i am using all Class B address and standred MASK .My problem is when i am going to add reverse lookup zone it will give me only 134.136.1.x address how i can create a zone for 134.136.x.x.

See More: Windows 2003 Reverse Lookup problem

Report •

April 4, 2009 at 07:36:17
Where are you getting the 134.136.x.x address? That belongs to the United States Air Force. Your name tells me that you're not in the Air Force, although I could be wrong.

OrgName: 754th Electronic Systems Group
Address: 501 E. Moore Drive
City: MAFB-Gunter Annex
StateProv: AL
PostalCode: 36114
Country: US

NetRange: -
NetHandle: NET-134-136-0-0-1
Parent: NET-134-0-0-0-0
NetType: Direct Assignment
NameServer: NS1.ACC.AF.MIL

Report •

April 4, 2009 at 16:40:35
should be using private b address range through

I seem to recall that when you go to make a host entry in the forward lookup zone there is a check box to create the ptr in the reverse lookup zone

Report •

April 5, 2009 at 01:29:49
Dear all actually this IP we are using on our private network. we are not connected with internet and we are using this IP classes more than 8 years and now it is very tough job to change this IP class. In the start people set IP address randomly so now it's like one machine another and means every machine has ip of B class but randomly.My question is,is it any way to configure reverse lookup zone for all Class B with standrad mask

Report •

Related Solutions

April 5, 2009 at 05:42:17
You can't have users picking IP addresses from the air. If there is no internet connection, wouldn't a complete hosts file solve the problem? How many machines are there? Even if there are 100 machines, I could change all the IPs in 2 days.

Report •

April 5, 2009 at 07:32:45
I have to agree, changing the IP's wouldn't be that hard. Tedious and time consuming yes, but hard no. Especially not hard if you convert over to DHCP from static.

My question is,is it any way to configure reverse lookup zone for all Class B with standrad mask

Did you not see what wanderer said above? If not, I'll paste and bold it here for you:

I seem to recall that when you go to make a host entry in the forward lookup zone there is a check box to create the ptr in the reverse lookup zone

I seem to recall that checkbox too.....even though it's been about 4 years now since I even touched, or looked at, a Windows server.

Truth be told, you need to revamp your entire setup from what I can see. Using non-private IP's and static assignment is not a good plan. Plus you seem to have multiple subnets. Unless you have a very large environment with an equally large number of users, I can't see any reason to have multiple subnets. The general rule-of-thumb in computing is to always follow the KISS principle

KISS = keep it simple silly

Report •

April 5, 2009 at 07:36:44
What do you do for work Curt, if you don't mind me asking?

I assumed you would be in the Networking industry but not having, "touched a Windows server for about 4 years" can you really be in the industry that long and not..?

Report •

April 5, 2009 at 08:41:40

A Windows server isn't the only server that can provide DHCP services. A lot of companies use *nix servers. I haven't touched a Windows DHCP server for almost 10 years. Our company uses 500 Linux servers and 5 Windows servers. Of course, they don't all provide DHCP service, but all of our DHCP is handled by the Linux boxes.

Report •

April 5, 2009 at 08:51:03
I'm a "Network Technician" at a university.

I've actually been working with computers for around 15 years now. I have a diploma in computing (2 year course) as well as my MCSE, A+, Network+ and a plethora of vendor cert's including, Compaq, IBM, HP, Lexmark.

Prior to taking the position I presently hold I've done everything from hardware to domain administration. I've done everything from building an AD integrated domain from the ground up, to upgrading people from NT 4.0 to 2000/2003.

The responsibilities of my present position include day-to-day maintenance and support of our network.

This includes our WAN - we have locations in 4 different cities and one of those locations includes two different buildings connected via a point-to-point Enterprise wireless shot. Another location includes 3 separate buildings connected via the same p-to-p wireless as well as one of them having a redundant fibre optic (dedicated) connection to the main building at our site.

So that's a WAN that encompasses two MAN's and two locations with a single LAN.

We have dual redundant Nortel Passport 8600 core switches. Somewhere in the area of 100+ high density Nortel Baystack 5510 and 5520 switches spread over 13 wiring closets in our main location (including our data center which holds over 200 servers - can't give you an actual count there - most of which are *nix servers) and 30+ switches located in the other locations.

I'm also responsible for our in-house wireless network as well as VoIP. I handle day-to-day changes on all switches (and then backup up the configs after making changes) and I'm also responsible for configuring/deploying new switches.

I'm presently in the middle of evergreening out the old Cisco and 3Com switches in our environment and have to date created and deployed 4 "stacks" of switches (connected via 'cascade cables' which allows multiple switches to behave as one single BIG switch) in our data center. I've replaced multiple single switches in favor of the 4 stacks which are:
Server stack (5 switch stack)
Client stack (5 switch stack)
DMZ stack (4 switch stack)
Firewall stack (3 switch stack)

The DMZ and Client stacks are already in production and the Server and FW stacks are deployed and we've already started moving servers over onto the server stack (new connections only so far) but to move all firewall connections and the remaining server connections to the new stacks requires coordinating with all other computing departments so will be a little tricky as it will require a wee bit of downtime. We should be finishing that up in the next 8 weeks or so.

Let's see, have I missed anything..............

Oh yes! The server I built and deployed that does our network monitoring. It's a linux based server running Cacti. That's really the only server I touch anymore as all the others belong to other departments like the Web department.

The last thing I haven't mentioned yet is the least enjoyable part of my job, but also one of the most necessary..........documentation.

So do you now understand how I can not touch a Windows server in the last 4 years (that's how long I've held my present 'network technician' position)?


Report •

April 5, 2009 at 09:28:16
Good answer, thanks, i am forever learing and this what is just the stuff i need to know.......

Report •

April 6, 2009 at 10:42:48

Acording to Mr. Wanderer
"should be using private b address range through

I seem to recall that when you go to make a host entry in the forward lookup zone there is a check box to create the ptr in the reverse lookup zone"

If i use IP private b address range through then how can i make reverse lookup zone for when i make revese lookup zone it will ask network id and when i define 172.16.0.x it will fix these three (172.16.0) and ask last address it's mean if my first host is then how i add this in reverse lookup zone and suppose i add another host with ip address then how i will create PTR record.

Report •

April 6, 2009 at 11:32:17
I didn't say use this as your range but this is the private Class B address range you should be using instead of a public ip range which you are using.

Have you reviewed this?

Report •

April 6, 2009 at 11:43:00
Applying the famous quote by Curt R to the situation at hand.
KISS = keep it simple silly

My guess is that a Class B subnet isn't needed in the first place & a Class C would work just fine, which would make things even more simple.

No matter what, everyone agrees to move to an internal block of IP addresses.

Report •

Ask Question