finance_teacher
asked on
Windows Server 2016 -- replace "DNS Servers" -- create pointer record ?
I already deployed two Windows Server 2016 "DNS Servers" a few months ago that are working fine, with DHCP IPs getting processed correctly, therefore I turned off my two old Windows Server 2008 "DNS Servers", with everything continuing to work correctly.
I have some REALLY old printers, etc that are almost never turned on, but I turned them on a few days ago, seeing that they still have the OLD static DNS Servers listed.
I can easily change the static DNS Servers, but wanted to see if I could create some type of pointer record, doing something like the below
1. printer has old DNS Server 192.168.24.1 listed
2. since this old DNS Server 192.168.24.1 no longer exists some type of POINTER record automatically forwards this DNS Server request to the new 192.168.24.2 that is on the same subnet/etc
Any ideas on how to setup the above POINTER on my Windows Server 2016 "DNS Servers" ?
I have some REALLY old printers, etc that are almost never turned on, but I turned them on a few days ago, seeing that they still have the OLD static DNS Servers listed.
I can easily change the static DNS Servers, but wanted to see if I could create some type of pointer record, doing something like the below
1. printer has old DNS Server 192.168.24.1 listed
2. since this old DNS Server 192.168.24.1 no longer exists some type of POINTER record automatically forwards this DNS Server request to the new 192.168.24.2 that is on the same subnet/etc
Any ideas on how to setup the above POINTER on my Windows Server 2016 "DNS Servers" ?
David Johnson, CD
A static network adapter never changes whether right or wrong. for it to update it has to be dynamic either in the network address or the dns record area and then the applicable item will be updated via dhcp
ASKER
Correct, is there anyway to setup something on the network so 192.168.24.1 requests automatically get forwarded to 192.168.24.2 instead ?
Give your DNS server 2 IP addresses. That is the solution. Or go back and fix everything trying to use the now invalid DNS server.
Too late now, but I don't create new DNS servers when I replace a DC. I always use the existing IP address on the new server to prevent this problem.
Too late now, but I don't create new DNS servers when I replace a DC. I always use the existing IP address on the new server to prevent this problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Main point: there needs to be a device responding to the old address. There is no service redirecting traffic for non-existing IPs just magically, because the partners need to communicate directly.
The "honeypot" approach (setting up a laptop or VM or the like) with the old address and recording directed traffic is a good idea to catch everything set up "wrong". ARP requests for the old IP are a good hint, because those always are the first step when trying to start TCP/IP connectios.
The "honeypot" approach (setting up a laptop or VM or the like) with the old address and recording directed traffic is a good idea to catch everything set up "wrong". ARP requests for the old IP are a good hint, because those always are the first step when trying to start TCP/IP connectios.
Basicly you have three options to solve the issue:
Reconfigure static info to conform to the new environment
Reconfigure the printers to receive a reserved DHCP address (printer address is the same, all other stuff is inherited,they will update on next startup)
(Also create DHCP entries to match).
Reconfigure DNS server to (also) listen on the old address.
If option 3 is off the table, you may want some mechanism to trap "forgotten systems" like Qlemo suggests.
Reconfigure static info to conform to the new environment
Reconfigure the printers to receive a reserved DHCP address (printer address is the same, all other stuff is inherited,they will update on next startup)
(Also create DHCP entries to match).
Reconfigure DNS server to (also) listen on the old address.
If option 3 is off the table, you may want some mechanism to trap "forgotten systems" like Qlemo suggests.
Seems like what you're asking is actually an IP redirect/forward.
Tip: There is no such thing as a POINTER record. As Mal said, there are PTR records + this is different than what you're asking.
Inside Linux this is very easy, you'd just use HAProxy to redirect any IP/port/protocol to any other IP/port/protocol.
With HAProxy this takes, maybe 5 minutes to get working.
With Windows... whew... I'm unsure... A Windows expert will have to say whether there's similar tech for Windows, as there's no HAProxy project release for Windows.
If this is crucial, 1000s of machines referencing an old IP, likely best to setup a Linux machine running HAProxy inside your infrastructure.
If you only have a few machines referencing the old IP, likely the simple fix is just to change all these machines to use the new IP.
Tip: There is no such thing as a POINTER record. As Mal said, there are PTR records + this is different than what you're asking.
Inside Linux this is very easy, you'd just use HAProxy to redirect any IP/port/protocol to any other IP/port/protocol.
With HAProxy this takes, maybe 5 minutes to get working.
With Windows... whew... I'm unsure... A Windows expert will have to say whether there's similar tech for Windows, as there's no HAProxy project release for Windows.
If this is crucial, 1000s of machines referencing an old IP, likely best to setup a Linux machine running HAProxy inside your infrastructure.
If you only have a few machines referencing the old IP, likely the simple fix is just to change all these machines to use the new IP.
@David Favor, it is trivial to setup additional IP address on the new DNS server to listen to queries coming to the old server. The old and new are on the same subnet. No need to redirect anything.
I have hundreds to thousands of devices or settings where my main DNS servers are referenced, which is why I never change the IP addresses for them. The servers come and go, but the IP addresses stay the same.
I have hundreds to thousands of devices or settings where my main DNS servers are referenced, which is why I never change the IP addresses for them. The servers come and go, but the IP addresses stay the same.
You cant do this with DNS. Start - run - ncpa.cpl
Right click your NIC - properties - IPV4 - Properties - advanced - add the Old IP address as an additional IP address. To the existing NIC.
Job done.
Right click your NIC - properties - IPV4 - Properties - advanced - add the Old IP address as an additional IP address. To the existing NIC.
Job done.
Ideally, you should update the DNS IP on the printers to direct traffic to the new DNS servers. Unless you have hundreds of devices using this old DNS address that is the simplest option for a variety of reasons.
Alternatively, you could add the old IP as an additional IP for your new DNS servers so it responds to DNS requests on either IP.
Note: This is assuming they are only DNS servers. Some other services (e.g. Domain Controller) may cause unnecessary complexity if given multiple IPs, but may still be possible if done right.
Alternatively, you could add the old IP as an additional IP for your new DNS servers so it responds to DNS requests on either IP.
Note: This is assuming they are only DNS servers. Some other services (e.g. Domain Controller) may cause unnecessary complexity if given multiple IPs, but may still be possible if done right.