FH_JGoodwin
asked on
DNS Host (A) Record -- Different Record for Each Subnet
We have a centralized domain with a private IP scheme 172.16.X.Y -- X = location number, Y = individual address. This is across multiple locations. Our RF guns load a software that has the default location of the RF server as the word "RFSERVER." Obviously, I could make a Host (A) record to forward the word RFSERVER to the correct address for our main location's RF server - 172.16.1.Y.
My problem is we have multiple locations on one domain, with different subnets, but all pass DNS info back and forth through Active Directory. How do I make a Host (A) record to forward RFSERVER to 172.16.2.Y, and then another to forward to 172.16.3.Y, etc.? Is this even possible?
I don't want the RF guns at 172.16.2.Y sending RF info to RFSERVER if it forwards info to 172.16.1.Y (each location has it's own RF server). So, if our RF server's IP is 122 at all locations, it should load like this:
Location 1: 'RFSERVER' forwards to 172.16.1.122
Location 2: 'RFSERVER' forwards to 172.16.2.122
Location 3: 'RFSERVER' forwards to 172.16.3.122
etc
Any help would be appreciated. Thanks.
My problem is we have multiple locations on one domain, with different subnets, but all pass DNS info back and forth through Active Directory. How do I make a Host (A) record to forward RFSERVER to 172.16.2.Y, and then another to forward to 172.16.3.Y, etc.? Is this even possible?
I don't want the RF guns at 172.16.2.Y sending RF info to RFSERVER if it forwards info to 172.16.1.Y (each location has it's own RF server). So, if our RF server's IP is 122 at all locations, it should load like this:
Location 1: 'RFSERVER' forwards to 172.16.1.122
Location 2: 'RFSERVER' forwards to 172.16.2.122
Location 3: 'RFSERVER' forwards to 172.16.3.122
etc
Any help would be appreciated. Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Each site has it's own DC. All sites are set up in ADSS with appropriate DC servers. Replication is working correctly through this. I also have subnets set up and tied to each Site. For example, the subnet 176.16.1.0/24 is tied to Location1, the subnet 176.16.2.0/24 is tied to Location2, etc.
I have DNS and DHCP installed at each site DC. DNS is replicated across AD, but each DC acts as its own DHCP server (no replication).
So, are you saying I need to set up WINS at each DC and set it up in there?
I have DNS and DHCP installed at each site DC. DNS is replicated across AD, but each DC acts as its own DHCP server (no replication).
So, are you saying I need to set up WINS at each DC and set it up in there?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
JGoodwin,
how are you routing between sites, though Site to site vpn; same building with different routers, or other ways. that is important to know.
how are you routing between sites, though Site to site vpn; same building with different routers, or other ways. that is important to know.
ASKER
Basically, if I ping RFSERVER at Location1, I want it to ping resolve to and ping 172.16.1.122. If I ping RFSERVER at Location2, I want it to resolve to and ping 172.16.2.122.
In looking at DNS, I only have one Forward Lookup Zone and it is our main (and only) domain. Then I have Reverse Lookup Zones for our main site and other sites. The Forward Lookup Zone is where I can create Host (A) records. Can I create multiple Host (A) records for the word 'RFSERVER?' Will the resolve and ping like the above examples?
In looking at DNS, I only have one Forward Lookup Zone and it is our main (and only) domain. Then I have Reverse Lookup Zones for our main site and other sites. The Forward Lookup Zone is where I can create Host (A) records. Can I create multiple Host (A) records for the word 'RFSERVER?' Will the resolve and ping like the above examples?
ASKER
Each location has its own router that resolves back to our main location's router.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We do only have one DNS and I basically set up Reverse Lookups at all remote locations.
I got this working at our main location. If I ping RFSERVER it resolves to 176.16.0.122. However, if I try from an RF gun, even though it shows "Pinging Host RFSERVER [172.16.1.122], the pings fail.
I noticed that when creating the new Host (A) records, there was an option to "Create associated pointer (PTR) record" and also another option "Allow any authenticated user to update DNS records with the same owner name."
Should I have checked either of these options?
If I ping from my computer, it works just fine.
I got this working at our main location. If I ping RFSERVER it resolves to 176.16.0.122. However, if I try from an RF gun, even though it shows "Pinging Host RFSERVER [172.16.1.122], the pings fail.
I noticed that when creating the new Host (A) records, there was an option to "Create associated pointer (PTR) record" and also another option "Allow any authenticated user to update DNS records with the same owner name."
Should I have checked either of these options?
If I ping from my computer, it works just fine.
ASKER
Thanks for all the help guys, but Krzysztof seemed to have all the right answers. I'm now resolving via ping to the correct address at each site because of my previously set up subnets.
For the RF gun issue, that is a whole other problem as I have to set up hosts records within the device.
For the RF gun issue, that is a whole other problem as I have to set up hosts records within the device.
You're welcome :)
"Create associated pointer (PTR) record" creates a PTR record (pointer) in reverse lookup zone. It's helpful when you want to resolve IP address to host name
Krzysztof
"Create associated pointer (PTR) record" creates a PTR record (pointer) in reverse lookup zone. It's helpful when you want to resolve IP address to host name
Krzysztof
note that all subnets must have the same dns server ip. you have a one dhcp I assume.
hope this helps.