Osirion

Hi Guys, My father moves from two different offices and each have their own domain. I want to setup a trust so that he can login at either office without issues. Primary domain: examplemain.pvt (not a "real domain") Network IP: 192.168.0.100 DynDns: examplemain.dyndns.biz Primary Domain Server OS: Windows Server 2008 Secondary domain: examplesub.pvt (not a "real domain") Network IP: 192.168.0.100 DynDns: examplesub.dyndns.biz Secondary Domain Server OS: Windows Server 2008 R2 So I RD into examplemain.pvt and I go to the domain properties and click on trust to setup a new domain, but because "examplesub.pvt" isnt a real domain, its not resolvable. So - how do I make this work? Im assuming I would have to setup port forwarding to get this going as well - which ports do I need to forward?

Managed to sort it out, this is what you do: You need to use your local DNS in an Active Directory environment. Configure your statics and DHCP to use local DNS only and create forwarders to your ISP DNS. To do this: Open DNS management on your Domain Controller. Right click the server name and goto properties. Select the forwarders tab. Type the IPs of your ISPs DNS servers in here. On every device with a static IP, goto network connections. right click the connection being used and goto properties. click IP v 4 and choose properties. Put the IP 192.168.0.100 as the DNS server. On the Domain Controller open DHCP management. Under IPv4 Server Options add 006 DNS Server and type the IP of your Domain Controller.

Hi Guys, I have a problem that keeps popping up: Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.promedis.pvt.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). Possible causes of failure include: - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers - Specified preferred and alternate DNS servers are not running - DNS server(s) primary for the records to be registered is not running - Preferred or alternate DNS servers are configured with wrong root hints - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration My setup: Windows Server 2008 Server IP: 192.168.0.100 Gateway: 192.168.0.1 P-DNS: 192.168.0.1 promedis.pvt is a "ficticious" domain in the sense that its not a real TLD that is registered, but rather just a domain for in office use. According to the points above I should check my TCP/IP and DNS settings, but surely that is all correct? The primary dns / gateway are both set to my ADSL router which gets its Primary/Secondary DNS servers directly from the ISP. What to do? Thanks in advance! Kind Regards, Michael