A
Alain Bourgeois
Hi,
I have in-house a win 2016 server standard, mail.<domain>.com, hosting the mails. We also have our internal dns, redirectors are 8.8.8.8 (google) + isp.
There is a datacenter hosting a web site on www.<domain>.com, on other servers/computers (we pay for hosting the web site, it is not in-house).
From outside the network (e.g. home: nslookup www.domain.com is an alias on domain.com, and has a fix IP).
From the lan DNS server:
nslookup www.<domain>.com
Serveur : UnKnown
Address: ::1
*** UnKnown ne parvient pas à trouver www.<domain>.com : Non-existent domain
It works fine for other domains.
I thought that when the address could not be found locally, it was redirected to 8.8.8.8 .
It seems it is not the case. Do I have to add <domain>.com and www.<domain>.com as PTR and A records pointing to the WAN ip address of www.<domain>.com, or did I miss something?
Alain Bourgeois
Continue reading...
I have in-house a win 2016 server standard, mail.<domain>.com, hosting the mails. We also have our internal dns, redirectors are 8.8.8.8 (google) + isp.
There is a datacenter hosting a web site on www.<domain>.com, on other servers/computers (we pay for hosting the web site, it is not in-house).
From outside the network (e.g. home: nslookup www.domain.com is an alias on domain.com, and has a fix IP).
From the lan DNS server:
nslookup www.<domain>.com
Serveur : UnKnown
Address: ::1
*** UnKnown ne parvient pas à trouver www.<domain>.com : Non-existent domain
It works fine for other domains.
I thought that when the address could not be found locally, it was redirected to 8.8.8.8 .
It seems it is not the case. Do I have to add <domain>.com and www.<domain>.com as PTR and A records pointing to the WAN ip address of www.<domain>.com, or did I miss something?
Alain Bourgeois
Continue reading...
