DNS/Public Domain Name Not Resolving


good day all, thank , contributions. 

i installed , configured rds environment on home network in access applications internally , externally via self-signed certificates. when decided configure environment production purposes ran few problems regards pointing/resolving registered domain name (first time registering public domain name) rds server externally. can access remote applications internally via https://mydomain/rdweb when accessing internet receive following error prompt dns_probe_finished_nxdomain – server mydomain.com cant found, because dns lookup failed.

quick outline of servers (using 1 physical server) & domain name configs

  • 1 x hyper-v host (ip: xxx.xxx.xxx.82) – (name: vhost01)
  • 1 x addc (dc/dhcp/dns) (ip: xxx.xxx.xxx.83) – vm – (name: dc01)
  • 1 x rds (domain joined) (ip: xxx.xxx.xxx.84) – vm – (name: rds01)

credentials of service provider hosting domain name mydomain.com

domain : mydomain.com 

xxx.xxx.xxx.177 (this default ip under manage dns console via provider, allocated various hostnames’s (@/mail/www). changed xxx.xxx.xxx.84 in order point rds server.

hostname                     ttl                  record type                 destination

@                                                         a                                  xxx.xxx.xxx.84

mail                                                      a                                  xxx.xxx.xxx.177 (not using mail server)

www                                                     a                                  xxx.xxx.xxx.84

ns records provided host

name server                             destination                   ip address

primary                                     xx1.dns-x.com              xx.xxx.xxx.2

secondary                                xx2.host-x.net               xxx.xx.xxx.254

third                                         xx1.host-x.net               xxx.xx.xx.254

i know correct way in should configure dns on dc01 in order resolve mydomain name externally. should pointing hostname records dc01 or rds01(which pointing to). possible make use of providers dns name servers or must configure new name servers on dc01/dns , change providers name servers.

i can provide additional information , assist best can if information provided vague. thank once again assisting me in matter.  

kind regards

hi scot,

as per previous post referred public domain information not being registered directly, mean isp has notified add dns records in public dns server?

yes, case, otherwise external users cannot resolve public dns name.

my internal , external domain name same, mean need split brain dns or has been resolved in 2012 r2 , no longer requirement rds?

wouldnt better make use of domain service providers public dns , register name servers there?

both methods work, setup split brain dns or register public dns records external-faced servers.

i still unsure how point mydomain.com (fqdn) publicly registered mydomain.com users can access servers remote apps externally via rdweb.

since public dns records registered, on external clients, point public dns server such isp’s public dns server.

best regards,

amy


please remember mark replies answers if , un-mark them if provide no help. if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  Remote Desktop clients



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...