Hello all,
I have an odd question here and I'm hoping that someone can help out. I am running a hidden master DNS scenario where my DNS actually hosts all the zones, and hten an ISP is slaved off of me and that ISP's DNS are registered as the NS for the domain. This effectively saves my bandwidth. It is all hosted on a Linux server that is running Red Hat 7.3 and using Bind 9, it is NATed on my LAN and I just use port forwarding to get the DNS and web stuff to that machine. My question is this... if someone on my LAN queries the server for the web address and gets my WAN IP(the main NAT IP), when they try to access the site it won't work. The only way they can get the site is if they have it's internal IP. So, the question is... is there a way to distribute a different set of zones for internal host queries and not propogate those zones out to the real world?
If I need to clarify more, please let me know, but I would really appreciate some help.
Burke
I have an odd question here and I'm hoping that someone can help out. I am running a hidden master DNS scenario where my DNS actually hosts all the zones, and hten an ISP is slaved off of me and that ISP's DNS are registered as the NS for the domain. This effectively saves my bandwidth. It is all hosted on a Linux server that is running Red Hat 7.3 and using Bind 9, it is NATed on my LAN and I just use port forwarding to get the DNS and web stuff to that machine. My question is this... if someone on my LAN queries the server for the web address and gets my WAN IP(the main NAT IP), when they try to access the site it won't work. The only way they can get the site is if they have it's internal IP. So, the question is... is there a way to distribute a different set of zones for internal host queries and not propogate those zones out to the real world?
If I need to clarify more, please let me know, but I would really appreciate some help.
Burke