Resolving DNS entries to internal IPs

[LandyMan]

Ok, maybe someone can help:

We have a DNS server inside our organisation, which is configured as primary, as well as carrying SOA for all our domains.

Now, we have a specific server (SERVER1) running webservices, that should be accessible from external and internal systems.

In the DNS server, we have the following entries:
www Host(A) 196.12.13.14 - External IP
www Host(A) 168.0.1.2 - Internal IP

Problem is that the internal IP is published to the ISP DNS servers, which obviously causes havoc for external connections.

Question: How do I set it up to have the internal IP not published to the ISPs?

Thanks

 

[Asha'man X]

Are you hosting all internet facing DNS services on premesis, or is the ISP handling part of that? If the ISP is hosting part of DNS, you just need the public IP published to them, not the internal. The external IP should be in a DMZ segment of your network, or it is port forwarded via the router.

 

[LandyMan]

Are you hosting all internet facing DNS services on premesis, or is the ISP handling part of that? If the ISP is hosting part of DNS, you just need the public IP published to them, not the internal. The external IP should be in a DMZ segment of your network, or it is port forwarded via the router.

We do a combination of various DMZ zones and port forwarding/routing.

We host all our own DNS entries

 

[hilton]

Without thinking about this too much (cos it's still to early for my brain) I would say the problem may be that the internal IP that you stipulated is actually not a recognised 'free' internal IP. It's part of an external range. Another thing is that your external DNs server should be in some sort of DMZ and completely separate from the internet DNS server.

Dunno, sounds like a hack job.

 

[LandyMan]

Got it sorted yesterday .... won't say how, but it's working

 

[MidnightWizard]

Unfair

Got it sorted yesterday .... won't say how, but it's working

Now that really spoils the fun


MW