Join Log in
Score:0
avatar Server

Internal Access to Published Services: Direct vs Bouncing Off Firewall

in flag
evenmoreconfused

We have, as is common, two DNS infrastructures, one for internal resolution and another, non-forwarding, authoritative server for our public domains.

This question is about the comparative merits of two different approaches for our internal hosts to access our public services:

  • Some services have been set up so that internal hosts are given an internal address for the service (ie. a direct route to the server in the DMZ). In other words, the two DNS infrastructures point to entirely different IP addresses for the same server name.
  • Other services have been set up to bounce off the firewall, which rewrites the request to look like it's coming in from outside (our firewall calls this "Full NAT"). In this scenario, there is no record for the server in the internal DNS, and the public-facing DNS is relied upon to resolve the external address for the service.

I want to try to standardize on one approach or the other. Which is better?

22
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.