Setting up correct upstream DNS
-
This post is deleted! -
Oh my Godness ... I got it
- System Domain Local Zone Type was not correct setup. Was on redirect, should be Type Transparent
-
@gamienator-0 said in Setting up correct upstream DNS:
should be Type Transparent
depends - I have mine on static which to be honest I would think more people would want than transparent.
Why would I my dns to go ask for something.local.lan if I do not have a record for it.. The only time you would want transparent is if your using same local domain that is public and you could have records in this domain that are resolved public etc..
Normally you would want to be using a non public resolvable name for your local resources, the new home.arpa for example would never resolve public so why should your dns try resolve anything ever in that domain from roots or where you forward.. So static is the more appropriate setting in that case.
-
@johnpoz said in Setting up correct upstream DNS:
[...] Normally you would want to be using a non public resolvable name for your local resources [...]
Well, I learned a different way: You should use a valid subdomain of a domain you use. Otherwise you could get in serious trouble if the TLD, you use internally will be available later. Therefore I decided to do it that way. Otherwise you could use a TLD mentioned in RFC2606, but it is written down that you shouldn't use it on production.
-
@gamienator-0 valid point about the tld.. Which is why use something like home.arpa which now the specific domain to use for local use domains.
I have used .lan as my local tld for many years - I don't think such a tld would ever be public.. But your point is still valid..
At previous company, we used companyname.com for external resources, and the AD and used companyname.net which we did own, but not used in public space..
Problem with using a sub is with dns devolution it is possible for client to query the parent domain without the sub, etc. which could lead to resolution issues.
