3 ms·
Its perfectly ok to let your internal sites be resolved outside your network? Abc.internal resolves to 192.168.0.101 is fine?
by lazylizard 7y ago
Its perfectly ok to let your internal sites be resolved outside your network? Abc.internal resolves to 192.168.0.101 is fine?
- growse 7y agoWhat's the risk?
- isostatic 7y agoHow do you do PTR records? (what hostname is 10.12.43.122) How do you do split DNS? (Inside my network I want it pointing to my internal server) Now you could argue that the fault in both of those cases is IPv4 and the natting that comes with it.
- lazylizard 7y agoi don't get the ptr problem. My internal sites already have ptr records. My dns server sits facing the internet. Ptr records too. But yes. If u have a domain that is supposed to resolve different depending on the source ip that'd be..interesting... Now u need a website that displays different content depending on source ip or something like that...
- isostatic 7y agoIf your machine is pointing to doh on the Internet, how does a reverse lookup for an rfc1918 address work? One issue with doh is that it’s inconsistent - some applications use one resolver, some use another. The network (via dhcp) can’t hint at which resolver to use.
- unionpivo 7y agoi'd prefer not to. We work for a number of different clients, and its common to have pg11-clientanme.* and node-clientname.* ... I have over 200 domains internally, that i don't have externally. but its also flexibility. We often when we develop, want to redirect certain domains to our endpoints, for testing or whatever, and do that on DNS so that not everyone has to edit host files etc. we have pfsense internally, with number of people that can and do add/remove hosts/domains on daily basis, but host our external DNS on CF, and only 2 people have access to that.