Need DNS server to respond to queries from a workstation in a different subnet with the correct IP of the multi-homed DC
hello,
here environment:
- multi-homed dc/dns server (i know not recommended, there no way around meet requirements of system). there call "normal" connection on server serves clients (192.168.1.100), , "management" connection remote management , logging (192.168.10.100).
- round robin turned off on dc/dns server, clients on 192.168.1.0/24 subnet receive 192.168.1.100 address server when query dns.
- have workstation outside routed firewall - address 192.168.50.10. there no nat on firewall (the nat screws dns records, , workstation not join domain unless nat off). since not on 192.168.1.0/24 subnet, turning off round robin doesn't seem helping make sure workstation receives 192.168.1.100 address server when querying dns. firewall logs show machine attempting communicate 192.168.10.100 address, not allowed acls. nslookup on workstation returns both entries, order random (not consistent).
- disconnected system without distributed ad hierarchy (everything in lab.local domain).
how can set dns server such respond dns queries workstation correct ip of multi-homed dc?
is there way configure dns server such sees 192.168.50.0/24 subnet being "closest" 192.168.1.0/24 subnet subnet prioritization take care of this?
paul,
modifying hosts file on client fall-back workaround, have software application overwrite host file on periodic basis - code change would needed static entry mh dc in hosts file on particular client not overwritten/erased.
Windows Server > Directory Services
Comments
Post a Comment