A proper way to organize a DNS
 

Hello,

I have a question of the type "best practices". My architecture is very common but given the fact that I don't have much experience I would like to ask for comments.

I am administering a domain with a couple of machines in the LAN, and a DMZ. Say the public IP is 123.123.123.1. The domain name that points to this IP is my.company.com. From the inside part I have my LAN which is at 192.168.1.0 and my DMZ that is at 192.168.10.0. In the DMZ I have a web server which is at 192.168.10.5 and a dns server at 192.168.10.6.

Actually the dns resolves the www.my.company.com as 123.123.123.1. Then I have a rule on my router that forwards this connection to 192.168.10.5.

From the inside I have an intern domain that is my.company, and my DNS points www.my.company to 192.168.10.5.

Besides the fact that I have some troubles with wordpress which has a site_url variable that should be unique (that is the url that we type to go to the wordpress site), I was wandering is it a common practice to have two domains - one internal and one external, and to point to the web server with two different URLs.

I had a suggestion to organize my DNS in a manner that from the inside network www.my.company.com to point to the internal address of the web server 192.168.10.5. It seems to me not very proper manner to address this issue.

Any comments please.

Best,
E

You should follow the suggestion. If you're running bind, this is exactly what views are for.

Regards

Thank you for the link. That was the document I was looking for. Will give it a try tomorrow.

Best,
E