Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

DNS and Reverse Lookup PTR Records - Server 2003

$
0
0

this network was setup before I came on board about a month ago and I am trying to get a handle on somethings like the DNS Reverse Lookup.

The company uses Spiceworks which is a free webbase program to gather information on each device on the network and it has a  helpdesk ticket app in it that they use.  I am not getting all the devices on the inventory list in Spiceworks and one of the reasons is because Reverse Lookup was not configured.  So I configured it to the best of knowledge, have not done it in the past so with the help of KB's I have it set up..

configuration of DC01 server that has DNS on it.  (DC02 also has DNS on it and is configured the same way)

General: 

Status: Running,

Type: Active Driectory-intergrated, 

Replication:  All domain controllers in the AD domain,  

Dynamics updates: Secure only

Start of Authority(SOA):

Serial number 10,

Primary server: HS-DC01.HSC.local for dc01(name changed to protect the company :) ), HS-DC02-HSC.local  for dc02

Responible person: hostmaster.HSC.local,

Refresh interval 15 minutes,

Retry interval 10 minutes,

expires after 1 days,

Minimum (default)TTL 1 hours, TTL for this record: 0:1:0:0

Name Servers:

HS-DC02.HSC.local              (10.10.1.14*)

HS-DC01.HSC.local              (10.10.1.13*)

Wins-R:

NOTHING CHECKED   not using WINS

Zone Transfers:

Nothing checked off... not sure if I need to Allow Zone Transfers: and if i do, do i add the 10.10.1.14 to the DNS on DC01 and 10.10.1.13 to the DNS on DC02?

Security:  local admin, authenicated users, domain admins, enterprise admins, enterprise domain controllers, Everyone(read only for everyone), Pre-windows 2000 compatible access and system. 

When I first set Reverse Lookup up, the following appeared in the DNSMGMT console on both DC's DNS screens

Reverse Lookup Zones with 10.10.1.X subnet underneath it.

10.10.1X Subnet had

(same as parent folder)            Start of Authority (SOA)  and Data info

(same as parent folder)            Name Server (NS)   and data info

10.10.1.103                             Pointer (PTR)          and data info (i did not add this one and not sure why it showed up)

I went in and added 10.10.1.13 Pointer (PTR) for the first DC 

Then I went into the second DC and added 10.10.1.14 Pointer (PTR)

both of those pointers showed up in DNS on both DC's so i have 5 items in the DNSMGMT on both DC's DNS screen so it looks like they are syncing

about an hour later after I had to do some other things i went into DNSMGMT and notice that another PTR showed up.  

I was thinking that since I have "Dynamics updates: Secure only" it would add all the other computers to the list, however it has been over an hour and no other PTR's have appeared in the Reverse Lookup Zone.  Do I have to manually go in and add each device?   I sure hope not.

When I do an NSLOOKUP hs30 I get

Server: HS-DC01.HSC.local

Address: 10.10.1.73

however when i do NSLOOKUP 10.10.1.73 I get

Server:HS-DC01.HSC.local 

address: 10.10.1.13

****HS-DC01.HSC.local can't find 10.10.1.73: Non-existent domain

why is that if I configured reverse lookup zone?  or could it be related to what is happening in the next paragraph?

In reading another post with someone who had a simular problem, in one of the replies to this persons post mentioned " On the DHCP server properties there is an option to configure user credentials.  If that is set to a user account make of the following......"   

For some strange reason (again I was not here when the network was setup), the SonicWall firewall has the DHCP configuration on it.  DHCP is NOT configured on either of the DC's.  could this be the reason Reverse Lookup is not working properly?  the problem I have is no one here knows what the password is to get into the SonicWall webbased program to do any configuration changes. the consulting company that set up the sonicwall  tells me that the password is one thing and it is not and they are not corporating with me.  As far as we know there is no backdoor entry to Sonicwall like there is if you had a Cisco unit, you have to reset the unit and start all over again and I am not willing to do that at this point since I don't know what settings are there (VPN, DHCP, and I do not want to mess anything up, this is a 24/7/365 day operation and it can not afford to be down one minute.

If anyone can help me out I would greatly appreciate it.

my questions once again.

1) in the configuration of Zone Transfers:  not sure if I need to Allow Zone Transfers: and if i do, do i add the 10.10.1.14 to the DNS on DC01 and 10.10.1.13 to the DNS on DC02?

2) In  they Dynamic Updates: Secure only---   Do I have to manually go in and add each device?

3) NSLOOKUP issue: why is that if I configured reverse lookup zone?  or could it be related to what is happening in the next paragraph?

4) SonicWall having DHCP configured: could this be the reason Reverse Lookup is not working properly?

Thank you in advance

Robin

   



Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>