jakgumbo
asked on
dns issue
AD integrated DNS on windows 2003 server. website is hosted offsite. want to be able to get to userpages built into website by going to username.domain.com. outside of network this works just fine. inside the network the sites do not resolve. any help would be appreciated.
when you are inside of your network, are you about the resolve the domain name (username.domain.com) to IP address?
Your internal network is probably identical with your internet domain name. In this case, your only choice is to create individual host (A) entries "username" in your internal DNS zone, pointing to the respective external IP addresses.
ASKER
when i try to resolve username.domain.com i get "host not found", my internal domain is also domain.com
ASKER
@sage wow, there isnt a better way to do this?
that's exatly what oBdA pointed out. all you need to do is set up a host record entry in your DNS, pointing username.domain.com to the correct public IP address
ASKER
so for 5000 users i would need to set this up individually for each person?
no. only on your DNS server, not client
ASKER
right but on my dns server i need to add 5000 entries??
well, if you have 5000 users, then that's not a good idea.
a way to work around is, you can setup another machine, which is NOT part of your AD domain, use ISP dns server, then remote control that machine to manage this.
a way to work around is, you can setup another machine, which is NOT part of your AD domain, use ISP dns server, then remote control that machine to manage this.
ASKER
im not sure i understand you. setup another machine, which is not part of my ad domain.....?
I mean a stand alone machine, don't join to your AD domain.
If all of the username.domain.com DNS entries need to point to the same IP address / hostname then setup a wildcard host on your AD server. With the wildcard you can have *.domain.com forward to your other host and then for everything that you don't want to go to the host you can specify.
The host side doing the username.domain.com hosting would have to be able to handle a user not existing, but the URL exists( ie: baduser.domain.com would resolve.. ).
The host side doing the username.domain.com hosting would have to be able to handle a user not existing, but the URL exists( ie: baduser.domain.com would resolve.. ).
ASKER
ok, i added a wildcard, but now when i do an nslookup domain.com i get by active directory computers and the external IP address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
my suggestion is set up a stand alone machine (not part of any AD domain), make sure it can access the proper username.domain.com (that means it needs to use other DNS server, like ISP's, not the DNS server in the current AD domain). Then just remote control this machine to manage all 5000 of users.