Right now internal DNS is controlled by our parent company. I also know putting private IP on public URLs could also be a security risk.īut the reason internal DNS is not an option is because I don't have access to it. So everyone is already use to using our testing URL we have with GoDaddy.
Again I know this is not best practice and I am trying to remedy that as well. Right now our test websites are using a publicly accessible URL. I don't want to do a host file for each PC, it would be between 10 and 15 PCs that would be accessing our test websites. So what is actually the problem for not being able to run your own internal DNS? There are all kinds of low-level simple DNS servers available that you can run on any kind of system, all down to an RPi. In addition there is a bunch of other reasons - check out the internet draft " IP Addresses that should never appear in the public DNS". In addition some security solutions don't allow public DNS servers to answer internal systems with private IP addresses. In theory it should work, to let a public DNS resolve your private queries - but people avoid this also because of security reasons - it makes no sense to allow everyone see what hosts you have on your internal network. In that case it wouldn't work.Īs wcrolando said, it doesn't make much sense for public DNS servers to handle private addresses, as these are not routed over the internet. Checking for private IP addresses could be implemented among other controls programmed into the UI of the public DNS. I'd suppose, that a generic DNS server wouldn't care, if an address is public or private.īut these public DNS servers out there are a bit upgraded in their logic, to prevent user input error. I'll leave the record up if you want to try it yourself. The A record is not on any internal DNS server.
The DNS server has no association with my domain. I just went into my DNS provider and created a record for a spare domain and set it to an RFC1918 address. That IP will just happen to be an RFC1918 address.2 OP just wants a DNS name () to resolve to an IP. He doesn't want to route the private IP over the Internet. If you have few stations you can use host addressing until you get DNS. You need public addresses to traverse the public network.
No See RFC 1918 Private addresses won't route. Why are saying you cannot use internal DNS? If you need to be connected to the internal network for it to work, then you just add it in internal DNS.
0 kommentar(er)
